Commits on Source (23)
-
Ignacio Casal Quinteiro authored
Otherwise we are translating even if it is not needed and they will show in the profiler. Partially fixes #188
0e933937 -
Ignacio Casal Quinteiro authored
Otherwise this becomes expensive when doing lots of read/writes and endups consuming quite a bit of CPU. Partially fixes #188 Part-of: <https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/210>
f31598c7 -
Nirbheek Chauhan authored
``` FAILED: subprojects/glib-networking/tls/tests/connection-openssl.p/connection.c.o ccache cc -Isubprojects/glib-networking/tls/tests/connection-openssl.p -Isubprojects/glib-networking/tls/tests -I../subprojects/glib-networking/tls/tests -Isubprojects/glib-networking -I../subprojects/glib-networking -Isubprojects/glib-networking/tls -I../subprojects/glib-networking/tls -Isubprojects/glib-networking/tls/openssl -I../subprojects/glib-networking/tls/openssl -Isubprojects/glib/gio -I../subprojects/glib/gio -Isubprojects/glib/gmodule -I../subprojects/glib/gmodule -Isubprojects/glib -I../subprojects/glib -Isubprojects/glib/glib -I../subprojects/glib/glib -Isubprojects/proxy-libintl -I../subprojects/proxy-libintl -Isubprojects/glib/gobject -I../subprojects/glib/gobject -fcolor-diagnostics -Wall -Winvalid-pch -O2 -g -DHAVE_CONFIG_H '-DG_LOG_DOMAIN="GLib-Net"' -DG_LOG_USE_STRUCTURED '-DLOCALE_DIR="/usr/local/share/locale"' -DG_DISABLE_DEPRECATED -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -Werror=declaration-after-statement -Werror=implicit-function-declaration '-DSRCDIR="/Users/nirbheek/projects/repos/gstreamer.git/1.20/subprojects/glib-networking/tls/tests"' '-DTOP_BUILDDIR="/Users/nirbheek/projects/repos/gstreamer.git/1.20/builddir"' '-DBACKEND="openssl"' -DBACKEND_IS_OPENSSL -MD -MQ subprojects/glib-networking/tls/tests/connection-openssl.p/connection.c.o -MF subprojects/glib-networking/tls/tests/connection-openssl.p/connection.c.o.d -o subprojects/glib-networking/tls/tests/connection-openssl.p/connection.c.o -c ../subprojects/glib-networking/tls/tests/connection.c In file included from ../subprojects/glib-networking/tls/tests/connection.c:40: ../subprojects/glib-networking/tls/openssl/openssl-include.h:46:10: fatal error: 'openssl/ssl.h' file not found ^~~~~~~~~~~~~~~ 1 error generated. ```
eb887265 -
Zurab Kargareteli authoredd5ed4a31
-
Olivier Crête authored
This way it can be used as a subproject Part-of: <https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/213>
2228cfb9 -
Michael Catanzaro authored
This just rebuilds the CI image with the latest Fedora. Also, we don't need to clone all of the history of GLib. Just need the latest commit.
b50f76cb -
Michael Catanzaro authored
We're currently exceeding the max log output length, which is not useful. Running the tests less often makes it harder to detect race conditions, but detecting problems does not good if we have no logs to see what they are, so the status quo 1000 runs is not useful. I first tried 100 runs, but we were still hitting the output length limit when we were approximately 20% through. So let's try just 10 runs. I fear this is too little to find unlikely race conditions, but it's better than reducing debug verbosity. Besides, the tests have been flaky for several years, and I haven't managed to fix them yet. The benefit of detecting flakiness is reduced if I don't do anything about it. This will also make our CI way faster.
3454aac3 -
Michael Catanzaro authored
Instead of blindly trusting the environment, let's make sure we have actually received proper URLs. An empty string will be assumed to mean "no proxy, please." Any empty environment variable will still cause all GNOME proxy settings to be ignored, because you might want to use an empty environment variable to temporarily suppress use of GNOME proxy settings without messing with XDG_CURRENT_DESKTOP. Helps with glib#2597 Fixes #189 Part-of: <https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/212>
10959c69 -
Michael Catanzaro authored
I've been waiting to do this for a long time! Part-of: <https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/212>
8bfbdf3a -
Michael Catanzaro authored
This adds an extra layer of safety to ensure our GProxyResolver only ever returns URIs that GLib considers valid. Otherwise, if libproxy returns something silly like an empty string, nothing prevents us from passing it along. Part-of: <https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/212>
962d2f3c -
Michael Catanzaro authored
If we have something silly stored in gsettings, we should reject it rather than pass it along to API users. This ensures we return only valid URIs or NULL. P.S. This also fixes a GError leak on an error path. Part-of: <https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/212>
3643009d -
Michael Catanzaro authoredc0d70917
-
Michael Catanzaro authored
If the banner warning not to second-guess our defaults is not enough for distros, hopefully this will help.
13d15234 -
Michael Catanzaro authoredaf191b18
-
Nart Tlisha authored215d7834
-
Michael Catanzaro authored
This is trendy, and we don't have to maintain our own container images anymore. https://freedesktop.pages.freedesktop.org/ci-templates/templates.html
ebcd3df8 -
Michael Catanzaro authored
Currently the environment proxy resolver has 100 priority. The portal resolver in GLib has 90 priority, the GNOME settings resolver has 80 priority, and the libproxy resolver is relegated to last place with 0 priority. Making the new environment proxy resolver highest-priority seemed like a good idea to me because environment variables are for debugging and surely if an environment variable is set it's because you want it to be respected, right? Wrong. Problem is, Console and Terminal both inspect GNOME proxy settings and translate them into environment variables, see console#81. If we prioritize the environment variables, which are unable to fully express the desktop configuration, then we lose out on goodies like web proxy autoconfig and such. Worse, this will only happen when running from your terminal, meaning applications will break only when run in Console or Terminal. Imagine how frustrating that would be to debug. Although I'm usually reluctant to make major behavior changes in a stable release, we should revert back to longstanding historical behavior. The environment proxy resolver will be used only as the last fallback, useful in case libproxy is not available. Fixes #190 Part-of: <https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/217>
6e2cf4fb -
Michael Catanzaro authored
Since fixing #190, the environment proxy resolver is now redundant with libproxy and there is no reason for it to be built or installed if libproxy is enabled. Accordingly, let's give it its own build option. It will be enabled by default if libproxy is enabled, and disabled by default otherwise. Part-of: <https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/217>
cb3f08fa -
Michael Catanzaro authored
Instead of hiding it behind a secret dummy value, let's implement the real deal. Also, remove some misplaced fallthrough comments. Depends on: glib!2853 Fixes #191
1d4cf09f -
Michael Catanzaro authored
This allows us to get rid of a bunch of old channel bindings code, and also some manual ciphersuite name computation.
3f11b0c3 -
Michael Catanzaro authored
The Windows CI will need to be updated to build the latest GLib.
593dd90e -
Michael Catanzaro authored77c9cee6
-
Jeremy Bicha authored96c1a9c9
.gitlab-ci/Dockerfile
deleted
100644 → 0
.gitlab-ci/README.md
deleted
100644 → 0
.gitlab-ci/run-docker.sh
deleted
100755 → 0
po/ab.po
0 → 100644
po/ka.po
0 → 100644