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.
Most problems deploying/upgrading BinderHub can be solved by checking indentation
See original GitHub issueHello!
So 9 times out of 10 when my BinderHub is acting weird, it’s because I’ve indented something incorrectly in config.yaml. There was a (brief) discussion in #835 around trying to implement some kind of linting check to catch these types of mistakes, but there isn’t a concrete plan yet.
For the time being, I suggest updating the Debugging BinderHub docs to advise users to thoroughly check their config files before diving into k8s debugging.
Are there any thoughts or further ideas around this?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:12 (12 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
@sgibson91 ❤️ 🎉 you are great! 😄
I’m having a headache with connecting an Azure container registry to my BinderHub. So if I don’t have any breakthroughs with that, I can start a PR for this 😄