Skip to content
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

omero fs usage on a non-existent object returns an uninformative error #187

Closed
manics opened this issue Feb 26, 2020 · 0 comments
Closed

Comments

@manics
Copy link
Member

manics commented Feb 26, 2020

$ omero fs usage Project:1234567890
Using session for USER@HOST:4064. Idle timeout: 10 min. Current group: GROUP
Error:
$

Expected: Error message should indicate the object doesn't exist

snoopycrimecop added a commit to snoopycrimecop/omero-py that referenced this issue Mar 6, 2020
snoopycrimecop added a commit to snoopycrimecop/omero-py that referenced this issue Mar 6, 2020
Repository: ome/omero-py
Excluded PRs:
  - PR 184 manics 'Auto-format code with black' (exclude comment)
  - PR 162 manics 'import --fetch-jars' (exclude comment)
  - PR 160 manics 'prefs.py: config throw if OMERODIR not set' (exclude comment)
  - PR 129 dominikl 'Add option to create new ThumbnailStore connection' (exclude comment)
  - PR 115 manics 'Remove omero_ext.argparse' (exclude comment)
Already up-to-date.

Merged PRs:
  - PR 114 manics 'First attempt at adding optional packages'
  - PR 185 joshmoore 'config: Escape quotes in `Default:` section'
  - PR 186 joshmoore 'omero.scripts: prepare scripts for use of CLI'
  - PR 188 manics ' admin diagnostics: show BF (and optionally other) jar versions'
  - PR 189 manics 'BlitzGateway defaults to secure=True'
  - PR 192 joshmoore 'Use get_error for 'fs usage' failures (fix ome#187)'
  - PR 193 joshmoore 'cli: don't unset ICE_CONFIG (fix ome#191)'
  - PR 194 manics 'Support Python 3 asyncio concurrency'

Generated by OMERO-python-superbuild-push#245 (https://merge-ci.openmicroscopy.org/jenkins/job/OMERO-python-superbuild-push/245/)
joshmoore added a commit that referenced this issue Mar 6, 2020
Use get_error for 'fs usage' failures (fix #187)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant