summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* gnotification: Add g_notification_set_sound_file()wip/tingping/notification-soundsPatrick Griffis2018-11-184-0/+65
|
* gnotification: Add g_notification_set_soundPatrick Griffis2018-11-175-0/+82
|
* Merge branch 'autolist-chainup' into 'master'Philip Withnall2018-11-154-11/+200
|\ | | | | | | | | Add support for g_auto(s)list to G_DECLARE'd types See merge request GNOME/glib!413
| * gobject, tests: add tests for autoptr (and lists) with declaredMarco Trevisan (Treviño)2018-11-143-0/+183
| | | | | | | | | | | | | | | | 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
| * gmacros: remove duplication on autoptr cleanup definitionMarco Trevisan (Treviño)2018-11-141-19/+17
| | | | | | | | | | Define _GLIB_DEFINE_AUTOPTR_CLEANUP_FUNCS and reuse it for both _GLIB_DEFINE_AUTOPTR_CHAINUP and G_DEFINE_AUTOPTR_CLEANUP_FUNC
| * gmacros: make _GLIB_DEFINE_AUTOPTR_CHAINUP to define funcs for g_autolistMarco Trevisan (Treviño)2018-11-141-3/+11
|/ | | | | Also chainup to glib_(s)listautoptr_cleanup_* parent functions to make g_autolist work with object defined in this way
* Merge branch 'fix-gio-test-build' into 'master'Xavier Claessens2018-11-142-14/+14
|\ | | | | | | | | Meson: Fix build error in gdbus-example-objectmanager See merge request GNOME/glib!461
| * Meson: Rename test_c_args to avoid confusion with gio tests c_argsXavier Claessens2018-11-141-7/+7
| |
| * Meson: Fix build error in gdbus-example-objectmanagerXavier Claessens2018-11-091-7/+7
| | | | | | | | | | | | 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.
* | Merge branch 'master' into 'master'Xavier Claessens2018-11-131-1/+1
|\ \ | | | | | | | | | | | | meson: add aarch64 memory barrier handling See merge request GNOME/glib!462
| * | meson: add aarch64 memory barrier handlingNiclas Moeslund Overby2018-11-131-1/+1
| | | | | | | | | | | | memory barriers for aarch64 ref: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.den0024a/CJAIAJFI.html
* | | Merge branch 'gmain-tsan' into 'master'Philip Withnall2018-11-132-19/+66
|\ \ \ | | | | | | | | | | | | | | | | gmain: Fix data races in GUnixSignalWatchSource and GChildWatchSource See merge request GNOME/glib!446
| * | | gmain: Indicate atomic fields with a commentTomasz Miąsko2018-11-131-2/+2
| | | |
| * | | gmain: Guarantee handler dispatch after receiving UNIX signalTomasz Miąsko2018-11-132-2/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | gmain: Make GUnixSignalWatchSource pending field atomicTomasz Miąsko2018-11-131-10/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ensure synchronization between prepare / check /dispatch of GUnixSignalWatchSource and UNIX signal dispatcher by making operations on `pending` field atomic. Issue #1312.
| * | | gmain: Make GChildWatchSource child_exited field atomicTomasz Miąsko2018-11-131-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | gmain: Remove redundant volatile from unix_signal_refcountTomasz Miąsko2018-11-131-1/+1
| | | | | | | | | | | | | | | | Acesss to unix_signal_refcount is protected by unix_signal_lock.
* | | | Merge branch 'gdate-parse-month' into 'master'Philip Withnall2018-11-132-44/+65
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gdate: Use longest matching month name in g_date_set_parse Closes #1343 See merge request GNOME/glib!433
| * | | | gdate: Use longest matching month name in g_date_set_parseTomasz Miąsko2018-11-132-44/+65
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | Merge branch 'mr285-subscription-docs' into 'master'Philip Withnall2018-11-131-0/+5
|\ \ \ \ | |/ / / |/| | | | | | | | | | | docs: Clarify return/error behaviour of D-Bus signal subscriptions See merge request GNOME/glib!470
| * | | docs: Clarify return/error behaviour of D-Bus signal subscriptionsPhilip Withnall2018-11-131-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | | | Merge branch 'tests-tsan' into 'master'Philip Withnall2018-11-133-28/+17
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | tests: Fix some data races in tests See merge request GNOME/glib!453
| * | | | tests: Fix data races in gwakeuptest.cTomasz Miąsko2018-11-041-11/+12
| | | | |
| * | | | tests: Fix data races in refcount/signals.cTomasz Miąsko2018-11-041-8/+4
| | | | |
| * | | | tests: Fix data races in refcount/closures.cTomasz Miąsko2018-11-041-9/+1
| | | | |
* | | | | Merge branch 'settings-list-does-not-exist' into 'master'Philip Withnall2018-11-131-10/+3
|\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | Clarify docs for g_settings_list_children Closes #1362 See merge request GNOME/glib!465
| * | | | Clarify docs for g_settings_list_childrenMatthias Clasen2018-11-121-10/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | | Merge branch 'wjt/g-file-info-filesystem-readonly-fails' into 'master'Philip Withnall2018-11-135-31/+84
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Improve tests/g-file-info-filesystem-readonly, and run it in CI. Closes #1590 See merge request GNOME/glib!466
| * | | | | ci: document how to update the Docker imageWill Thompson2018-11-132-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | By making run-docker.sh to `cd` to the correct directory, we don't need to document that step.
| * | | | | ci: add bindfs and fuse to Fedora CI imageWill Thompson2018-11-133-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Without `bindfs` and `fusermount`, all tests in g-file-info-filesystem-readonly.c are skipped.
| * | | | | tests/g-file-info-filesystem-readonly: remove output stream stuffWill Thompson2018-11-131-13/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | | | tests/g-file-info-filesystem-readonly: unmount lazilyWill Thompson2018-11-131-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | | | tests/g-file-info-filesystem-readonly: assert subcommands succeedWill Thompson2018-11-131-16/+55
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | Merge branch 'wip/tintou/gio-symbols-index-update' into 'master'Philip Withnall2018-11-131-0/+12
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | docs: add index of new symbols for gio > 2.52 See merge request GNOME/glib!469
| * | | | | docs: add index of new symbols for gio > 2.52Corentin Noël2018-11-131-0/+12
| | | | | |
* | | | | | Merge branch '1261-settings-documentation' into 'master'Philip Withnall2018-11-131-0/+5
|\ \ \ \ \ \ | |/ / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | gsettings: Add an example of a <default> with an empty string Closes #1261 See merge request GNOME/glib!468
| * | | | | gsettings: Add an example of a <default> with an empty stringPhilip Withnall2018-11-131-0/+5
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/1261
* | | | | Merge branch 'mcatanzaro/tls1.3-handshake' into 'master'Philip Withnall2018-11-121-2/+4
|\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | Update documentation of g_tls_connection_handshake() again See merge request GNOME/glib!467
| * | | | Update documentation of g_tls_connection_handshake() againMichael Catanzaro2018-11-121-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | Merge branch '107-key-file-comment-line-breaks' into 'master'Philip Withnall2018-11-122-13/+35
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gkeyfile: Fix parsing of new lines in comments Closes #107 See merge request GNOME/glib!432
| * | | | | gkeyfile: Fix parsing of new lines in commentsPhilip Withnall2018-10-302-13/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, the code which parsed comments in key files would append a line break to the comment where there was none before; this was part of the code for handling re-inserting line breaks into multi-line comments after removing the ‘#’ prefix. Now, we don’t add a terminal line break. This was slightly icky to implement because parse_value_as_comment() is called once for each line of a multi-line comment. This expands the existing test case to cover a single line comment, and also fixes the documentation to correctly state that the leading ‘#’ *is* removed and mention the new line break behaviour. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/glib/issues/107
* | | | | | Merge branch 'dont-memoize-in-g_log_writer_is_journald' into 'master'Philip Withnall2018-11-121-20/+22
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gmessages: don't memoize in g_log_writer_is_journald() Closes #1589 See merge request GNOME/glib!464
| * | | | | | gmessages: don't memoize in g_log_writer_is_journald()Will Thompson2018-11-121-20/+22
| | |_|/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | | Merge branch 'issues/1310' into 'master'Philip Withnall2018-11-124-3/+220
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | gdbusproxy: make g-name-owner property useful with unique names See merge request GNOME/glib!454
| * | | | | | gdbusproxy: make g-name-owner property useful with unique namesCosimo Cecchi2018-11-104-3/+220
| | |_|_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | | | Merge branch 'master' into 'master'Philip Withnall2018-11-121-0/+11
|\ \ \ \ \ \ | |_|/ / / / |/| | | | | | | | | | | | | | | | | gio, tests: fix leak of dbus connection. See merge request GNOME/glib!463
| * | | | | gio, tests: fix leak of dbus connection.INSUN PYO2018-11-121-0/+11
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// 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
* | | | | Updated Lithuanian translationAurimas Černius2018-11-101-256/+259
| |_|_|/ |/| | |
* | | | Merge branch 'atomic-ref-count-cnd' into 'master'Philip Withnall2018-11-083-29/+28
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Atomic reference count in GVariant, ContainerInfo and GDBus introspection See merge request GNOME/glib!452
| * | | | gdbusintrospection: Use atomic operations to read ref_countTomasz Miąsko2018-11-061-14/+14
| | | | |
View Lorry Controller Status