spantaleev
commented
2 months ago Despite the bot having done its avatar setup already, it can't know its current avatar is what it expects it to be, so it does a profile check (preparation) every time it starts. If it notices that its name is out-of-sync with the configuration, or its avatar is not what it expects it to be (there's a single image hardcoded in the binary), it will update its profile.
So it checking its profile on every startup is not an issue. It's supposed to do it successfully.
Does it keep retrying unsuccessfully for you?
You can try enabling more verbose logging (trace) and see if you get anything else.
It's odd that it's getting a "not found" error. It almost sounds like the homeserver is down, but.. it shouldn't be, because before the profile preparation work, the underlying library (mxlink) actually does a "who am I" check to ensure the access token is still valid. So the homeserver should have been confirmed working just a moment ago before trying to prepare the profile.
dreamtwi
The first login was successful. However, on the second login attempt, since the avatar was already created during the first login, the process continuously repeats and gets stuck in the following error: 2024-09-21T15:02:16.359433Z DEBUG ThreadId(01) baibot::bot::implementation: src/bot/implementation.rs:264: Preparing profile.. 2024-09-21T15:02:17.259867Z WARN ThreadId(01) baibot::bot::implementation: src/bot/implementation.rs:249: Failed to prepare profile.. Will retry after delay... err=Failed fetching existing avatar: Http(Api(Server(ClientApi(Error { status_code: 404, body: Standard { kind: NotFound, message: "Not found" } })))) delay=3s
The homeserver I used is matrix.org