Google Git
Sign in
fuchsia / third_party / github.com / GNOME / glib / ba8e2c69fa97b17107b2097e404c18a997e747e6
commitba8e2c69fa97b17107b2097e404c18a997e747e6[log] [tgz]
authorSimon McVittie <smcv@debian.org>Mon May 06 21:24:53 2024 +0100
committerSimon McVittie <smcv@debian.org>Tue May 07 11:45:21 2024 +0100
tree11c6edaac19f1dd52b490412749d771eed52f8dc
parente942df7ebea0853abbd026ef2ebb1e3c836b2053 [diff]
gdbus-proxy test: Wait before asserting name owner has gone away

GDBusConnection sends each signal to recipients in a separate idle
callback, and there's no particular guarantee about the order in which
they're scheduled or dispatched. For the NameOwnerChanged signal that
reports the name becoming unowned, it's possible that g_bus_watch_name()
gets its idle callback called before the GDBusProxy:g-name-owner
machinery has updated the name owner, in which case the assertion
will fail.

Fixing GNOME/glib#3268 introduced a new subscription to NameOwnerChanged
which can alter the order of delivery, particularly in the case where
G_DBUS_PROXY_FLAGS_NO_MATCH_RULE was used (as tested in
/gdbus/proxy/no-match-rule). The resulting test failure is intermittent,
but reliably appears within 100 repetitions of that test.

Fixes: 511c5f5b "tests: Wait for gdbus-testserver to die when killing it"
Signed-off-by: Simon McVittie <smcv@debian.org>
1 file changed
tree: 11c6edaac19f1dd52b490412749d771eed52f8dc
  1. .gitlab-ci/
  2. .reuse/
  3. docs/
  4. fuzzing/
  5. gio/
  6. glib/
  7. gmodule/
  8. gobject/
  9. gthread/
  10. LICENSES/
  11. m4macros/
  12. po/
  13. subprojects/
  14. tests/
  15. tools/
  16. COPYING ⇨ LICENSES/LGPL-2.1-or-later.txt
  17. .clang-format
  18. .dir-locals.el
  19. .editorconfig
  20. .gitignore
  21. .gitlab-ci.yml
  22. .gitmodules
  23. .lcovrc
  24. CODE_OF_CONDUCT.md
  25. CONTRIBUTING.md
  26. glib.doap
  27. HACKING
  28. INSTALL.md
  29. meson.build
  30. meson_options.txt
  31. msvc_recommended_pragmas.h
  32. NEWS
  33. README.md
  34. README.win32.md
  35. SECURITY.md
README.md

GLib

GLib is the low-level core library that forms the basis for projects such as GTK and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.

The official download locations are: https://download.gnome.org/sources/glib

The official web site is: https://www.gtk.org/

Installation

See the file ‘INSTALL.md’

Supported versions

Only the most recent unstable and stable release series are supported. All older versions are not supported upstream and may contain bugs, some of which may be exploitable security vulnerabilities.

See SECURITY.md for more details.

Documentation

API documentation is available online for GLib for the:

Discussion

If you have a question about how to use GLib, seek help on GNOME’s Discourse instance. Alternatively, ask a question on StackOverflow and tag it glib.

Reporting bugs

Bugs should be reported to the GNOME issue tracking system. You will need to create an account for yourself. You may also submit bugs by e-mail (without an account) by e-mailing incoming+gnome-glib-658-issue-@gitlab.gnome.org, but this will give you a degraded experience.

Bugs are for reporting problems in GLib itself, not for asking questions about how to use it. To ask questions, use one of our discussion forums.

In bug reports please include:

  • Information about your system. For instance:
    • What operating system and version
    • For Linux, what version of the C library
    • And anything else you think is relevant.
  • How to reproduce the bug.
    • If you can reproduce it with one of the test programs that are built in the tests/ subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded.
  • If the bug was a crash, the exact text that was printed out when the crash occurred.
  • Further information such as stack traces may be useful, but is not necessary.

Contributing to GLib

Please follow the contribution guide to know how to start contributing to GLib.

Patches should be submitted as merge requests to gitlab.gnome.org. If the patch fixes an existing issue, please refer to the issue in your commit message with the following notation (for issue 123):

Closes: #123

Otherwise, create a new merge request that introduces the change. Filing a separate issue is not required.

Default branch renamed to main

The default development branch of GLib has been renamed to main. To update your local checkout, use:

git checkout master
git branch -m master main
git fetch
git branch --unset-upstream
git branch -u origin/main
git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main