Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Jeroen Hofstee <jhofstee@victronenergy.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Jeroen Hofstee <jhofstee@victronenergy.com>
|
|
Reproduces: https://github.com/firewalld/firewalld/issues/985
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
get_allow_interactive_authorization for message
add unit tests
|
|
Python 2 reached EOL on 2020-01-01, and the latest version of
AX_PYTHON_DEVEL breaks the build with Python 2. This seems as good a
time as any to drop compatibility.
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
It is deprecated and no longer necessary.
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Back in the days of PyGTK, there was only the gobject module, containing
bindings for both GLib and GObject. This is no longer the case.
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
The latest version of tappy dropped Python 2 support, but I want to be
able to continue to run dbus-python tests on Python 2 for now.
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
This lets us catch them in the test code.
Fixes: e9f658d9d57b97395545c5ed2eaf9a85436f135d
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
See https://gitlab.freedesktop.org/dbus/dbus-python/issues/26
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Casting via void (*)(void) is the documented way to suppress this
warning. This is required because the CPython API treats function
pointers as generic, with flags to indicate different calling
conventions.
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
There is a race condition here between these chains of events, which as
far as I can tell has existed for at least 10 years:
* server receives Tests.Trigger() and schedules SignalTests.Triggered
* server returns to main loop
* server emits SignalTests.Triggered
* client receives SignalTests.Triggered
and
* server receives Tests.Trigger() and replies with success
* client receives success and emits SignalTests.Trigger
* server receives SignalTests.Trigger and calls CallbackTests.Response()
* client receives CallbackTests.Response() and calls Tests.Exit()
* server receives Tests.Exit() and replies with success
* client quits its main loop
If we don't reply to Tests.Trigger() until after the SignalTests.Triggered
signal has been sent, because the client called Tests.Trigger()
asynchronously, messages are not re-ordered and the reply arrives after
the signal; so the whole chain of events leading up to
"client receives SignalTests.Triggered" happens before
"client receives success and emits SignalTests.Trigger" and there is
no race condition.
Bug-Debian: https://bugs.debian.org/898158
|
|
On a slow machine under load, communication might legitimately take time.
After the default method-call timeout (25 seconds) we'll go into
quit_error_handler() and exit anyway.
Bug-Debian: https://bugs.debian.org/898158
|
|
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
Python 3.6.0a4 is meant to have fixed this.
This reverts commit 1013581fef91c9be087d6264084cec34c2ca6e9a.
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
It hasn't had security support for about 3 years.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
This is a workaround for <http://bugs.python.org/issue27736>.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
For now this means that skipped tests will be reported as passed.
This will be corrected in the next commit.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
Python 2.6 didn't allow struct.pack(u'...', ...).
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=57140
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
Now that dbus.__version__ and dbus.version exist even in uninstalled
builds, we can do this.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
This means we can consistently #include <dbus/dbus-python.h>,
either in-tree or out-of-tree.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
|
|
|
|
|
|
|
|
Fall back to Telepathy's old with-session-bus.sh script if dbus doesn't
have dbus-run-session (versions < 1.8).
Also run most of the tests individually, instead of under run-test.sh.
|
|
|
|
|
|
|
|
Now that Python 2.6 isn't a supported version in Debian, it doesn't
get a gi module, but we can still get some minimal test coverage.
|
|
We used to reject noncharacters, but now we accept them.
|
|
See <https://bugs.freedesktop.org/show_bug.cgi?id=63119>.
|
|
|