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

DM-24290: Remove if Butler exists checks from bin.src scripts. #368

Merged
merged 1 commit into from Apr 28, 2020

Conversation

DinoBektesevic
Copy link
Collaborator

Checks are made against local filesystem only. This stopped being a valid assumption since S3Datastore was implemented as the data repository does not need to be local anymore.

The failure case should be handled internally by Butler itself at instantiation time.

These check currently block executing makeGen3SkyMap if the location of the data repository is in S3 (f.e. s3://bucketname/).

The errors raised by the butler are either RuntimeError if the butler config file is of unknown format or FileNotFoundError if it's not at the given location. I think this is fine, but if required I think it should be possible to reinstate the exact error messages as before by attempting to instantiate a Butler, catching the exceptions and then printing and exiting with error code 1.

@DinoBektesevic
Copy link
Collaborator Author

@TallJimbo maybe you could share your thoughts on this PR when you find the time?

Checks are made against local filesystem only. This stopped
being a valid assumption since S3Datastore was implemented
as the data repository does not need to be local anymore.

The failure case should be handled internaly by Butler itself
at instantiation time.
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

Successfully merging this pull request may close these issues.

None yet

2 participants