x86pup
x86pup
We simply don't implement the endpoint at the moment.
Are you able to clarify if this is an issue with simplified sliding sync (syncv5), used by Element X, or normal syncv3 used by Element Web / etc?
Are you able to run a debug build and see if you can find any debug logs related that would help identify the issue more clearly?
This doesn't show any real error messages. I think I see a few places of where this error is coming from, but this is unfortunately legacy / potentially broken code...
I added some extended debug logging in this area, are you able to run a debug build and get debug and warn logs if this issue still happens? I also...
Okay I was able to get the logs of what I want now to know where this specific problem is coming from: ``` [2m2025-04-04T15:30:54.695700Z[0m [33m WARN[0m [1mrouter[0m[1m{[0m[3mmethod[0m[2m=[0mPOST [3mpath[0m[2m=[0m/_matrix/client/v3/keys/signatures/upload[1m}[0m[2m:[0m[1mrequest[0m[2m:[0m[1mhandle[0m[1m{[0m[3mactive[0m[2m=[0m0 [3mhandled[0m[2m=[0m313[1m}[0m[2m:[0m [2mconduwuit_service::users[0m[2m:[0m...
Has anyone validated if this proxy code still works in conduwuit? It's been pretty much untouched since we forked.
This was added recently into the example config.
This has been implemented in https://github.com/girlbossceo/conduwuit/pull/571 which is available in our main branch and will be in the next tagged release. We don't support PATCH at the moment, but GET/PUT/DELETE...
Leaving open until MSC4133 is merged