Peter Chubb
Peter Chubb
You just connect: ``` uri='ws://user:password@host/api' websocket = await connect(uri) ``` If digest auth is enabled on the server, the connect method will respond to the challenge and insert a new...
It's a little more complex than that. The `Authorization`: header to be sent changes on each request, so it can't be calculated just once. What's more the server can issue...
More debugging --- loaded `libpython-3.9d.so` with debugging syms; the bug is because we're trying to release the curent thread.
Commenting out the call to `PyThreadState_Clear(tstate);` near line 306 of `mod_python.c` makes the issue go away. There is only one documented change for this function: from Python 3.9 on it...
This could be related to #100
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975608 which has a patch attached for the Debian version.
Try converting to bytes and back. I find I need: ``` query = util.parse_qs(req.args.encode(encoding='utf-8')) newquery = {} for q in query: val = query[q][0].decode('utf-8')1 newquery[q.decode('utf-8')] = [val] query = newquery...
This appears to be a gcc bug. There's no way to make the gcc-12 accept this code with `-Warray-bounds=1` or `-Warray-bounds=2`
OK, after more investigation: Try adding ``` # gcc-12 assumes pointers into the first page are always errors. # Allow low pointers by making the assumed page size 0. --param=min-pagesize=0...
Fixed with https://github.com/seL4/seL4/pull/904