| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
We should run test_pass_fd twice, once using gspawn's fork/exec codepath
and once attempting to use its posix_spawn codepath. There's no
guarantee we'll actually get the posix_spawn codepath, but it works
for now on Linux.
This causes the test to fail if I break the fd remapping implementation
in my previous commit. Without this, we fail to test fd remapping on the
optimized codepath.
|
|
|
|
|
|
| |
This means that GSubprocess will (sometimes) be able to use the
optimized posix_spawn codepath instead of having to fall back to
fork/exec.
|
|\
| |
| |
| |
| | |
Small optimization for g_object_set
See merge request GNOME/glib!2254
|
| |
| |
| |
| |
| |
| |
| |
| | |
No need to call memset in the loop, we can just
initialize all the values in one go.
GtkBuilder is now using g_object_setv, so this
may improve application start times a bit.
|
| |
| |
| |
| |
| |
| | |
We've already followed the redirection, no need
to check for that again - just avoid notifying
non-readable properties.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
gobject: Cleanup GWeakRef locations on object finalization
Closes #2390 and #865
See merge request GNOME/glib!2064
|
| |
| |
| |
| |
| |
| |
| | |
Weak locations were not fully cleaned on run_dispose() and after dispose
vfunc was called, so ensure that this is the case.
Fixes: #865
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As per the previous change, an object that had weak locations set may
need to lock again the weak locations mutex during qdata cleanup, but
we can avoid this when we know we're removing the last location, by
removing the qdata entry and freeing the data.
In case a new location is needed for the same object, new data will be
added.
However, by doing this the weak locations during dispose may be
invalidated once the weak locations lock is passed, so check again if
this is the case while removing them.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It can happen that a GWeakRef is added to an object while it's disposing
(or even during finalizing) and this may happen in a thread that (weak)
references an object while the disposal isn't completed yet or when
using toggle references and switching to GWeakRef on notification (as
the API suggests).
In such scenario the weak locations are not cleaned up when the object
is finalized, and will point to a free'd area.
So, during finalization and when we're sure that the object will be
destroyed for sure, check again if there are new weak locations and
unset them if any as part of the qdata destruction.
Do this adding a new utility function so that we can avoid duplicating
code to free the weak locations.
Added various tests simulating this case.
Fixes: #2390
|
|\ \
| | |
| | |
| | |
| | | |
GString: Bump minimum size
See merge request GNOME/glib!2251
|
|/ /
| |
| |
| |
| |
| | |
GString starts out at a size of 2, which is just
not useful. Bump the minimum size to 64 to cut
down on the number of tiny reallocations we do.
|
|\ \
| | |
| | |
| | |
| | | |
gdesktopappinfo: Do not call xterm when it does not exist, inform the caller the launch failed
See merge request GNOME/glib!2245
|
| | |
| | |
| | |
| | |
| | | |
Instead of calling xterm when it clearly does not exist and causes a silent error,
inform the user that the launch failed so they can take the right action.
|
| | |
| | |
| | |
| | | |
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
| |/
|/| |
|
|\ \
| | |
| | |
| | |
| | | |
ci: Replace FreeBSD 11 with FreeBSD 13
See merge request GNOME/glib!2248
|
|/ /
| |
| |
| |
| | |
FreeBSD 11 will go EOL in a month, and FreeBSD 13 was released several
months ago. Remove the FreeBSD 11 job and add a FreeBSD 13 job.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
|\
| |
| |
| |
| | |
docs: Add a note about git-evtag to SECURITY.md
See merge request GNOME/glib!2110
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
gsettingsschema: Fix docs for g_settings_schema_key_range_check()
Closes #2425
See merge request GNOME/glib!2160
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The first sentence incorrectly said that it checked the type of the
value, and then the second sentence explicitly said it was a programmer
error to give a value of the wrong type.
According to the code, the second sentence is correct.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
Fixes: #2425
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Fix false deprecation warnings on old GCC/MSVC
Closes #2472
See merge request GNOME/glib!2234
|
| | |
| | |
| | |
| | | |
Closes #2472
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
gpowerprofilemonitorportal: Set property value by default
Closes #2481
See merge request GNOME/glib!2241
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If the first power-profile installed test fails (for example, because
xdg-desktop-portal isn’t available), correctly tear down the dbusmock
object, or it will cause setUp() to fail when the next test in the suite
is run.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
Helps: #2481
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When first creating the monitor, correctly set its property value to the
value from the portal, rather than waiting for the portal value to
change to set it.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
Fixes: #2481
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It’s not always guaranteed that a property is cached, so handle the case
when it isn’t.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
get_cached_property() returns a new reference.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Revert "Merge branch 'fix/gclosure-invoke-type-annotation' into 'main'"
Closes #2477
See merge request GNOME/glib!2237
|
| | | |
| | | |
| | | | |
This reverts merge request !2181
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
gio: Fix conditions in memory-monitor test
See merge request GNOME/glib!2240
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We were lucky that this worked in some cases (the test is racy), but we
should actually run the condition check each loop, rather than when the
function is called.
Spotted by Martin Pitt:
https://github.com/GNOME/glib/commit/96a8c02d240d7c9ae366c63771291413384bdfb7#r54773831
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
ci: Use C.UTF-8 locale on FreeBSD 12
See merge request GNOME/glib!2238
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
doc: Explicitly said, that no null term. is needed
See merge request GNOME/glib!2219
|
|/ / / / / |
|
| | | | | |
|
| | | | | |
|
|/ / / / |
|
| | | | |
|
|/ / / |
|