-
Notifications
You must be signed in to change notification settings - Fork 81
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
adding revision for assets creation path #1988
Conversation
The documentation is not available anymore as the PR was closed or merged. |
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1988 +/- ##
==========================================
- Coverage 90.82% 89.71% -1.12%
==========================================
Files 234 162 -72
Lines 14788 9264 -5524
==========================================
- Hits 13431 8311 -5120
+ Misses 1357 953 -404
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM ! and the already existing assets will keep working indeed since we store the full URLs :)
Yes I think so
The revision for assets is set to "main" so it should overwrite the files every time, but IIUC it will have the same issue with cloudfront still serving the old files ? In this case we should use the right revision (git commit sha) and have a mechanism to clean the outdated directory in the first-rows jobs maybe ? or a cron job, not sure what's the easiest |
I would like to send another PR before merging this one to ensure that now dataset "version" is mandatory, so that I can remove the optionals here.
No, for assets it will apply the revision as well https://github.com/huggingface/datasets-server/pull/1988/files#diff-4072a6f63a7fdcc185cb1170651d53216c3db8db2b5d2374db9e7974d648e2e5R229 so, no problem with CloudFront. |
good idea |
ArgoCD Diff for commit
|
Legend | Status |
---|---|
✅ | The app is synced in ArgoCD, and diffs you see are solely from this PR. |
The app is out-of-sync in ArgoCD, and the diffs you see include those changes plus any from this PR. | |
🛑 | There was an error generating the ArgoCD diffs due to changes in this PR. |
Fix for #1981
As suggested by @lhoestq in #1981 (comment) , adding dataset version (revision) as part of assets path:
Open questions for upcoming PRs: