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

Improve error message returned when user has no email templates #91

Closed
johnbradley opened this issue Jun 19, 2017 · 7 comments
Closed
Milestone

Comments

@johnbradley
Copy link
Contributor

When this happens you receive this error response:

<h1> Server Error (500) </h1>
@dleehr
Copy link
Member

dleehr commented Jul 26, 2017

This came up again today

Despite the error I get, not sure who to send this to, since I don’t know if it’s a script issue or server issue. The person I’m testing with doesn’t get an email, nor does his instance of Data Service get a copy of the project I’m trying to send.

Finally got everything working for uploading, but when I try delivering data to someone, I get this:

ddsclient deliver -p xxx --user xxxx
Delivering project.
Downloading a copy of 'xxx'.
Done: 100%
Uploading to 'xxx 2017-07-26 14:12'.
Done: 100%

Request to https://d4s2.gcb.duke.edu/api/v1/deliveries/x/send/ failed with 500:
<h1>Server Error (500)</h1>.

@dleehr
Copy link
Member

dleehr commented Mar 23, 2018

Related to #106

@dleehr
Copy link
Member

dleehr commented Sep 14, 2018

Seen again by @hlapp in #180

@hlapp
Copy link

hlapp commented Sep 14, 2018

This happens when which user has no email template? The sender or the recipient? I assume the sender, because that the recipient doesn't have a template will be normal?

So the assumption would be that normally this won't happen because an actual core will have a template set up?

@dleehr
Copy link
Member

dleehr commented Sep 14, 2018

This happens when which user has no email template? The sender or the recipient? I assume the sender, because that the recipient doesn't have a template will be normal?

We've since updated D4S2 to use a set of default templates, so nobody should see this error when creating a delivery. But we have some cleanup to do on how to make sure those templates exist (#181).

I think the error you saw on monday (#180) was due to D4S2 looking up a template based on the recipient (and not the sender), and we'll get to the bottom of that too.

@dleehr dleehr added this to the Beta UI milestone Sep 17, 2018
@dleehr
Copy link
Member

dleehr commented Nov 12, 2018

@johnbradley Same fate as #180?

@johnbradley
Copy link
Contributor Author

Fixed by #183

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

3 participants