summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix Since tag.arnaudb/option-flag-append-empty-lineArnaud Bonatti2019-09-121-1/+1
|
* Add G_OPTION_FLAG_APPEND_EMPTY_LINEArnaud Bonatti2019-09-122-4/+12
| | | | | This flag adds in --help output an empty line after the line of the option, allowing to visually group options.
* Merge branch 'doc-win' into 'master'Xavier Claessens2019-09-111-2/+7
|\ | | | | | | | | | | | | Fix doc build on Windows Closes #1888 See merge request GNOME/glib!1092
| * Fix doc build on WindowsXavier Claessens2019-09-091-2/+7
| | | | | | | | | | | | | | This is a work around for this Meson bug: https://github.com/mesonbuild/meson/issues/5893 Closes: #1888
* | Merge branch 'root-test-fix' into 'master'Nirbheek Chauhan2019-09-101-0/+1
|\ \ | | | | | | | | | | | | tests: Fix skipping mkdir-with-parents-permission test See merge request GNOME/glib!1080
| * | tests: Fix skipping mkdir-with-parents-permission testPhilip Withnall2019-09-021-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the user has `CAP_DAC_OVERRIDE` or similar (for example, if running the tests as root), the `mkdir-with-parents-permission` test is skipped. The check for `CAP_DAC_OVERRIDE` was by creating a subdirectory of the test directory. That subdirectory, however, was never removed, which caused a ‘directory not empty’ error when trying to delete the test directory. Fix that by correctly deleting the subdirectory if skipping the test. Signed-off-by: Philip Withnall <withnall@endlessm.com>
* | | Merge branch 'fix_a_misunderstanding_in_gtypeaddinterface' into 'master'Nirbheek Chauhan2019-09-101-2/+2
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | docs: fix a misunderstanding in g_type_add_interface_* Closes #259 See merge request GNOME/glib!1077
| * | | docs: fix a misunderstanding in g_type_add_interface_*Steve Frécinaux2019-09-041-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The previous documentation said this: g_type_add_interface_static: "Adds the static interface_type to instantiable_type" g_type_add_interface_dynamic: "Adds the dynamic interface_type to instantiable_type" The above suggests that if one is adding a static interface to a dynamic object, one should use g_type_add_interface_static because the interface is static, but the code and usage (with the newly added G_IMPLEMENTS_INTERFACE_DYNAMIC) imply that this is wrong, and that what matters is whether the *instanciable_type* is dynamic or not. Hence this patch moves the "static" and "dynamic" words close to "instantiable_type". Closes issue #259
* | | | Update Punjabi translationA S Alam2019-09-091-1803/+3646
| | | | | | | | | | | | | | | | (cherry picked from commit e75a6b546f6c7a447851f0f517ed65f0a190c551)
* | | | Merge branch 'remove-gmodule-dyld' into 'master'Sebastian Dröge2019-09-074-159/+0
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | gmodule: remove macOS dyld implementation See merge request GNOME/glib!1093
| * | | | gmodule: remove macOS dyld implementationTom Schoonjans2019-09-074-159/+0
|/ / / / | | | | | | | | | | | | | | | | It did not work for dylibs, was full of ancient, deprecated code, and was not actually used anyway.
* | | | Merge branch 'fix-gmodule-macos' into 'master'Nirbheek Chauhan2019-09-073-7/+29
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gmodule: use dl implementation on macOS Closes #1887 See merge request GNOME/glib!1091
| * | | | gmodule: write test for shared librariesTom Schoonjans2019-09-062-5/+27
| | | | |
| * | | | gmodule: use dl implementation on macOSTom Schoonjans2019-09-061-2/+2
| | |_|/ | |/| | | | | | | | | | Closes #1887
* | | | Update Turkish translationEmin Tufan Çetin2019-09-071-681/+736
|/ / /
* | | Merge branch 'io-create-watch-docs' into 'master'Sebastian Dröge2019-09-061-0/+3
|\ \ \ | | | | | | | | | | | | | | | | giochannel: Clarify type of GSource callback in documentation See merge request GNOME/glib!1090
| * | | giochannel: Clarify type of GSource callback in documentationPhilip Withnall2019-09-061-0/+3
|/ / / | | | | | | | | | | | | | | | | | | This should clarify questions like https://stackoverflow.com/q/57807738/2931197. Signed-off-by: Philip Withnall <withnall@endlessm.com>
* | | Update Italian translationMilo Casagrande2019-09-061-811/+755
| | |
* | | 2.62.02.62.0Philip Withnall2019-09-052-1/+18
| | | | | | | | | | | | Signed-off-by: Philip Withnall <withnall@endlessm.com>
* | | Merge branch 'wip/chergert/fix-modification-date-time' into 'master'Philip Withnall2019-09-052-24/+90
|\ \ \ | | | | | | | | | | | | | | | | fileinfo: ignore USEC if not available See merge request GNOME/glib!1087
| * | | tests: Add tests for GFileInfo modification timePhilip Withnall2019-09-051-0/+61
| | | | | | | | | | | | | | | | Signed-off-by: Philip Withnall <withnall@endlessm.com>
| * | | tests: Use g_assert_*() rather than g_assert() in g-file-info testPhilip Withnall2019-09-051-22/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | They provide more detailed failure messages, and aren’t compiled out when building with `G_DISABLE_ASSERT`. Signed-off-by: Philip Withnall <withnall@endlessm.com>
| * | | fileinfo: ignore USEC if not availableChristian Hergert2019-09-051-2/+7
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When future porting deprecated code to use g_file_info_get_modification_date_time() we risk a number of breakages because the current implementation also requires the additional use of G_FILE_ATTRIBUTE_TIME_MODIFIED_USEC. This handles that situation gracefully and returns a GDateTime with less precision. Applications that want the additional precision, are already using the additional attribute. (Minor tweaks by Philip Withnall.)
* | | Update Brazilian Portuguese translationRafael Fontenelle2019-09-051-440/+411
| | |
* | | Merge branch 'gobject_init-suppression' into 'master'Philip Withnall2019-09-041-1/+1
|\ \ \ | |/ / |/| | | | | | | | glib.supp: make gobject_init() calloc also of the possible kind See merge request GNOME/glib!1086
| * | glib.supp: make gobject_init() calloc also of the possible kindClaudio Saavedra2019-09-041-1/+1
|/ / | | | | | | | | | | | | | | | | | | | | | | | | It's currently marked only as reachable but Valgrind also finds it as possible: ==18842== 96 bytes in 1 blocks are possibly lost in loss record 2,029 of 2,284 ==18842== at 0x4837B65: calloc (vg_replace_malloc.c:762) ==18842== by 0x49614AD: g_malloc0 (gmem.c:129) ==18842== by 0x4A7013B: type_node_any_new_W (gtype.c:439) ==18842== by 0x4A70609: type_node_fundamental_new_W (gtype.c:550) ==18842== by 0x4A7855A: gobject_init (gtype.c:4406) ==18842== by 0x4A78672: gobject_init_ctor (gtype.c:4493)
* | Update Friulian translationFabio Tomat2019-09-031-723/+735
| |
* | Merge branch 'fix-sizeof-check' into 'master'Philip Withnall2019-09-021-1/+1
|\ \ | | | | | | | | | | | | garray: Fix reference to GLIB_SIZEOF_INT See merge request GNOME/glib!1084
| * | garray: Fix reference to GLIB_SIZEOF_INTAlexander Larsson2019-09-021-1/+1
| | | | | | | | | | | | This doesn't ever get set. SIZEOF_INT is set though, so use that instead.
* | | Merge branch '487-ci-memcheck' into 'master'Sebastian Dröge2019-09-028-18/+142
|\ \ \ | |/ / |/| | | | | | | | | | | | | | Add CI job for running tests under Valgrind Closes #487 See merge request GNOME/glib!169
| * | tests: Fix some minor memory leaks in testsPhilip Withnall2019-09-022-3/+8
| | | | | | | | | | | | Signed-off-by: Philip Withnall <withnall@endlessm.com>
| * | glib.supp: Add some fundamental type suppressionsPhilip Withnall2019-09-021-0/+18
| | | | | | | | | | | | Signed-off-by: Philip Withnall <withnall@endlessm.com>
| * | glib.supp: Fix some indentationPhilip Withnall2019-09-021-5/+5
| | | | | | | | | | | | Signed-off-by: Philip Withnall <withnall@endlessm.com>
| * | glib.supp: Add leak typesPhilip Withnall2019-09-021-1/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Mark all the memcheck leaks as ‘reachable’, so the suppressions will not apply if that memory is no longer reachable on exit(). This feature was introduced in Valgrind 3.9, and is documented here: http://valgrind.org/docs/manual/mc-manual.html#mc-manual.suppfiles Signed-off-by: Philip Withnall <withnall@endlessm.com>
| * | tests: Don’t run Python tests under ValgrindPhilip Withnall2019-09-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | The Python runtime is not amenable to Valgrind, and leak checking is a lot less relevant in Python compared to C. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #487
| * | ci: Include stderr output in JUnit XML reportPhilip Withnall2019-09-021-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When running tests under valgrind, the valgrind summary is printed in stderr, and the TAP output is printed in stdout. The valgrind summary is useful to include in the GitLab test report, so append it to the textual failure information for failed tests. I can’t find a better XML element in the [JUnit schema](https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd) for representing it. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #487
| * | ci: Add valgrind memcheck support on FedoraPhilip Withnall2019-09-022-2/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a separate CI job which runs memcheck on the unit tests. This is done as a separate job from the main build, since we don’t want it to interact with code coverage at all. Currently, failure of this job is ignored. Issue #333 will eventually fix that. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #487
| * | ci: Add valgrind to fedora Docker imagePhilip Withnall2019-09-022-5/+6
| | | | | | | | | | | | | | | | | | | | | | | | It will be used in an upcoming commit. Signed-off-by: Philip Withnall <withnall@endlessm.com> Helps: #487
| * | gerror: Add a docs paragraph about not displaying errors verbatim in UIPhilip Withnall2019-09-021-0/+7
| | | | | | | | | | | | | | | | | | | | | It’s confusing and often doesn’t help the user. Match the error code and come up with a more UI-appropriate error message. Signed-off-by: Philip Withnall <withnall@endlessm.com>
* | | 2.61.32.61.3Philip Withnall2019-09-021-0/+76
| |/ |/| | | | | Signed-off-by: Philip Withnall <withnall@endlessm.com>
* | Merge branch 'ossfuzz-16101-iso8601-parsing' into 'master'Emmanuele Bassi2019-09-022-6/+118
|\ \ | | | | | | | | | | | | Improve ISO 8601 parsing by GDateTime See merge request GNOME/glib!1017
| * | tests: Add ISO 8601 parsing tests for g_date_time_new_from_iso8601()Philip Withnall2019-08-211-0/+107
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These are copies of the existing tests for `g_time_val_from_iso8601()`, with the test strings which fail for `GDateTime` commented out. This is OK, as it’s documented as only accepting a subset of ISO 8601 (and for some of the test vectors, it’s debatable whether they’re actually valid ISO 8601, depending on how you interpret the valid bounds of timezone offsets — some interpretations of the available documentation would say that timezone offsets should never be ≥24 hours or ≥60 minutes). There is one test string which is not accepted by `g_time_val_from_iso8601()` but which is accepted by `GDateTime`, as `g_date_time_new_from_iso8601()` actually accepts RFC 3339, which is a little more liberal than ISO 8601. Fun times. See https://tools.ietf.org/html/rfc3339#section-5.6. Signed-off-by: Philip Withnall <withnall@endlessm.com>
| * | gdatetime: Avoid an assertion failure when parsing some ISO 8601 datesPhilip Withnall2019-08-212-6/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some malformed ISO 8601 date/time strings were causing an assertion failure when passed to `g_date_time_new_from_iso8601()`, due to a mismatch between the bounds checking of timezone offsets in `GDateTime` and `GTimeZone`. Fix that and add a unit test for it. oss-fuzz#16101 Signed-off-by: Philip Withnall <withnall@endlessm.com>
* | | Merge branch '1309-delayed-settings-changed' into 'master'Emmanuele Bassi2019-09-022-0/+20
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | gsettings: Add missing changed() call to delayed settings backend Closes #1309 See merge request GNOME/glib!1046
| * | | gsettings: Add missing changed() call to delayed settings backendPhilip Withnall2019-08-212-0/+20
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | When resetting a key in the delayed settings backend, g_settings_backend_changed() was not called to notify the backend of the change. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #1309
* | | Merge branch 'wip/lantw/gthread-set-thread-name-on-bsd' into 'master'Philip Withnall2019-09-022-3/+29
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | gthread: Set thread name on *BSD Closes #1761 See merge request GNOME/glib!1072
| * | | gthread: Set thread name on *BSDTing-Wei Lan2019-08-302-3/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add support for setting thread name on FreeBSD, DragonFlyBSD, OpenBSD, and NetBSD. Fixes https://gitlab.gnome.org/GNOME/glib/issues/1761
* | | | Updated Czech translationMarek Černocký2019-09-021-675/+713
| | | |
* | | | Updated Lithuanian translationAurimas Černius2019-09-011-100/+66
| | | |
* | | | Update Korean translationChangwoo Ryu2019-09-011-665/+706
| | | |
View Lorry Controller Status