-
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
[24.0] Fix History Dataset Association creation so that hid is always set #18036
Merged
jdavcs
merged 12 commits into
galaxyproject:release_24.0
from
mvdbeek:implicit_conversion_no_hid_fix
Apr 23, 2024
Merged
Changes from 1 commit
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
b1333e0
Also perform strict checks for new database objects
mvdbeek 1b1094b
Set (copied) output hid before queuing job
mvdbeek e3aba2d
Relax requirement for DCEs of collections that are not populated
mvdbeek 5648478
Adjust schema for collection elements of collections that aren't popu…
mvdbeek bf34997
Fix unitialize typo
mvdbeek 5aecc08
Fall back to populated method if collection not committed yet
mvdbeek d889002
Commit only after copying library item to history
mvdbeek e1a45a2
Drop unused copy_from_ldda method
mvdbeek a56f642
Drop unused method
mvdbeek badbd3a
Fix premature flush in hda_manager.copy
mvdbeek c2140bd
Avoid flush in set_meta by using MetadataFile.uuid
mvdbeek 121f27e
Default HID to -1 if for whatever reason we didn't record a HID
mvdbeek 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
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.
Isn't that what
versioned_objects_strict()
does? If so, why not do something like this: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 creates a version, which doesn't make sense for new objects.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.
Ah, yes, I could do that, though it's not related to versioning objects, which is what threw my off in your comment.
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.
And then, if I'm not mistaken, you wouldn't need this
if/then
that checksos.environ
and contains 2 similar function definitions, and just use the existing logic, I think? i.e., settingversioned_objects = versioned_objects_strict
would still work?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 don't think one is better than the other with the exception this one is slightly better since we don't run the os.environ check in the module space ?