We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
See https://forum.image.sc/t/omero-metadata-fails-on-deletemap-when-well-to-images-was-set-yes/27761 and #11 (comment)
The default wait value of the CLI command is set -1 but the logic for handling indefinite waiting is not implemented in the plugin:
wait
-1
omero-metadata/src/omero_metadata/cli.py
Lines 481 to 484 in ad50292
This means the default populate --context deletemap command will fail immediately unless --wait is overriden.
populate --context deletemap
--wait
Looking at the implementation in the base GraphControl, two options can be considered for the immediate fix:
None
loops
ms
wait=-1
The text was updated successfully, but these errors were encountered:
No branches or pull requests
See https://forum.image.sc/t/omero-metadata-fails-on-deletemap-when-well-to-images-was-set-yes/27761 and #11 (comment)
The default
wait
value of the CLI command is set-1
but the logic for handling indefinite waiting is not implemented in the plugin:omero-metadata/src/omero_metadata/cli.py
Lines 481 to 484 in ad50292
This means the default
populate --context deletemap
command will fail immediately unless--wait
is overriden.Looking at the implementation in the base GraphControl, two options can be considered for the immediate fix:
wait
value toNone
and use some sensible default values forloops
andms
wait=-1
use case i.e. wait for the deletion command to finish by default and allow it to be aborted via the CLIThe text was updated successfully, but these errors were encountered: