Katia Esposito
Katia Esposito
@siddharthkp for the most part, it's simply Docker containers, where exit code != 0 is failure. Some env vars are available, fwiw: https://docs.gitlab.com/ce/ci/variables/README.html What other information would you need? Happy...
yep, probably good enough as gitlab.com has free shared runners :D
While this might be useful for your use-case, I do not see this PR getting accepted anytime soon due to the standalone nature of this software.
At second glance it might just be that the `nurdism/neko:firefox` image is just so outdated. Could you please set automatic builds for all the images on Docker Hub? I am...
Not sure if related, but my bitlbee crashes on latest bitlbee-steam commit (https://github.com/bitlbee/bitlbee-steam/commit/56b72608ee7ac804835f390e921a2234060b424c) and 3.4.2+20160526+master+35-g59a7dc5-git bitlbee. ``` @root │ steam - Logging in: Connecting @root │ steam - Logging in:...
I would have, but it works now. Sorry! :~(
I can also reproduce this error by sending a message from bitlbee to a friend.
I can seem to be able to send messages again, so yes, it's something on Steam's side, however, not sure the connection should reset at that point.. 2016-01-03 20:04 GMT+01:00...
:trollface:
I haven't had time to test this, but if that's the case, shouldn't it start the login-shell by default?