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

Clarify error message when study bucket is not found in upload #758

Open
znatty22 opened this issue Sep 23, 2021 · 3 comments
Open

Clarify error message when study bucket is not found in upload #758

znatty22 opened this issue Sep 23, 2021 · 3 comments
Assignees
Labels
refactor Something needs to be done better

Comments

@znatty22
Copy link
Member

This message is too cryptic for end users to understand

image

@znatty22 znatty22 added the refactor Something needs to be done better label Sep 23, 2021
@znatty22 znatty22 assigned gsantia and unassigned gsantia Sep 29, 2021
@gsantia gsantia self-assigned this Oct 19, 2021
@gsantia
Copy link
Contributor

gsantia commented Oct 22, 2021

@znatty22 Was there any more info provided by the user? For example, how can I recreate this?

@znatty22
Copy link
Member Author

@gsantia I think this happens when a user tries to save a document to the study bucket and study bucket name is null. The study bucket name has a regex validator on it that checks the name follows a specific format.

@znatty22
Copy link
Member Author

znatty22 commented Oct 29, 2021

@gsantia I think I know where this is coming from. Its an exception thats raised by the boto s3 client which is why we can't find it anywhere in the code lol.

I think this issue will get resolved once we fix bucket setup bc the bucket name is not saved to the Study on creation since bucket setup fails. So I guess right now, if the bucket name is blank due to failed bucket setup it will try to create a new doc and save it to an invalid bucket. So let's see what happens once we test #790 in QA/prod

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactor Something needs to be done better
Projects
None yet
Development

No branches or pull requests

2 participants