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

Endpoints and keys in datajoint config are allowed to be undefined #93

Open
linuswagner opened this issue Sep 17, 2020 · 0 comments
Open

Comments

@linuswagner
Copy link
Member

The datajoint config in the main are allowed to be unset (namely MINIO_ENDPOINT, MINIO_ACCESS_KEY and MINIO_SECRET_KEY).

In my case this lead to a runtime error thrown by the Bayesian hypersearch because storing wasn't possible.

Is there an obvious usecase where you don't need the storage defined?
If there isn't, I would suggest replacing the function call by directly accessing the os.environ object allowing for an exception to be raised. If the same behavior is desired, I'd add a try except around that with a user warning in the except.

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