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
I recently tried using Slurm-web 4.1.0. I'm trying to use the RacksDB integration, however when I go to the resources tab I see a message where I'd expect to see the drawing that says:
Server error: Request failed with status code 403
All the other endpoints seem to work fine. Using browser tools I can see that this call is not being sent a Bearer token while all other calls appear to be getting one.
The only thing I see in the logs on the system itself is a message that says:
uwsgi[835945]: uWSGIWorker5Core0: [WARNING] Unauthorized access without bearer token
The text was updated successfully, but these errors were encountered:
This is clearly a bug, it is visible since the release of RFL v1.3.0 which brings a few changes in the way requests without bearer token are managed. I will probably release a v4.1.1 to fix this bug soon.
Hello @thatguy24601, I published Slurm-web packages 4.1.0-2 and 3.2.0-2 with a patch to fix this bug. Can you update your packages to check it is fixed for you?
I recently tried using Slurm-web 4.1.0. I'm trying to use the RacksDB integration, however when I go to the resources tab I see a message where I'd expect to see the drawing that says:
Server error: Request failed with status code 403
All the other endpoints seem to work fine. Using browser tools I can see that this call is not being sent a Bearer token while all other calls appear to be getting one.
The only thing I see in the logs on the system itself is a message that says:
uwsgi[835945]: uWSGIWorker5Core0: [WARNING] Unauthorized access without bearer token
The text was updated successfully, but these errors were encountered: