https://github.com/GNOME/glib

sort by:
Revision Author Date Message Commit Date
041dc26 Add boxing for GTree, GQueue and GNode Closes issue #1233 14 August 2019, 08:10:51 UTC
10be2c1 Update Catalan translation 14 August 2019, 05:57:18 UTC
0984b54 Merge branch 'wip/smcv/reproducer-for-1852' into 'master' glib/tests/fileutils: Add a reproducer for #1852 See merge request GNOME/glib!1034 13 August 2019, 15:23:22 UTC
09b3bf2 Merge branch 'post-release-version-bump' into 'master' Post-release version bump See merge request GNOME/glib!1015 13 August 2019, 09:04:01 UTC
941c0bd glib/tests/fileutils: Add a reproducer for #1852 This test passes on the glib-2-60 branch, and failed before merging !1027. Signed-off-by: Simon McVittie <smcv@collabora.com> 13 August 2019, 07:37:40 UTC
6d7143e Merge branch 'wip/carlosg/utf8-strreverse-invalid-writes' into 'master' gutf8: Assert that written memory stays in bounds See merge request GNOME/glib!1026 12 August 2019, 10:39:11 UTC
870b30b Merge branch 'wip/carlosg/fix-mkdir-with-parents-errors' into 'master' gfileutils: Fix error propagation for other than ENOENT See merge request GNOME/glib!1027 12 August 2019, 08:01:59 UTC
0ae99bf Update Indonesian translation 12 August 2019, 06:03:05 UTC
3a4a665 gfileutils: Fix error propagation for other than ENOENT Commit 6f55306e04e5 unintendedly broke error handling for other error conditions than ENOENT along the path, like EPERM. It wanted to ignore ENOENT on all elements except the last in the path, but in doing that it ignored any other error that might happen on the last element. https://gitlab.gnome.org/GNOME/glib/issues/1852 08 August 2019, 00:32:46 UTC
154f6ca gutf8: Assert that written memory stays in bounds You may expect funny effects from passing invalid UTF-8, but not that funny. The assert will probably be a better and more immediate confirmation of an error than invalid writes under the address of the string copy. https://gitlab.gnome.org/GNOME/glib/issues/1863 07 August 2019, 21:33:46 UTC
179fdc5 Update Romanian translation 05 August 2019, 14:03:50 UTC
37b2093 Merge branch 'contributing-fixes' into 'master' Remove mentions of mailing lists from the documentation See merge request GNOME/glib!1002 05 August 2019, 10:20:40 UTC
57b6b4b Merge branch 'g-object-get-property-zero-init' into 'master' g_object_get_property: Improve documentation for use of G_VALUE_INIT See merge request GNOME/glib!1023 01 August 2019, 09:47:56 UTC
41d31cd g_object_get_property: Document accepting G_VALUE_INIT as new API Code intended to be portable to older versions of GLib cannot rely on this being considered valid. Signed-off-by: Simon McVittie <smcv@collabora.com> 01 August 2019, 08:29:52 UTC
bf8b669 g_object_get_property: Clarify meaning of G_TYPE_INVALID "Uninitialized value" is partially correct, since it has not been initialized with a type, but it's more precise to say "zero-initialized value". It is still a programming error to pass a pointer to uninitialized memory with arbitrary contents as the value. Signed-off-by: Simon McVittie <smcv@collabora.com> 01 August 2019, 08:29:52 UTC
1f79c7f Updated Spanish translation 30 July 2019, 07:38:18 UTC
84738f7 Merge branch 'wip/hadess/gnetworkmonitor-nm-fixups' into 'master' gnetworkmonitornm fixups See merge request GNOME/glib!1016 29 July 2019, 15:47:55 UTC
b80fcc6 tests: Remove unneeded ";" in G_DEFINE_INTERFACE_WITH_CODE 29 July 2019, 15:28:01 UTC
f299886 gnetworkmonitornm: Remove double-space 29 July 2019, 15:28:01 UTC
109f247 gnetworkmonitornm: Arguments to g-signal's callback are const 29 July 2019, 15:28:01 UTC
7d3ecce gnetworkmonitornm: Disconnect g-signal from proxy So that we're sure never to receive a signal if something is keeping the proxy alive. 29 July 2019, 15:28:01 UTC
ef1d5b5 gnetworkmonitornm: Remove unneeded ";" in G_DEFINE_INTERFACE_WITH_CODE 29 July 2019, 15:28:01 UTC
86ba1b3 Merge branch 'application-free-remote-actions' into 'master' gapplication: Fix a leaking GRemoteActionGroup member See merge request GNOME/glib!1011 29 July 2019, 13:21:51 UTC
a3d9c3f Post-release version bump Signed-off-by: Philip Withnall <withnall@endlessm.com> 29 July 2019, 13:16:45 UTC
6bebef1 2.61.2 Signed-off-by: Philip Withnall <withnall@endlessm.com> 29 July 2019, 13:04:40 UTC
018eaf5 Merge branch '1438-deprecate-gtimeval' into 'master' Deprecate GTimeVal- and GTime-based APIs Closes #1438 See merge request GNOME/glib!1004 29 July 2019, 12:59:50 UTC
5c5034a Merge branch '1792-again-marshal-params' into 'master' glib-genmarshal: Avoid a param ref for static param valist arguments Closes #1792 See merge request GNOME/glib!928 29 July 2019, 11:45:07 UTC
14b087e gmain.c: Fix comment about Y2038 safety of g_get_real_time() This comment was correct until commit adf1f98f62, when the `GTimeVal` which the result was put into (introducing the Y2038-unsafety) was dropped. The adjustment and scaling of the `FILETIME` should not make it Y2038-unsafe: the maximum `FILETIME` is 2^64-1. Subtracting the epoch adjustment and dividing by 10 gives the timestamp 1833029933770955161, which is in June 58086408216 (at just after 3am UTC). I think that’s enough time to be going on with. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
96c74fd win32: Stop using deprecated GTimeVal in GWinHttpFile Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
2d62503 gdatetime: Stop using deprecated g_get_current_time() This requires some reworking of the internal g_date_time_new_from_unix() function, since it previously operated in seconds, which wasn’t high enough resolution — the g_get_current_time() code path used to operate in microseconds. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
2df27e3 tests: Ignore deprecated functions in a few main loop and timer tests Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
2ed7696 tests: Ignore deprecated functions in parts of GDateTime tests Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
82e3e10 glib: Stop using g_get_current_time() in various places Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
c0f958d glib: Stop mentioning deprecated g_get_current_time() in docs Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
de25be7 tests: Stop using deprecated g_get_current_time() Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
1616546 gfileinfo: Stop using deprecated GTimeVal Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
def5db2 gdbusutils: Stop using g_get_current_time() It is deprecated. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
4faf4fc gfileinfo: Deprecate g_file_info_{get,set}_modification_time() They use the deprecated GTimeVal type, which is not year 2038 safe, so have to be deprecated. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
d166a55 gfileinfo: Add g_file_info_{get,set}_modification_date_time() APIs These are alternatives to g_file_info_{get,set}_modification_time(), which will soon be deprecated due to using the deprecated GTimeVal type, which is not year 2038 safe. The new APIs take a GDateTime instead. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
a3f22f0 gbookmarkfile: Use GDateTime instead of GTimeVal internally Avoid using a deprecated type. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
aa261ca gasyncqueue: Ignore use of deprecated types in deprecated APIs It’s unavoidable. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
45b74b0 gdate: Deprecate methods which use GTimeVal GTimeVal is not year-2038-safe. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
ec0cc39 gmain: Add deprecation ignore guards around other GTimeVal usage Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
fe760ba gmain: Swap implementations of g_get_current_time() + g_get_real_time() The former is now deprecated, so it makes sense to base its implementation on the latter, rather than the other way around. This introduces no functional changes. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
626b6f5 gmain: Deprecate g_get_current_time() because it uses GTimeVal GTimeVal is not year-2038-safe. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
b8540db glib: Deprecate API using GTimeVal in gtimer.h GTimeVal is not year-2038-safe. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
e971b25 gdatetime: Deprecate GDateTime API which uses GTimeVal GTimeVal is not year-2038-safe. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
44d1fa3 gdate: Fix minor typo in GTimeVal documentation Signed-off-by: Philip Withnall <withnall@endlessm.com> 29 July 2019, 11:27:29 UTC
e3f88f3 gtypes: Deprecate GTimeVal in favour of guint64 or GDateTime GTimeVal is subject to the year 2038 problem, since its `tv_sec` field is a `glong`, which is 32 bits on 32-bit platforms. Use `guint64` to represent microsecond-precision time since the Unix epoch; or use `GDateTime` for full date/time representation. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #1438 29 July 2019, 11:27:29 UTC
e357619 gdate: Minor documentation formatting improvements for GTime Signed-off-by: Philip Withnall <withnall@endlessm.com> 29 July 2019, 11:27:29 UTC
5983cc8 gdate: Deprecate GTime It’s not Y2038-safe, as it’s 32-bit. While it was previously deprecated in the documentation, now add the deprecation annotation for the compiler. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
dbabd2b gdatetime: Add g_date_time_format_iso8601() convenience function This is a simple wrapper around g_date_time_format_iso8601() which always produces ISO 8601 dates, without people having to remember the format string for them (and with the convenience of terminating UTC dates with ‘Z’ rather than ‘+00’). Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #1438 29 July 2019, 11:27:29 UTC
8f385b8 Merge branch 'master' into 'master' windows: fix multicast socket binding to specific network interfaces Closes #1635 See merge request GNOME/glib!887 29 July 2019, 11:10:40 UTC
014e8d0 Merge branch 'wip/lantw/gapplication-remove-inactivity_timeout-source-on-finalize' into 'master' gapplication: remove inactivity_timeout source on finalize See merge request GNOME/glib!1009 29 July 2019, 09:50:39 UTC
0f13185 gapplication: Fix a leaking GRemoteActionGroup member Fix prompted by Ting-Wei Lan’s similar fix for the inactivity timeout (!1009). Signed-off-by: Philip Withnall <withnall@endlessm.com> 29 July 2019, 09:49:45 UTC
d62cabc Merge branch '1847-log-structured-max-version' into 'master' gmessages: Only use structured logs if GLIB_VERSION_MAX_ALLOWED is ≥2.56 Closes #1847 See merge request GNOME/glib!1008 28 July 2019, 10:49:57 UTC
0ed8605 gapplication: remove inactivity_timeout source on finalize The event source used to handle inactivity_timeout doesn't hold a reference on the application. Therefore, it is possible for callback function of the event source to run after the application has been freed, leading to use-after-free problem. To avoid the problem, we should remove the event source before the application is freed. This should fix SIGBUS crash of gio/tests/gapplication on FreeBSD. https://gitlab.gnome.org/GNOME/glib/issues/1846#note_566550 27 July 2019, 07:28:23 UTC
54f94b1 gmessages: Only use structured logs if GLIB_VERSION_MAX_ALLOWED is ≥2.56 Only redefine g_message() and friends to use structured logging if the compiling code is OK with depending on GLib functionality from ≥2.56. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #1847 26 July 2019, 19:49:01 UTC
517f756 Merge branch 'rnagy/glib-mkdir' into 'master' Resubmission of !832 “Try to create the complete path right away and fall back” See merge request GNOME/glib!1007 26 July 2019, 10:57:53 UTC
ca98741 gfileutils: Try creating complete path first Try to create the complete path right away and fall back to creating all path elements one by one. This also helps to avoid TOCTTOU problems and avoids walking the path all the time, providing a nice performance gain, by avoiding syscalls. 26 July 2019, 10:28:43 UTC
6f55306 gfileutils: Ignore ENOENT from all except the last element Ignore ENOENT errors up until the last element while trying to create each of the path elements in case a restricted file-system is being used where path elements can be hidden or non-accessible. 26 July 2019, 10:27:50 UTC
b482a5c Merge branch 'array-test-fixes' into 'master' Small array test fixes See merge request GNOME/glib!996 26 July 2019, 08:59:17 UTC
78b1278 Merge branch '488-assert-gobjects-dont-leak' into 'master' gobject: Add a g_assert_finalize_object() macro Closes #1780 and #488 See merge request GNOME/glib!859 25 July 2019, 15:42:39 UTC
b6d4da7 tests: Use g_object_assert_last_unref() in various tests Signed-off-by: Philip Withnall <withnall@endlessm.com> 25 July 2019, 14:23:21 UTC
b76bf3c gobject: Add a g_assert_finalize_object() macro With modifications by Philip Withnall. Fixes: #488 25 July 2019, 14:23:21 UTC
17be9e5 Merge branch '436-test-coredumps' into 'master' Fix tests creating coredumps Closes #436 See merge request GNOME/glib!959 25 July 2019, 13:49:09 UTC
298ee8f Merge branch '1791-macos-get-mime-dirs' into 'master' gcontenttype: Add no-op versions of {get,set}_mime_dirs() on win32/macOS Closes #1791 See merge request GNOME/glib!927 25 July 2019, 13:48:04 UTC
3de1b88 gcontenttype: Add no-op versions of {get,set}_mime_dirs() on win32/macOS These are here to prevent linker errors, since `gcontenttype.[ch]` aren’t compiled on Windows or macOS. The implementations are stubs to be filled out by someone who knows each platform, at some point in the future. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #1791 24 July 2019, 13:50:53 UTC
0c0cf59 Merge branch 'meson-bump' into 'master' Bump the required version of Meson See merge request GNOME/glib!924 24 July 2019, 12:57:32 UTC
bd372e3 ci: Fix non-build jobs All non-build jobs must share the same Docker image with the Fedora build job. 24 July 2019, 12:32:55 UTC
85dc45e build: Bump up the required version of Meson We cannot bump to the latest stable version of Meson, even if it would make our life easier. We can, though, use the version of Meson shipped by the next, soon to be released Debian stable. 24 July 2019, 12:08:06 UTC
f0d713e ci: Use the new Docker images 24 July 2019, 12:08:06 UTC
fa6f2d4 ci: Update the MSYS2 build script 24 July 2019, 12:08:06 UTC
772a6e3 ci: Update the MSVC build script 24 July 2019, 12:08:06 UTC
f6b4012 ci: Update the MingW Docker image 24 July 2019, 12:08:06 UTC
ed7c258 ci: Update the Android NDK Docker image 24 July 2019, 12:08:06 UTC
14d2c48 ci: Update Fedora's Docker image Match the version of Meson we install with the one we require. 24 July 2019, 12:08:06 UTC
9fdc276 ci: Update Debian's Docker image New stable release of Debian is out, and we need to bump the version of Meson to match our requirements. 24 July 2019, 12:08:06 UTC
00d7568 build: Remove unsupported `install` directives We're using the `install` argument for configure_file() all over the place. The support for an `install` argument for configure_file() was added in Meson 0.50, but we haven't bumped the minimum version of Meson we require, yet; which means we're getting compatibility warnings when using recent versions of Meson, and undefined behaviour when using older versions. The configure_file() object defaults to `install: false`, unless an install directory is used. This means that all instances of an `install` argument with an explicit `true` or `false` value can be removed, whereas all instances of `install` with a value determined from a configuration option must be turned into an explicit conditional. 24 July 2019, 11:45:02 UTC
3f1a79a Merge branch 'allow_guid_key_in_dbus_addresses' into 'master' Allow guid key in dbus addresses Closes #1018 See merge request GNOME/glib!995 23 July 2019, 13:01:09 UTC
c50304f Merge branch 'master' into 'master' Add (out) annotation to (optional) parameters Closes #1837 See merge request GNOME/glib!999 23 July 2019, 12:14:18 UTC
74583af Add (out) annotation to (optional) parameters … as the parameters are not (inout). Closes #1837 23 July 2019, 11:41:42 UTC
ab544aa docs: Remove mentions of mailing lists And drop FTP from the list of places where to find release archives. This is not 1998. 23 July 2019, 10:27:30 UTC
4d73e1f Use GitLab to reserve a new fundamental type slot Even though you *really* shouldn't do that at all. 23 July 2019, 10:27:30 UTC
bcf208b Bugs should be reported on GitLab Not on mailing lists that do not exist any more. 23 July 2019, 10:27:30 UTC
6a207c3 doap: Update the <mailing-list> element 23 July 2019, 10:27:30 UTC
dd42b8f docs: Remove mentions of mailing lists We use a tag on Discourse, now. 23 July 2019, 10:27:30 UTC
11715d1 docs: The mailing lists are no more Don't send people to mailing lists that do not exist any more. We moved to Discourse. 23 July 2019, 10:05:17 UTC
8c5a14a Update Brazilian Portuguese translation 22 July 2019, 03:28:50 UTC
204c625 Merge branch 'fix_G_DECLARE_DERIVABLE_TYPE_documentation' into 'master' Fix typo in G_DECLARE_DERIVABLE_TYPE documentation Closes #1838 See merge request GNOME/glib!1000 20 July 2019, 14:38:43 UTC
79da355 Fix typo in G_DECLARE_DERIVABLE_TYPE documentation Closes issue #1838 20 July 2019, 14:05:12 UTC
249299a Merge branch 'doc-fixes' into 'master' Various doc fixes See merge request GNOME/glib!982 17 July 2019, 10:58:21 UTC
fa4423d Merge branch 'clang-cl-support' into 'master' Experimental clang-cl support See merge request GNOME/glib!979 17 July 2019, 10:30:28 UTC
81b1ff8 Merge branch 'atomic' into 'master' fix atomic detection on older gcc versions See merge request GNOME/glib!991 17 July 2019, 10:22:00 UTC
77cc96a Update the instructions in .gitlab-ci. These where a copied, but not adapted. This is similar to a change in the gtkdoc module. 17 July 2019, 04:12:24 UTC
f6666f5 Merge branch 'dbus-address-transfer-annotation' into 'master' gdbusaddress: Add missing transfer annotation See merge request GNOME/glib!997 16 July 2019, 21:07:20 UTC
0c495f3 gdbusaddress: Add missing transfer annotation 16 July 2019, 20:43:20 UTC
298c6ad Merge branch 'docs-examples' into 'master' docs: Add example to g_test_summary() documentation See merge request GNOME/glib!992 16 July 2019, 13:51:41 UTC
c0f13f3 garray: Fix binary search for non-existent elements on the left If searching for an element which is smaller than every element in the array (i.e. the element being searched for is not in the array), the previous g_array_binary_search() implementation would underflow in the calculation `right = middle - 1`, and end up trying to dereference an element way off the right of the array. Fix that by checking the additions/subtractions before doing them, and bailing if the bounds are hit. We don’t need to check `middle < G_MAXUINT`, as `middle` is bounded above by `right`, which is always `<= _array->len - 1`, and `_array->len <= G_MAXUINT`. Add some tests for that, and for not-present elements in the middle of the array. Previously, the tests only checked for not-present elements which were bigger than every element in the array. Signed-off-by: Philip Withnall <withnall@endlessm.com> 16 July 2019, 11:14:53 UTC
ec61daf garray: Rewrite binary search calculation to avoid integer overflow If `right` and `left` are both near `G_MAXUINT`, it’s possible for the addition to overflow, even if the eventual result would fit in a `guint`. Avoid that by operating on the difference instead. The difference is guaranteed to be positive due to the prior `left <= right` check. Signed-off-by: Philip Withnall <withnall@endlessm.com> 16 July 2019, 10:35:18 UTC
back to top