Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Better Error messages when exporting to ORCID
See original GitHub issueIs your feature request related to a problem? Please describe.
I was testing out the export to orcid feature on dev and came across Could not export to ORCID: Not Found a lot. Seems like the orcid sandbox is really flakey and it eventually went completely down later (endpoint started working later once the sandbox was back). The message is confusing and makes it seem like the id of the Dockstore entry/version can’t be found.
Describe the solution you’d like The message should indicate it’s a problem with orcid and not Dockstore.
Additional context Hopefully it is just their sandbox that is really flakey, so this might only be annoying for developers.
┆Issue is synchronized with this Jira Story ┆fixVersions: Dockstore 1.12 ┆friendlyId: DOCK-1764 ┆sprint: SEAB 79- Gary (the snail) ┆taskType: Story
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
seems to be a different issue. this issue is for better error message. that issue (with the infinite progress bar) implies no error message is displayed because the frontend didn’t handle it
Sounds hard to reproduce and more likely to affect developers (sandbox) than users. Going to close, please re-open if seen again