Skip to content
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

Support request_delay meta value in client #1247

Open
ml-evs opened this issue Jun 15, 2022 · 0 comments
Open

Support request_delay meta value in client #1247

ml-evs opened this issue Jun 15, 2022 · 0 comments
Assignees
Labels
client Issues/PRs relating to the OPTIMADE client. help wanted Extra attention is needed OPTIMADE v1.2 This label describes actions that have to be taken to be complient with OPTIMADE 1.2 priority/low Issue or PR with a consensus of low priority
Milestone

Comments

@ml-evs
Copy link
Member

ml-evs commented Jun 15, 2022

Now that Materials-Consortia/OPTIMADE#411 is merged, the client should obey the request_delay field for all requests, as well as the standard HTTP Retry After in cases where a 429 Too Many Requests has been returned.

@ml-evs ml-evs added priority/low Issue or PR with a consensus of low priority client Issues/PRs relating to the OPTIMADE client. labels Jun 15, 2022
@ml-evs ml-evs self-assigned this Jun 15, 2022
@ml-evs ml-evs added the OPTIMADE v1.2 This label describes actions that have to be taken to be complient with OPTIMADE 1.2 label Jun 29, 2022
@ml-evs ml-evs added this to the OPTIMADE v1.2 milestone Dec 6, 2022
@ml-evs ml-evs added the help wanted Extra attention is needed label Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client Issues/PRs relating to the OPTIMADE client. help wanted Extra attention is needed OPTIMADE v1.2 This label describes actions that have to be taken to be complient with OPTIMADE 1.2 priority/low Issue or PR with a consensus of low priority
Projects
None yet
Development

No branches or pull requests

1 participant