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.
Misleading Error Message When Refreshing Workflows
See original GitHub issueBug Report
If there is an error refreshing workflows because your GitHub token doesn’t have the correct scope, the error message says it failed trying to create/modify, which could be read as Dockstore was trying to modify something in your GitHub account.
Expected behaviour
If refreshing workflows fails due to an authorization issue, the error message should not say it was trying to create or modify anything.
Actual behaviour
It says it was trying to create/modify.
Steps to reproduce the behaviour
To reproduce this, you have to be in a state where your GitHub token is missing a scope. I don’t know how you into that state, but once you are:
- Go to
My workflows - Click on
Refresh All Workflows
See following error screen:
┆Issue is synchronized with this Jira Story ┆Fix Versions: Dockstore 1.7 ┆Issue Number: DOCK-202 ┆Sprint: Seabright Sprint 10 Jet Ski ┆Issue Type: Story
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 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
Why is this not syncing
I think getting rid of create/modify is fine, its usually not useful. I do like keeping the http status codes, makes bug reports (user or other-wise) more helpful.