Bert Kleewein
Bert Kleewein
@michaelosthege I'm still thinking through how to deal with this, but the `loop_start()` thread can silently die. When it does, many of the `self.client` methods still _appear_ to work, but...
@michaelosthege - calling `loop_start()` won't hurt, but it probably won't help either. I've tried some easy tricks to revive the thread, but none of them worked. This was a few...
I think I have the same request. I'm using this to set up a server for my son, so i'm finding myself typing lots of console commands, especially as I'm...
OK, I found a better workaround for my purposes: from my host, I launch a bash shell on the container: ``` bert@Beast:/$ docker exec -it spigot /bin/bash ``` Then, from...
I had this problem. I fixed it with some fumbling and stumbling. I tried to figure out exactly what made it work, but I can't get it to break again...
@robertsLando - yes, this is ready for review.
@robertsLando - it should fix _some_ flaky tests. I don't know if it will fix the flaky tests that you were seeing though. :)
@robertsLando - ready again. I think this second set of changes really improves these tests. I found a few things that might explain general flakiness.
@ramumr06 - I recommend you change the password on your container repository. You accidentally leaked it in the deployment manifest above. If that password gives write access to the repository,...
Hi @ramumr06 , yes, my comment was only about securing your registry. Logs from edgehub don't really help. logs form your gwmodule are more useful, but I 'm not sure...