March maintenance

See merge request !741

Dockerfile: Install Turkish locale in CI for UTF-8 locale too

See merge request !743

This is the actual recipe that has been used to generate the current
image, but I forgot to update the branch that got merged earlier.

gi: fix the usage of closure in CallbackIn::release

Closes #479

See merge request !740

jsapi-util-strings: Ignore locale to compute the upper case of a char (i.e. fix implicit properties on Turkish locale)

See merge request !742

We used to compute camel-case name of properties using toupper(),
however this is locale-dependent, while in this case we want to be sure
that we're only using ASCII values.

This is particularly problematic in Turkish (and maybe other locales)
because there 'i'.toLocaleUpperCase() is 'İ', that is definitely not an
ASCII char, causing problems to with our generated properties.

See: https://github.com/micheleg/dash-to-dock/issues/1687

An "Async" promise-based DBus method will return an FD list if it receives
one that is not falsy. This didn't match the behaviour of the "Remote"
callback-based DBus methods, which would always return either an FD list
or null as the third parameter to the callback.

So, when porting from "Remote" to "Async" you may get situations where a
null FD list is now undefined.

Add tests that encode this expectation.

In !731 we added this API. These tests make sure it can do everything that
the previous "Remote" callback-based API could, and serve as documentation
for how to use it.

In spirit is is a const object, but that cannot be passed to
gobject-introspection C APIs because they take a non-const pointer.

Rename it garray_new_for_storage_type() to reflect that we are supposed to
pass the result of g_type_info_get_storage_type(), and to remove the gjs_
prefix since it is a static function.

This allows calling this function in a future refactor where we don't have
access to the GITypeInfo pointer.

This increases expressiveness of the code because it expresses the
intent better than comparing the different values of the GITypeTag. This
will be used more in future refactors.

Requires bumping the Meson version, no need to do it just for this

We were getting closure pointer from in_arg.  Unfortunately, in_arg
contains the native closure pointer, which does not equals to of the
pointer to ffi_closure if libffi is built without
`--disable-exec-static-tramp`.

I guess gjs has never been really tested with such a libffi build :).

Add support for JS async calls in DBusProxyWrapper

See merge request !731

Currently, DBusProxyWrapper dynamically creates two methods for
each method available in the DBus interface: one with the suffix
Sync (which blocks the calling thread until the call returns),
and another with the suffix Remote (which accepts a callback,
called when the DBus calls returns).

Since GJS has support for async/await, it is a good idea to use
them for DBus. Unfortunately, that means creating some plumbing
using Promises. It is not complex, but it is a repetitive task.

This MR fixes this by adding a third method, suffixed with
Async, that returns a Promise that calls the DBus method and
returns the result with `resolve` (or `reject` if an error
occurs). This allows to call a DBus method from an async
function and wait for the result using `await`.

Handle reference cycles in pretty print function

Closes #469

See merge request !739

value: Fix compilation error on Darwin

Closes #473

See merge request !738

Evan Miller authored Mar 18, 2022 and Philip Chimento committed Mar 18, 2022

Same gint64/int64_t type mismatch on Darwin (long vs long long) as the
previous commit.

Evan Miller authored Mar 18, 2022 and Philip Chimento committed Mar 18, 2022

It looks like this is due to a gint64/int64_t type mismatch on Darwin
(long vs long long), at least using GLib 2.66. This patch seems to fix
the immediate issue.

Closes: #473

gi: Use new GObject Introspection callable API

Closes #428

See merge request !737

This avoids misusing the closure pointer by creating a clear
separation between the native closure pointer and the pointer
to the libffi closure.

Fixes #428

Unreviewed, pushing to fix build.

Verbose object print output

Closes #107

See merge request !587

March maintenance

See merge request !736

February maintenance

See merge request !735

package: Reverse order of running-from-source checks

See merge request !734

Only the type tag information is used here, so there's no need to require
the type info pointer. This allows refactoring to call this function from
places where we don't have the type info pointer available.

This function doesn't need the whole GITypeInfo, just the type tag. This
refactor allows reusing it in a separate code path for basic types that
are only identified by their type tag.