-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
fix: LEAP-860: have GCS generate data URLs if presign is disabled #5968
Conversation
✅ Deploy Preview for heartex-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for label-studio-docs-new-theme ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #5968 +/- ##
===========================================
- Coverage 76.06% 76.04% -0.02%
===========================================
Files 162 162
Lines 13469 13475 +6
===========================================
+ Hits 10245 10247 +2
- Misses 3224 3228 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Make GCS behave the same way as S3 import storages, in that when presign isn't enabled for the storage, we return data URLs containing b64-encoded data instead of presigned URLs in task data.
We don't have any unit tests that simulate fetching real data from GCS and while this code should have them, setting up a mock GCS is too large to be in-scope for this task, so I've carefully verified the behavior locally instead.