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.
Document --debugWorker flag
See original GitHub issueAs a toil user, I was looking for a way to let my IDE set breakpoints in my toil workflow, and I came across #1910. Once I worked out I could --debugWorker, this totally solved my problem.
However, this flag isn’t documented:
- On the debugging help page: https://toil.readthedocs.io/en/3.15.0/running/debugging.html
- On the CLI help page: https://toil.readthedocs.io/en/3.15.0/running/cliOptions.html
I realise you may have done this because the flag is considered experimental (is it still experimental?), but even if it is I think it would be invaluable for users to document it in one or both of these places, even with some kind of disclaimer, because it improved productivity considerably for me.
┆Issue is synchronized with this Jira Task ┆Issue Number: TOIL-394
Issue Analytics
- State:
- Created 4 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
I’m happy to put in a PR for this, but I figure it should have an issue and someone telling me it’s a reasonable change first.
I haven’t. It could certainly help people wade through our huge pile of options…