-
Notifications
You must be signed in to change notification settings - Fork 422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP 500 on get permissions (ValueError) #2687
Comments
Hello @AlexB1986, thank you for your feedbacks, are you planning to send us pull-requests to issues that you are filling? If yes, I would recommend to create pull-request in between new issues. |
Hi, Can I work on this issue? |
@AlexB1986 Can you please provide more info to replicate the issue? I tried with your endpoint but I couldn't reproduce it |
@s-surineni Hi! I retested on new Kinto docker image 14.4.0.dev0 (in 2020 I tested on 14.0.1.dev0)-- I can not reproduce it. Seems it was fixed. |
I don't think there were much changes in that part of the code over this period of time. The error suggests it comes from a specific content in the DB. Somewhere somehow a permission with only 2 parts is stored and it eventually crashes the perm endpoint when retrieving it with |
|
is this issue still open?? |
@Abhishek-jha-96 yes, feel free to reproduce and fix 🙏 |
So while trying to reproduce this issue |
I believe you need a valid token to be able to access the page. |
Are you using the memory backend? It seems to happen only with it according to the stacktrace. |
yes, because by default(in the doc) backend option is memory backend |
Perfect then, let's close it. |
I'm a bit surprised though, because the line still exists: https://github.com/Kinto/kinto/blob/master/kinto/core/permission/memory.py#L101 |
then I guess I am unable to reproduce it. its gives 200 ok status but |
Steps to reproduce
docker run -p 8888:8888 kinto/kinto-server
Running kinto 14.0.1.dev0.
Request
Response
Log:
The text was updated successfully, but these errors were encountered: