-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Let file sources choose a path for uploaded files #19154
Open
kysrpex
wants to merge
5
commits into
galaxyproject:dev
Choose a base branch
from
kysrpex:file_sources_assign_paths
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
53012bf
Let file sources choose a path for uploaded files
kysrpex 5926778
Keep `BaseFilesSource` API backwards compatible
kysrpex a88ffd0
Introduce `FileSourceModelExportStore` abstraction
kysrpex 62c8955
Ignore mypy [arg-type] errors on unmodified functions
kysrpex 6fe9264
Merge branch 'dev' into file_sources_assign_paths
kysrpex 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 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 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 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 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.
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.
Before applying the set of changes from 53012bf, the method
ModelStoreManager.set_history_export_request_metadata()
instantiates aExportObjectMetadata
Pydantic model and dumps it to the database in the form of JSON as the fieldStoreExportAssociation.export_metadata
. After the export is complete, the methodset_history_export_result_metadata()
takes the same instance ofExportObjectMetadata
, instantiates aExportObjectResultMetadata
Pydantic model, sets it as theresult_data
of theExportObjectMetadata
instance, and then saves theExportObjectMetadata
Pydantic model in the form of JSON to the database again.After applying the set of changes, the call to
ModelStoreManager.set_history_export_request_metadata()
is delayed until the file has already been saved to the file source, as the actual URI that the file source assigns to the file is otherwise unknown.The URI assigned by the file source overwrites the original target URI in the request. This involves a slight deviation from the previous behavior: if for example, power gets cut at the right time,
StoreExportAssociation.export_metadata
may not exist despite the history having been already saved to the file source, because database writes happen within thefinally:
block.Moreover, overwriting the original target URI from the request is formally wrong, because the actual URI assigned by the file source should be part of the export result metadata, as it becomes known when the export completes. However, that implies modifying the other parts of the codebase that reference the URI from the request.
Despite the slight deviation in behavior and the formal incorrectness, rather than jumping straight into fixing these issues, I think it makes sense to leave the chance for discussion open, as doing things this way may still be an interesting tradeoff. Let me know what you think.
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.
I was thinking...
If we merge the PR as it is, then we'd never see an export that is in progress in the list from the UI. If the file is large, that alone would justify attempting to fix
right? I guess it makes sense to make an attempt.