alastairp, based on your whether cron is running PR, how about we also add an action to validate and display the crontabs in human readable form if a crontab is modified?
we do not need to do this now but seems a useful future enhancement
ruaok
reosarevok: seems good.
Freso
I would remove the "if you ask nicely", but otherwise seems good.
alastairp
mmm, maybe itercron will raise an exception if a pattern is invalid? I don't know if it can turn a pattern into a descriptive text
_lucifer
there's a is_valid function to check if the pattern is valid
alastairp
I guess ruaok and I have been around long enough that (most of the time) we know how to write a cron without screwing it up
would be happy to add additional cron management commands if you'd find it useful
ruaok snaps his suspenders in agreement
reosarevok
Freso: well, the point is we are not obliged to remove the name AFAICT and I certainly won't do it if they are dicks about it
_lucifer
👍, human readable text would have been nice but i do not see that in the library docs so let's leave it.
hmm. interesting. I should read up on the USB-3 spec. I wonder how the data is multiplexed
alastairp
there's so much going on there
usbc/thunderbolt/alt modes, etc
a friend of mine has a 4k monitor with built in ethernet and usb hub, and if he wants 60hz he can't run the hub at usb-3/gigabit ethernet because there's not enough bandwidth
alastairp, ruaok: we do not have buildx on bono. can we install that?
*docker buildx
ruaok
sure, have at it. bono is our wild west, right?
alastairp
you'll have to install a new version of docker
_lucifer
lol
i checked we have 19.03 so it should work
only need to install buildx
alastairp
maybe there's a setting to add in the daemon.json file
ruaok
alastairp: for `COPY ./docker/services/spark_reader/consul-template-spark-reader.conf /etc/consul-template-spark-reader.conf` how does the base image know to look at this file?
alastairp
ruaok: sorry - missed one more item
we add `down` to all services
and then in rc.local rm the down based on env variables
ruaok
understood, but this is a one service container that I always want up. so I should not need down, right?
alastairp
right, so add a new runit service with a `run` file
any tips on how to debug this? the flags for run-consul-template are not terribly helpful.
alastairp
are you just running it from a `docker run`?
_lucifer
i woudl suggest copying stuff from the statup improvements PR
alastairp
consul-agent requires syslog to be started up (which runit will do)
ruaok
the container just restarts, so I am doing a `docker run --rm -it ... bash`
yep, i have a valid looking /etc/service/syslog-ng/run
alastairp
I normally see this happening - consul-template starts up, doesn't see syslog, prints the error, syslog starts up, consul-template restarts, connects to syslog, and goes silent
_lucifer
reosarevok, i need to create a couple of fake users on MB for testing. can't use test.mb. what's the best way to go about it. i go ahead and create. after i am done, delete the account?
alastairp
but I'm unsure about the restart, sorry. I'm in a call, but can take a look at it afterwards if you get the code up
reosarevok
_lucifer: or don't delete them
I see no problem with having ListenBrainz Test User or something
ruaok, just saw your consul template, i think the startup improvements won't benefit you :(. those improvements are useful when loading stuff like keys from consul.
ruaok
ah, I feel better now. I looked at your links and wasn't certain what I should be copying.
thanks though.
_lucifer
one thing though, you might need a `cd /code/metrics` somewhere.