-
Notifications
You must be signed in to change notification settings - Fork 7
Adopt FileLike for more pipeline APIs #7134
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
Merged
Merged
Changes from all commits
Commits
Show all changes
49 commits
Select commit
Hold shift + click to select a range
fde4925
More file path improvements, mostly around pipeline jobs
labkey-jeckels 92cb958
Distinguish between failures
labkey-jeckels 6c4aacc
Test fixes,
labkey-jeckels 4a95775
Test fixes, fix line endings
labkey-jeckels 5c8aea2
Merge branch 'develop' into fb_pipelineFileLike
labkey-jeckels 7943797
Test fixes
labkey-jeckels 5c84742
More FileLike
labkey-jeckels 1590fbc
Merge branch 'develop' into fb_pipelineFileLike
labkey-jeckels e873cdd
Merge branch 'develop' into fb_pipelineFileLike
labkey-jeckels 0d1736f
Fix build
labkey-jeckels 1bb78a4
Test fixes
labkey-jeckels 10eb9b1
Get rid of new validation causing StackOverflowError
labkey-jeckels b3cd207
CloudStoreService.getFileLike()
labkey-matthewb 0ccca75
zip to the .zip
labkey-matthewb 9ddb5c1
PipeRootImpl.ensureSystemDirectory()
labkey-matthewb 513396e
Try returning S3 FileLike from getRootFileLike(). Are we ready?
labkey-matthewb f9b0cd3
Merge branch 'develop' into fb_pipelineFileLike
labkey-jeckels a2b6552
Test fixes
labkey-jeckels 7d84a25
Avoid File conversion
labkey-jeckels 5eb6e29
Try to support OutputStream
labkey-jeckels 0184353
Merge branch 'refs/heads/develop' into fb_pipelineFileLike
labkey-jeckels 0c5ae92
Removed unused variables, improve test credential handling, refresh b…
labkey-jeckels 2c07190
Serialize FileSystemBlobStore._FileLike
labkey-matthewb 37a9ad6
Serialize FileSystemBlobStore._FileLike
labkey-matthewb d92e8e9
Merge remote-tracking branch 'origin/develop' into fb_pipelineFileLike
labkey-matthewb c1cfda5
Issue 54156: Assay XAR with transform script can't be edited if the t…
labkey-jeckels 3a6eb4d
Fix exists() check
labkey-jeckels fe1eef5
Fix sequence setting on crazy key names
labkey-jeckels d76b2d5
Merge branch 'develop' into fb_pipelineFileLike
labkey-jeckels 709f99b
Test coverage for 54156, test code cleanup
labkey-jeckels 75b6feb
Merge branch 'develop' into fb_pipelineFileLike
labkey-jeckels 9f200e2
build(DeserializationContext ctx)
labkey-matthewb 616592c
Merge remote-tracking branch 'origin/fb_pipelineFileLike' into fb_pip…
labkey-jeckels 5e38a4c
Fix line endings
labkey-jeckels aa10113
Minor cleanup
labkey-jeckels a6413dd
Merge branch 'develop' into fb_pipelineFileLike
labkey-jeckels 7a70323
Delete dead code, avoid using reflection
labkey-jeckels 97cf1c9
Merge branch 'develop' into fb_pipelineFileLike
labkey-jeckels ad0e21e
Troubleshoot
labkey-jeckels 1fa36bf
Troubleshoot
labkey-jeckels b0431e5
Troubleshoot
labkey-jeckels b564a5f
Troubleshoot
labkey-jeckels 42656ea
Troubleshoot
labkey-jeckels 70fbf49
Troubleshoot
labkey-jeckels cb8e272
Nulls are great
labkey-jeckels 5125134
Unix-style relative paths
labkey-jeckels fd76eeb
Dial back logging
labkey-jeckels b1823b8
Merge branch 'develop' into fb_pipelineFileLike
labkey-jeckels 9b24eed
Refresh from develop
labkey-jeckels File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
It looks like there is a direct path from SaveProtocolAction to here, however it's not clear that any FS specific permissions have been validated. Should there be a version of FileSystemLike.wrap (or this new?) method take a user or proof of authorization for user events? (we could also have an .unsafe() to mimic usages elsewhere e.g. SQLFragment() and HtmlString()).
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.
See the check here:
platform/assay/src/org/labkey/assay/AssayDomainServiceImpl.java
Line 544 in f35fed5
It would be nice to switch to mandating that all scripts be placed in the special WebDav
@scriptsdirectory or in a module, at which pointAnalysisScriptcould use that as the root.I don't think that we can put a permission check at this level as the user who is executing the script by uploading assay data may not have the permissions to configure the script in the first place.
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.
https://www.labkey.org/home/Developer/issues/issues-details.view?issueId=54185