[#18] close iRODSFS file handles before interpreter exit. #19
Conversation
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
Collaborator
Author
|
This will have a companion branch in my fork of Python iRODS Client, which commit/PR I will link to this discussion once that PR is ready. |
Collaborator
Author
|
See accompanying Pull Request at irods/python-irodsclient#611 |
Collaborator
Author
|
Converting to draft for the time being... |
If available, the irods.at_client_exit.register feature of the Python iRODS Client is called in an attempt to properly schedule the auto-closing (and therefore auto-flushing) of content written to iRODSFS handles before Python interpreter exit.
Collaborator
Author
|
See companion pull request irods/python-irodsclient#616 |
trel
reviewed
Aug 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Allows writes to iRODSFS-generated file handles to be automatically handled at the right time. If happening at interpreter exit due to auto-closing data objects, then make sure these higher-level iRODSFS handles are closed out at the right time -- that is, first thing.