Funny how the same problem keep coming back: https://pagure.io/pagure/issue/4978
Yeah, I think someone should configure the bot. I have no idea how to use it, but I moved it to the room where it was invited earlier by someone.
Ok so it finally work, the last step is to create a alias on fedora.im and not my server, and then I will be able to update the config and merge it. Then move that to Fedora repo and cluster in…
So thanks to folks from Element, the issue is due to not having device attached to the access key (documenting to our LLM overload can claim to diagnose the issue later).
Ok, so for the record, after discussing on Matrix, the bot is now running on a separate room on my server, and I think we will change the alias and get people to join the new room.
Ok so after discussing with EMS folks that directed to use https://admin-beta.element.dev/, the latest code given by @kevin seems to work, but now, the bot crash with:
Now, it goes back to M_UNKNOWN_TOKEN (so I guess it expired). It seems the SDK used do not support renewing the token, but the bug say…
So it work (for how long, I do not know as I assume the token need to be renewed). However, now it crash with:
We can try the token given by default OAuth scope (eg, urn:matrix:org.matrix.msc2967.client:api:*) and test how it goes. I assume the mat_ prefix is a opaque identifier, so that shouldn't be…
I deployed it, but the token seems to not work. I tested with fedora.ems.host and fedoraproject.ems.host, same error message. If I test with curl directly, I have the same error code:
So, if we want to deploy, I need a access key. I have the rest. If people can give it to me, either on matrix, or our internal chat, I will do the deployment (likely later today, or tomorrow…