You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test: gate the comp-type-less time-range Run 2 on a ReportError rejection
CI failure on Cyrus: testSearchWithoutCompTypeWithDateRange's second run
forced search.time-range.comp-type-optional ON and asserted the event was
returned, relying on the reactive HTTP-400 fallback. But that fallback only
recovers from a ReportError (SabreDAV's 400) - Cyrus instead returns nothing
(CI) or 403 (locally), so the forced run either found nothing or crashed.
The forced "Run 2" is only meaningful where the raw comp-type-less time-range
query raises a ReportError (Baikal, Nextcloud). The test now probes the raw
behaviour first and only runs Run 2 in that case; other servers exercise just
the proactive split (Run 1). The reactive fallback itself remains covered
deterministically by the unit test.
#681
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
the httpx development seems stagnant, and httpx is even flagged as a
32
32
supply-chain risk in some Reddit-discussions. It seems like the http
33
-
user space is filled with drama and intrigues.
33
+
user space is filled with drama and intrigues. httpxyz is a
34
+
maintained fork of httpx. For async communication, the fallback chain
35
+
now is niquests, httpxyz and finally httpx if import of the former two
36
+
fails.
34
37
35
38
Fallbacks
36
39
---------
37
40
38
-
To enable the fallbacks, just ensure the requests and/or httpx library is available and that niquests isn't available. In virtual environments, fix the dependencies in `pyproject.toml`.
41
+
To enable the fallbacks, just ensure the requests and/or httpxyz/httpx library is available and that niquests isn't available. In virtual environments, fix the dependencies in `pyproject.toml`.
0 commit comments