Stuck on an issue?
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.
Initalization hang for launch experiment under assistant/init
See original GitHub issueUnder a local NextML, when having 6 unfinished experiments (using the PoolBasedBinaryClassification app) I observed an initialization hang (never completed) when attempting to launch the strange fruit experiment. No errors were observed in the NextML output.
The problem went away once I did docker rm $(docker ps -a -q)
Issue Analytics
- State:
- Created 6 years ago
- Comments:20 (4 by maintainers)
Top Results From Across the Web
App startup time - Android Developers
Launch the process. Initialize the objects. Create and initialize the activity. Inflate the layout. Draw your application for the first time.
Read more >Reducing your app's launch time - Apple Developer
Initialize a restricted subset of the app's behavior that's known to be viable on initial launch. For example, a task manager app can...
Read more >Default FirebaseApp is not initialized - android - Stack Overflow
You're trying to get an instance of Firebase without initialize it. Please add this line ... initializeApp(Context) first' crash in the run.
Read more >Migration to 2021.7 fails: Fatal Python error: init_interp_main
Hi: I using Home Assistant container version, I've migrated from 2021.6.6 to 2021.7, and the new version doesn't starts, I get this message: ......
Read more >just-containers/s6-overlay - GitHub
You'll never have zombie processes hanging around in your container, ... Our overlay init is a properly customized one to run appropriately in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
In my experience is the problem is when you haven’t removed the containers in a few days. I’ve had plenty of times when I’ve started 20+ experiments in quick succession.
I think the trick will be replicating it and then turning on some very verbose outputs to pinpoint the problem. That and removing the containers one at a time to try to see which one is causing it. I’ll try to figure it out the next time it happens to me.
Branch that fixes this here: https://github.com/nextml/NEXT/compare/fix_minionworker_hostname
Tests pass on my up-to-date images at work. I can’t test the normal ones here though so I’m holding off on the pull request.