| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=740303
|
|
|
|
|
|
|
| |
Nullable value-types are actually pointers to heap-allocated structures.
Therefore a pointer-based marshaller is required for those types.
https://bugzilla.gnome.org/show_bug.cgi?id=758816
|
|
|
|
|
|
| |
g_cclosure_marshal_VOID__BOXED
g_cclosure_marshal_VOID__VARIANT
g_cclosure_marshal_BOOLEAN__BOXED_BOXED
|
|
|
|
|
|
| |
This is because an EnumValue object does not have a type reference.
https://bugzilla.gnome.org/show_bug.cgi?id=780050
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=777697
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Based on patch by gandalfn
https://bugzilla.gnome.org/show_bug.cgi?id=764481
|
|
|
|
|
|
|
| |
Remove superfluous cname_prefix namespace-attribute.
Add get_version() and fix array-length-type of Dict.suggest().
https://bugzilla.gnome.org/show_bug.cgi?id=767522
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=759255
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=759255
|
|
|
|
|
|
|
| |
There is no explicit array-length returned while it is implicitly related
to the in-parameter those methods are taking.
https://bugzilla.gnome.org/show_bug.cgi?id=705987
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=777782
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=779090
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=779090
|
|
|
|
| |
Clarify contents of directory with new name
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=779490
|
|
|
|
|
|
| |
Fixes client-side dbus generation on methods that don't throw any error.
https://bugzilla.gnome.org/show_bug.cgi?id=779652
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 09e6818d01e introduced the possibility of inserting _error
labels at the end of functions, which make C compilers angry.
This "test" (no actual tests are run, just compile correctness is
checked here) triggers some of these situations.
the "test3" abstract method is trickier though, it doesn't warn
but produces code with early returns, which in practice means
possible leaks.
https://bugzilla.gnome.org/show_bug.cgi?id=778540
|
|
|
|
|
|
|
| |
If there are arguments that need freeing, we need to fall through the
_error label, if there is any.
https://bugzilla.gnome.org/show_bug.cgi?id=778540
|
|
|
|
|
|
|
| |
Fixes the _error label from being set at the end of a compound statement
if there are no values to unref.
https://bugzilla.gnome.org/show_bug.cgi?id=778540
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=779219
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The elements of current_required_app_classes end up in the generated
code in g_type_ensure() statements. The order of these can vary
between builds when using a HashSet, breaking reproducibilty.
See https://wiki.debian.org/ReproducibleBuilds
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802528
|
|
|
|
|
| |
BookmarkFile.load_from_file, load_from_data_dirs and to_file may
also throw FileError in addition to BookmarkFileError.
|
|
|
|
|
|
|
| |
The server will exhaust all fds before the fd list in the dbus
request is opened. We do expect it to fail in the client.
https://bugzilla.gnome.org/show_bug.cgi?id=778540
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 09e6818d01 changed dbus server paths so requests fell back
to freeing allocated memory on errors. However certain kinds of
dbus replies issue a final g_dbus_connection_send_message() there.
In case of errors, _reply_message will be NULL, and the error paths
would have already issued g_dbus_method_invocation_return_gerror(),
so the g_dbus_connection_send_message() call is both unnecessary and
warns on the NULL argument. So move the DBus reply before the _error
label.
https://bugzilla.gnome.org/show_bug.cgi?id=778540
|
|
|
|
|
|
|
|
|
| |
On the right situations (eg. fd exhaustion), both
g_dbus_message_get_unix_fd_list() and g_unix_fd_list_get() should be
considered failable here. Add proper error handling to avoid triggering
glib warnings.
https://bugzilla.gnome.org/show_bug.cgi?id=778540
|
|
|
|
|
|
|
| |
This will make extracted variables properly freed when extracting those
fails at some point.
https://bugzilla.gnome.org/show_bug.cgi?id=778540
|
|
|
|
|
|
|
| |
Those may be left uninitialized after error handling paths are introduced,
so invalid data might be attempted to be freed later on.
https://bugzilla.gnome.org/show_bug.cgi?id=778540
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=778224
|
|
|
|
|
|
|
| |
This make it match vala's generated code of async-module.
To properly account for non-void *_async methods we require some additional
metadata since only the return-type of *_finish method is known.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=777958
|
|
|
|
|
|
|
|
|
| |
Add test-case and fix code generator for call to the setter to pass
instance as a value rather than as a pointer to value.
Based on patches by Nathan Summers.
https://bugzilla.gnome.org/show_bug.cgi?id=657346
|
|
|
|
|
|
|
| |
Assigning values to properties this way leads to a ref/copy of the source
and therefore requires a unref/destroy afterwards.
https://bugzilla.gnome.org/show_bug.cgi?id=766739
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=762819
|