https://github.com/GNOME/glib

sort by:
Revision Author Date Message Commit Date
10be782 Merge branch 'zlib' into 'master' Check for zlib header See merge request GNOME/glib!486 23 November 2018, 09:28:03 UTC
c49ed61 Check for zlib header It is not enough to check for the library, we also need zlib.h installed to be able to use it. Autotools were also checking for the header. 23 November 2018, 01:14:30 UTC
b660a67 Merge branch 'mcatanzaro/tls1.3-handshake' into 'master' Deprecate TLS rehandshaking See merge request GNOME/glib!478 21 November 2018, 12:09:22 UTC
85f7d49 Deprecate TLS rehandshake APIs Allowing unsafe rehandshakes used to be required for web compatibility, but this is no longer a concern in 2018. So there should no longer be compatibility benefits to calling this function. All it does is make your TLS connection insecure. Also, rehandshaking no longer exists at all in TLS 1.3. At some point (maybe soon!) glib-networking will begin ignoring the rehandshake mode, so let's deprecate it now. 21 November 2018, 04:07:58 UTC
2031e37 Update documentation of g_tls_connection_handshake() one last time Let's entirely deprecate calling this function for rehandshaking. The current documentation is OK, but guarantees defined behavior (to attempt a rehandshake) when TLS 1.2 is in use. But there's no way to force TLS 1.2, and also no way to check which version of TLS is in use. I really should have deprecated use of this function for rehandshaking entirely last time I updated it. Fortunately, there should be no compatibility risk for existing code, because rehandshaking has no visible effects at the API level. 21 November 2018, 04:04:50 UTC
f54b48b Merge branch 'master' into 'master' meson: Turn selinux into a meson feature and make it auto by default See merge request GNOME/glib!483 20 November 2018, 19:14:52 UTC
8cc92bc meson: Turn selinux into a meson feature and make it auto by default Making it more user friendly when building on distro no deploying selinux 20 November 2018, 18:58:58 UTC
23f286e Merge branch 'libz-fallback' into 'master' Check for 'z' library before fallbacking to subproject See merge request GNOME/glib!482 19 November 2018, 22:38:57 UTC
e50f219 Merge branch '1594-dbus-docs' into 'master' gdbusconnection: Add missing (nullable) annotation to get_unique_name() Closes #1594 See merge request GNOME/glib!475 19 November 2018, 21:57:19 UTC
2ded434 Check for 'z' library before fallbacking to subproject 19 November 2018, 20:22:16 UTC
11847b8 Merge branch 'g-once-data-race' into 'master' gthread: Remove unsynchronized access to g_once_init_list from assertion See merge request GNOME/glib!477 19 November 2018, 19:11:41 UTC
c2b22bd gthread: Synchronize access to g_once_init_list 19 November 2018, 18:41:50 UTC
9874006 Merge branch 'patch-1' into 'master' docs: add a missing semicolon See merge request GNOME/glib!480 18 November 2018, 12:29:56 UTC
fccce84 docs: add a missing semicolon 18 November 2018, 08:05:28 UTC
8a96fca Merge branch 'autolist-chainup' into 'master' Add support for g_auto(s)list to G_DECLARE'd types See merge request GNOME/glib!413 15 November 2018, 10:25:41 UTC
5cc6942 gdbusconnection: Add missing (nullable) annotation to get_unique_name() Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1594 15 November 2018, 09:42:33 UTC
8d42b02 gobject, tests: add tests for autoptr (and lists) with declared Add tests using an object declared with G_DECLARE_FINAL_TYPE, that is derived from another, declared using G_DECLARE_DERIVABLE_TYPE, and that thus uses _GLIB_DEFINE_AUTOPTR_CHAINUP to define cleanup functions. And verify that both g_autoptr(Type) and g_auto(s)list(Type) work 15 November 2018, 04:47:39 UTC
86c073d gmacros: remove duplication on autoptr cleanup definition Define _GLIB_DEFINE_AUTOPTR_CLEANUP_FUNCS and reuse it for both _GLIB_DEFINE_AUTOPTR_CHAINUP and G_DEFINE_AUTOPTR_CLEANUP_FUNC 15 November 2018, 04:47:39 UTC
d58be1b gmacros: make _GLIB_DEFINE_AUTOPTR_CHAINUP to define funcs for g_autolist Also chainup to glib_(s)listautoptr_cleanup_* parent functions to make g_autolist work with object defined in this way 14 November 2018, 20:41:40 UTC
9534447 Merge branch 'fix-gio-test-build' into 'master' Meson: Fix build error in gdbus-example-objectmanager See merge request GNOME/glib!461 14 November 2018, 15:37:05 UTC
ba2c519 Meson: Rename test_c_args to avoid confusion with gio tests c_args 14 November 2018, 14:38:33 UTC
a72766b Merge branch 'master' into 'master' meson: add aarch64 memory barrier handling See merge request GNOME/glib!462 13 November 2018, 18:47:29 UTC
6375476 Merge branch 'gmain-tsan' into 'master' gmain: Fix data races in GUnixSignalWatchSource and GChildWatchSource See merge request GNOME/glib!446 13 November 2018, 16:04:12 UTC
704522c meson: add aarch64 memory barrier handling memory barriers for aarch64 ref: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.den0024a/CJAIAJFI.html 13 November 2018, 16:00:09 UTC
9e5a8ba Merge branch 'gdate-parse-month' into 'master' gdate: Use longest matching month name in g_date_set_parse Closes #1343 See merge request GNOME/glib!433 13 November 2018, 15:00:36 UTC
dd36cf3 gmain: Indicate atomic fields with a comment 13 November 2018, 13:57:45 UTC
969b0e0 gmain: Guarantee handler dispatch after receiving UNIX signal Guarantee that user signal callback is dispatched _after_ receiving a signal as long as the handler expresses continued interest in receiving such a notification. Previously if a signal has been received during user callback dispatch but before pending flag had been cleared then the signal would be irrevocably lost. This is a very useful guarantee to have in cases where signals are used to signify a need for synchronization with external resources. For example: reloading configuration file after SIGUSR1 or retrieving a terminal size after SIGWINCH. 13 November 2018, 13:57:27 UTC
9e652f9 gmain: Make GUnixSignalWatchSource pending field atomic Ensure synchronization between prepare / check /dispatch of GUnixSignalWatchSource and UNIX signal dispatcher by making operations on `pending` field atomic. Issue #1312. 13 November 2018, 13:57:22 UTC
6f84f68 Merge branch 'mr285-subscription-docs' into 'master' docs: Clarify return/error behaviour of D-Bus signal subscriptions See merge request GNOME/glib!470 13 November 2018, 13:57:02 UTC
d2fd53d gmain: Make GChildWatchSource child_exited field atomic Ensure synchronization between prepare / check of GChildWatchsource and UNIX signal dispatcher by making operations on `child_exited` field atomic. Use `child_exited` as publication flag for `child_status`. Issue #1312. 13 November 2018, 13:52:50 UTC
1c8f3c6 gmain: Remove redundant volatile from unix_signal_refcount Acesss to unix_signal_refcount is protected by unix_signal_lock. 13 November 2018, 13:52:50 UTC
ba18822 gdate: Use longest matching month name in g_date_set_parse There are languages where a name of one month is a substring of another. Instead of stopping search on the first match use the month that constitutes the longest match. Fixes #1343. 13 November 2018, 13:43:34 UTC
e014898 Merge branch 'tests-tsan' into 'master' tests: Fix some data races in tests See merge request GNOME/glib!453 13 November 2018, 13:12:38 UTC
2a52ff1 Merge branch 'settings-list-does-not-exist' into 'master' Clarify docs for g_settings_list_children Closes #1362 See merge request GNOME/glib!465 13 November 2018, 12:54:41 UTC
c63d37f docs: Clarify return/error behaviour of D-Bus signal subscriptions Based on a patch by David Sommerseth, from https://gitlab.gnome.org/GNOME/glib/merge_requests/285/. Signed-off-by: Philip Withnall <withnall@endlessm.com> 13 November 2018, 12:44:34 UTC
b323635 Merge branch 'wjt/g-file-info-filesystem-readonly-fails' into 'master' Improve tests/g-file-info-filesystem-readonly, and run it in CI. Closes #1590 See merge request GNOME/glib!466 13 November 2018, 12:38:18 UTC
1520afb ci: document how to update the Docker image By making run-docker.sh to `cd` to the correct directory, we don't need to document that step. 13 November 2018, 10:40:44 UTC
ab892ac ci: add bindfs and fuse to Fedora CI image Without `bindfs` and `fusermount`, all tests in g-file-info-filesystem-readonly.c are skipped. 13 November 2018, 10:37:46 UTC
a2f32f6 tests/g-file-info-filesystem-readonly: remove output stream stuff This test is intended to verify the fix for https://bugzilla.gnome.org/show_bug.cgi?id=787731, which was that g_file_query_filesystem_info() would return stale information for the mount. After replacing a read-only mount with a read-write mount, this test used to only fail if G_FILE_ATTRIBUTE_FILESYSTEM_READONLY was TRUE and yet the file could be opened for writing. In particular, if (due to a test bug) the file really was still on a read-only filesystem, the test would pass. Now that we have fixed that bug in the test, we can make a stronger assertion. 13 November 2018, 10:34:09 UTC
5b106cd tests/g-file-info-filesystem-readonly: unmount lazily fusermount -z behaves like umount --lazy, which is documented thus: > Detach the filesystem from the file hierarchy now, and clean up all > references to this filesystem as soon as it is not busy anymore. Without this, the call to `fusermount -u` often fails with: /usr/bin/fusermount: failed to unmount /home/wjt/src/gnome/glib/_build/dir_bindfs_mountpoint: Device or resource busy which causes the subsequent call to bindfs to fail: fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option It's not clear what is causing the mount to be busy. Inserting a g_usleep (100 * 1000) before the calls to `fusermount -u` also works to make the problem go away, but for the purposes of this test the important point is that the mount is detached from the directory, for which a lazy unmount is fine. Fixes #1590. 13 November 2018, 10:34:09 UTC
3821ba0 tests/g-file-info-filesystem-readonly: assert subcommands succeed In practice, fusermount -u often fails: /usr/bin/fusermount: failed to unmount /home/wjt/src/gnome/glib/_build/dir_bindfs_mountpoint: Device or resource busy which causes the subsequent calls to bindfs to fail: fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option This may or may not cause the current test run to fail, but it reliably causes a repeat run of the test to fail. This change causes the current run to fail instead. 13 November 2018, 10:34:09 UTC
cb174e6 Merge branch 'wip/tintou/gio-symbols-index-update' into 'master' docs: add index of new symbols for gio > 2.52 See merge request GNOME/glib!469 13 November 2018, 10:11:21 UTC
e835961 Merge branch '1261-settings-documentation' into 'master' gsettings: Add an example of a <default> with an empty string Closes #1261 See merge request GNOME/glib!468 13 November 2018, 10:10:32 UTC
c7ac6f3 docs: add index of new symbols for gio > 2.52 13 November 2018, 07:08:14 UTC
bc320d9 gsettings: Add an example of a <default> with an empty string Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1261 13 November 2018, 00:31:54 UTC
f81a2b3 Merge branch 'mcatanzaro/tls1.3-handshake' into 'master' Update documentation of g_tls_connection_handshake() again See merge request GNOME/glib!467 12 November 2018, 23:50:16 UTC
68878ab Update documentation of g_tls_connection_handshake() again I made a mistake when last updating the documentation in 94a99ae9. I wrote that, with TLS 1.3, this would perform a rekey instead of a rehandshake. In fact, that's only true for client connections. For server connections, it's a no-op. I was a bit nervous about how to document the behavior anyway, because we really don't know what behavior will be reasonable with non-GnuTLS crypto backends. This behavior is reasonable for the GnuTLS backend, but might not necessarily make sense for OpenSSL. Ideally, we would discourage API users from doing things which could have unexpected effects, so instead of documenting what the GnuTLS backend does, I think it'd be better to document that this is "undefined but not dangerous," since of course we want to make sure that existing code that doesn't know about TLS 1.3 is not broken. 12 November 2018, 20:49:30 UTC
bb1f765 Clarify docs for g_settings_list_children The docs sound like settings list is a thing, and a ::children-changed signal exists. That is not the case, and will never be the case at this point, so stop pretending. Closes: #1362 12 November 2018, 13:07:52 UTC
e990a9f Merge branch '107-key-file-comment-line-breaks' into 'master' gkeyfile: Fix parsing of new lines in comments Closes #107 See merge request GNOME/glib!432 12 November 2018, 12:57:24 UTC
378be29 Merge branch 'dont-memoize-in-g_log_writer_is_journald' into 'master' gmessages: don't memoize in g_log_writer_is_journald() Closes #1589 See merge request GNOME/glib!464 12 November 2018, 12:54:49 UTC
4ea5695 Merge branch 'issues/1310' into 'master' gdbusproxy: make g-name-owner property useful with unique names See merge request GNOME/glib!454 12 November 2018, 12:43:27 UTC
4af8edb Merge branch 'master' into 'master' gio, tests: fix leak of dbus connection. See merge request GNOME/glib!463 12 November 2018, 12:13:55 UTC
f117570 gmessages: don't memoize in g_log_writer_is_journald() Previously, g_log_writer_is_journald() would cache the result for the first (non-negative) FD it was called on, and return that result for all future (non-negative) FDs. While unlikely, it's possible that applications might call this function on something other than fileno(stderr). Move the memoization into g_log_writer_default(), which always passes fileno(stderr). Fixes #1589. 12 November 2018, 11:20:49 UTC
bf1a2d7 gio, tests: fix leak of dbus connection. ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// 1- Start server gio/tests/.libs/gdbus-example-peer --server --address unix:abstract=/tmp/peer/myaddr 2- Check the open fds for server process lsof -a -p 8253 .................. gdbus-exa 8253 imran 0u CHR 136,1 0t0 4 /dev/pts/1 gdbus-exa 8253 imran 1u CHR 136,1 0t0 4 /dev/pts/1 gdbus-exa 8253 imran 2u CHR 136,1 0t0 4 /dev/pts/1 gdbus-exa 8253 imran 3u 0000 0,9 0 6602 anon_inode gdbus-exa 8253 imran 4u unix 0xf1005680 0t0 966830 @/tmp/peer/myaddr 3- Run the client gio/tests/.libs/gdbus-example-peer --address unix:abstract=/tmp/peer/myaddr 4- Check the open fds for server process again lsof -a -p 8253 .................. gdbus-exa 8253 imran 0u CHR 136,1 0t0 4 /dev/pts/1 gdbus-exa 8253 imran 1u CHR 136,1 0t0 4 /dev/pts/1 gdbus-exa 8253 imran 2u CHR 136,1 0t0 4 /dev/pts/1 gdbus-exa 8253 imran 3u 0000 0,9 0 6602 anon_inode gdbus-exa 8253 imran 4u unix 0xf1005680 0t0 966830 @/tmp/peer/myaddr gdbus-exa 8253 imran 5u unix 0xf1004280 0t0 965811 @/tmp/peer/myaddr gdbus-exa 8253 imran 6u 0000 0,9 0 6602 anon_inode 5- Please note the fd '5u' which is created when client makes connection but even when the client goes down, the descriptor is still there.. /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// https://bugzilla.gnome.org/show_bug.cgi?id=734281 12 November 2018, 06:45:20 UTC
fcda663 Updated Lithuanian translation 10 November 2018, 15:51:22 UTC
47be0f7 gdbusproxy: make g-name-owner property useful with unique names Currently, GDBusProxy:g-name-owner only notifies changes to the unique name owner of the remote object in case the proxy was constructed for a well-known name. That sounds like an artificial restriction, and it's convenient to connect to notify::g-name-owner if a proxy instance has already been created for an unique name, instead of additionally using g_bus_watch_name() to track the owner. To fix this, always connect to NameOwnerChanged after the proxy is initialized, instead of only doing so when the proxy was constructed for a well-known name. https://bugzilla.gnome.org/show_bug.cgi?id=791316 https://gitlab.gnome.org/GNOME/glib/issues/1310 10 November 2018, 03:53:32 UTC
b3c899d Meson: Fix build error in gdbus-example-objectmanager test_c_args is defined in the root meson.build with unfiltered list of compiler flags, then redefined in gio/tests/meson.build after the subdir() call. Move it before. 09 November 2018, 18:23:43 UTC
0c6346c Merge branch 'atomic-ref-count-cnd' into 'master' Atomic reference count in GVariant, ContainerInfo and GDBus introspection See merge request GNOME/glib!452 08 November 2018, 14:22:03 UTC
0ef8dde Merge branch '1342-gvariant-alignment' into 'master' gvariant: Realign data on construction if it’s not properly aligned Closes #1342 See merge request GNOME/glib!455 07 November 2018, 16:55:50 UTC
55934a0 Merge branch 'vmlobanov78/glib-patch-2' into 'master' glib-compile-resources: Fix size allocation for compressed streams See merge request GNOME/glib!458 07 November 2018, 10:01:16 UTC
54549b7 Merge branch 'arm-closures-timeout' into 'master' closures test: Avoid timeout on ARM64 CPUs See merge request GNOME/glib!451 Reviewed-by: pwithnall 06 November 2018, 20:39:41 UTC
348b5ea Update Turkish translation 06 November 2018, 19:52:17 UTC
36cf465 Update Polish translation 06 November 2018, 16:23:27 UTC
0985e70 glib-compile-resources: Fix size allocation for compressed streams The length of the stolen data from a memory output stream is given by get_data_size() — get_size() can be larger, and hence cause unnecessary overallocation. 06 November 2018, 15:03:03 UTC
cb98e37 closures test: Avoid timeout on ARM64 CPUs Closures use a 16-bit atomic reference count, which is really slow on certain ARM64 CPUs such as the Cortex-A57 (glib#1316). This is non-trivial to solve, since the public struct field cannot be enlarged to 32-bit while preserving ABI, and 16-bit atomic operations would be new (and rather niche) API. Until this can be solved properly (hopefully in GLib 2.59.x), cut down the number of signal emission cycles and bump up the timeout in the Meson build system, so that builds won't time out. We can't just take another zero off the number of signal emission cycles, as was done in the original version of this patch in Debian, because if we do that it can result in test failures when the main thread starves the other threads. ARM64 CPUs are backwards-compatible with 32-bit ARM, and the same slowdown can be seen when building and testing 32-bit code on these CPUs, so check for both 32- and 64-bit ARM. Bug-Debian: https://bugs.debian.org/880883 Co-authored-by: Iain Lane <laney@debian.org> Signed-off-by: Simon McVittie <smcv@debian.org> 06 November 2018, 13:48:34 UTC
b599a0f gdbusintrospection: Use atomic operations to read ref_count 06 November 2018, 13:44:40 UTC
b5a41af gvarianttypeinfo: Use gatomicrefcount for ContainerInfo reference count 06 November 2018, 13:44:25 UTC
6d10858 gvariant-core: Use gatomicrefcount for GVariant reference count 06 November 2018, 13:39:19 UTC
409ff69 gvariant: Re-use g_variant_serialised_check() to check alignment Rather than duplicating the alignment checks when constructing a new GVariant, re-use the alignment checks from GVariantSerialised. This ensures that the same checks are done everywhere in the GVariant code. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1342 06 November 2018, 12:49:25 UTC
a3ad5a2 Merge branch 'bookmarkfile-self-move' into 'master' bookmarkfile: Don't move an item if the uri has not changed Closes #1588 See merge request GNOME/glib!456 06 November 2018, 12:21:19 UTC
7b0f2e0 gvariant: Fix some GIR annotations on internal functions Signed-off-by: Philip Withnall <withnall@endlessm.com> 06 November 2018, 11:50:20 UTC
0f2a6c6 gvariant: Realign data on construction if it’s not properly aligned Otherwise the GVariant would later fail internal alignment checks, aborting the program. If unaligned data is provided to (for example) g_variant_new_from_data(), it will copy the data into a new aligned allocation. This is slow, but better than crashing. If callers want better performance, they should provide aligned data in their call, and it will not be copied or reallocated. Includes a unit test. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1342 06 November 2018, 11:50:20 UTC
cfd1649 gbookmarkfile: remove trailing spaces 05 November 2018, 23:15:42 UTC
821d280 bookmarkfile: Don't move an item if the uri has not changed This was causing a crash, because we were first removing an item, freeing both the instance itself and the key, and then trying to reuse those. So, in this case, instead of reassigning an item, we can just return TRUE as we have already the item at the right place, while it's not needed to update the modified timestamp, since no modification happened in reality. Fixes #1588 05 November 2018, 23:15:32 UTC
94edafb bookmarkfile: test that moving to the same name works Verify that we can move a bookmark item to the same name, but actually this causes a crash right now. 05 November 2018, 23:06:52 UTC
68e78c6 tests: Fix data races in gwakeuptest.c 04 November 2018, 16:28:58 UTC
1cc7457 tests: Fix data races in refcount/signals.c 04 November 2018, 16:28:51 UTC
8322167 tests: Fix data races in refcount/closures.c 04 November 2018, 16:28:43 UTC
b09a0df Merge branch '1576-meson-armv5-atomic' into 'master' meson: Define __GCC_HAVE_SYNC_COMPARE_AND_SWAP_4 on GNU/Linux if needed Closes #1576 See merge request GNOME/glib!434 02 November 2018, 20:56:37 UTC
73a982f Merge branch 'wip/sadiq/likely' into 'master' gmacros: Fix G_[UN]LIKELY to not mask -Wparentheses See merge request GNOME/glib!372 02 November 2018, 20:45:38 UTC
5c7e64a Merge branch 'supp' into 'master' valgrind: Add glib_init()-related suppressions See merge request GNOME/glib!436 02 November 2018, 20:34:53 UTC
74d2a8e Merge branch 'test-timeout' into 'master' meson: Increase test timeouts See merge request GNOME/glib!407 02 November 2018, 11:02:32 UTC
8f115b6 Merge branch 'atomic-ref-count' into 'master' gvarianttypeinfo: Consistently use atomics to access ref_count See merge request GNOME/glib!444 02 November 2018, 10:29:48 UTC
7d4fb4d Merge branch 'g-test-rand-int-range-race' into 'master' tests: Avoid multithreaded use of g_test_rand_int_range See merge request GNOME/glib!443 02 November 2018, 10:21:20 UTC
aed3c00 gtestutils: Make test_rand_* thread-safe within a single test case Synchronize access to random number generator `test_run_rand` with a lock to ensure that `g_test_rand_*` family of functions is thread-safe. The reseeding taking place between test case runs is intentionally left unsynchronized. It is an error to continue using random number generator after test case has already finished running. Lack of synchronization here will make such erroneous use readily apparent with thread sanitizer. 02 November 2018, 07:29:08 UTC
03518e5 gvarianttypeinfo: Consistently use atomics to access ref_count 01 November 2018, 20:55:07 UTC
03413d5 meson: Mark gdatetime test as slow This test isn't inherently slow, but it produces so much output that it can take a minute or more on hardware with weak I/O performance. Signed-off-by: Simon McVittie <smcv@collabora.com> 01 November 2018, 19:13:21 UTC
a40ef2f meson: Increase fast test timeout from 30s to 60s This is enough for most Debian buildds, including embedded devices like mips and powerpcspe. It is not enough for hppa (PA-RISC), but that architecture is so uniquely slow that it might make more sense to special-case it downstream. Signed-off-by: Simon McVittie <smcv@collabora.com> 01 November 2018, 19:13:21 UTC
13e206a meson: Centralize test timeout values Signed-off-by: Simon McVittie <smcv@collabora.com> 01 November 2018, 19:13:21 UTC
d3f5559 Merge branch '1575-revert-strftime-format' into 'master' Revert "gdatetime: Enable compile time check of g_date_time_format() format" Closes #1575 See merge request GNOME/glib!442 01 November 2018, 18:12:41 UTC
e1056e5 Update Slovak translation (cherry picked from commit 985210849ceb926485656e8eddf8995b72de4ee5) 01 November 2018, 18:05:52 UTC
664fb63 Revert "gdatetime: Enable compile time check of g_date_time_format() format" This reverts commits: • 9ddcc79502349e02a1e796b363d891e177337af5 • ae02adc3c3795bb32348c07d8f48504b41e9e2c7 g_date_time_format() supports a few non-standard format placeholders: • %:z • %::z • %:::z These are all gnulib strtime() extensions, and hence are not recognised by the compiler when the function is annotated with G_GNUC_STRFTIME. However, this wasn’t noticed when we originally merged this change because the errors were disabled in the tests which covered those placeholders. 01 November 2018, 16:12:32 UTC
9ddcc79 Remove the G_GNUC_STRFTIME format check This does not work, since g_date_time_format() supports non-standard extensions such as %:::z, and this has broken several consumers which use format errors, such as ostree. 01 November 2018, 16:00:58 UTC
bfc661a Merge branch 'tests-memory-leaks' into 'master' Fix minor memory leaks in tests See merge request GNOME/glib!440 01 November 2018, 11:59:59 UTC
b7571d5 tests: Fix GVariantType leak in GAction tests 01 November 2018, 11:15:09 UTC
52bab02 tests: Fix GOptionContext leak in GSubprocess tests 01 November 2018, 11:14:52 UTC
9347c76 tests: Fix GRand leak in GMenuModel tests 01 November 2018, 11:14:09 UTC
afce4ef Merge branch 'flags_validation_fix' into 'master' gobject/genums.c: fix flags validation Closes #1572 See merge request GNOME/glib!401 01 November 2018, 10:46:29 UTC
aa1415c Add unit test for flags validation 31 October 2018, 22:41:32 UTC
1d6c784 gobject/genums.c: fix flags validation gint -> glong conversion causes flags to be invalid if the highest bit is set. Closes #1572 31 October 2018, 22:41:32 UTC
back to top