-
Notifications
You must be signed in to change notification settings - Fork 90
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 #4206: allow root folders named '/' #4207
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4207 +/- ##
========================================
Coverage 37.68% 37.69%
========================================
Files 768 768
Lines 35321 35326 +5
Branches 5021 5214 +193
========================================
+ Hits 13312 13317 +5
+ Misses 21402 20775 -627
- Partials 607 1234 +627
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
We have a customer with a lot of data in a path like "s3://bucket//raw". I presume the check was in place to prevent accidentally entering an absolute path. Should we drop it entirely, or provide a warning? |
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.
generally seems right
needs tests
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.
looks reasonable in general. i defer to @sir-sigurd on this one
Co-authored-by: Sergey Fedoseev <[email protected]>
…iltdata/quilt into 4206-allow-root-folders-named
allow initial '/'
Description
set_dir: Allow '/' folder in root.