We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Tutorial (https://giftless.datopian.com/en/latest/quickstart.html) does not work as raise following error occured.
INFO 127.0.0.1 - - "POST /my-organization/test-repo/objects/batch HTTP/1.1" 200 - INFO 127.0.0.1 - - "PUT /my-organization/test-repo/objects/storage/30e14955ebf1352266dc2ff8067e68104607e750abb9d3b36582b8af909fcb58 HTTP/1.1" 200 - INFO 127.0.0.1 - - "POST /my-organization/test-repo/objects/storage/verify HTTP/1.1" 200 -
2022-11-24 08:08:40,040 werkzeug INFO * Running on http://127.0.0.1:12789 (Press CTRL+C to quit) 2022-11-24 08:09:09,525 werkzeug INFO 127.0.0.1 - - [24/Nov/2022 08:09:09] "POST /my-organization/test-repo/locks/verify HTTP/1.1" 404 - 2022-11-24 08:09:09,533 werkzeug ERROR 127.0.0.1 - - [24/Nov/2022 08:09:09] code 400, message Bad request syntax ('{"ref":{"name":"refs/heads/master"}}') 2022-11-24 08:09:09,533 werkzeug INFO 127.0.0.1 - - [24/Nov/2022 08:09:09] "None /my-organization/test-repo/locks/verify HTTP/0.9" HTTPStatus.BAD_REQUEST -
So, How can I solve this issue? I think /my-organization/test-repo/locks/verify path does not exist.
/my-organization/test-repo/locks/verify
The text was updated successfully, but these errors were encountered:
I also experienced this issue.
Sorry, something went wrong.
FIXED. I believe this got fixed in #115 so closing ... Feel free to re-open if this reappears.
svetozarstojkovicdatopian
No branches or pull requests
Tutorial (https://giftless.datopian.com/en/latest/quickstart.html)
does not work as raise following error occured.
So, How can I solve this issue?
I think
/my-organization/test-repo/locks/verify
path does not exist.The text was updated successfully, but these errors were encountered: