-
Notifications
You must be signed in to change notification settings - Fork 847
feat: serve cached digest if available #462
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
Conversation
MickaelCa
commented
Jul 27, 2025
- Added methods to upload metadata alongside digest files to S3.
- Implemented S3-based digest caching mechanism for improved efficiency.
- Refactored digest storage logic to support both S3 and local storage.
⚙️ Preview environment was undeployed. |
5b757ee
to
655c0ba
Compare
acb00ea
to
dd6e541
Compare
dd6e541
to
579894d
Compare
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.
RGPD
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.
If we ingest a repo hello_world
then try to ingest it again with include/exclude patterns the cache is not used ?
Anyway, LGTM !
Combine steps to resolve and assign commit in query_processor.
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.
RPDC
fine for now going with simple check 404, can easily switch back if needed