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

Improve technical routes response #454

Merged
merged 11 commits into from
Jul 22, 2022
Merged

Conversation

severo
Copy link
Collaborator

@severo severo commented Jul 22, 2022

No description provided.

severo added 11 commits July 22, 2022 17:04
It serves no purpose since we can get more with
https://huggingface.co/api/datasets
we will instead expose the cache contents, and let the API users do this
kind of analysis by theirselves
/webhook is the way to do, and we refresh a dataset, not a specific
split (it's too internal to expose)
it is too heavy (the server times out) because it returns the whole list
of the past jobs. It was only used externally to do stats about the
duration of the jobs, which is not that important, and can be added to
prometheus better if needed.
only report for the new cache entries: /splits-next and /first-rows,
since /splits and /rows will be deprecated soon. Also: reduce the size
of the response to avoid timeouting. The client can fetch the complete
response by querying the corresponding endpoint if needed (to get the
cause message or the cause traceback for example)
@HuggingFaceDocBuilderDev
Copy link

HuggingFaceDocBuilderDev commented Jul 22, 2022

The documentation is not available anymore as the PR was closed or merged.

@severo severo merged commit bfe2900 into main Jul 22, 2022
@severo severo deleted the improve-technical-routes-response branch July 22, 2022 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants