<gchristensen>
they're following some feedback I gave them a while back
<LnL>
it's back down
<cole-h>
Which is to cull in-use machines? :D
<LnL>
what's that?
<gchristensen>
if they were doing maintenance which would break my spot servers for anything more than a few seconds, don't email me to say so -- just make the price expensive so I can't buy them
<cole-h>
Ohhhhh. That's smart.
<LnL>
heh
* cole-h
wishes he had a borg dashboard for when that happens
<LnL>
so.... they will come back automagically?
<gchristensen>
yeah, I'm updating the provision URL and the next deploy will automatically recreate them
<cole-h>
Woo! :)
<LnL>
ah so small intervention
<gchristensen>
the URL update won't be needed in a couple weeks, once the new images are updated with Packet
<LnL>
yeah figured, was referring to the deploy part
<gchristensen>
yeah
<gchristensen>
ehhh it may not work correctly actually
<gchristensen>
it might not realize the machines don't exist with Packet in a dry-activation deploy
<cole-h>
Also gchristensen++ for trying to push the new doc RFC closer
<{^_^}>
gchristensen's karma got increased to 290
<gchristensen>
well, let's see if it does work. I'll give it a few minutes.
<gchristensen>
the way this machine is created, there are 4 steps and the first 3 are very fast and the 4th takes a While
<gchristensen>
lol
<gchristensen>
hmmm
<cole-h>
oof
<cole-h>
More connection refused's :(
<gchristensen>
none of these are too surprising to me tbh
<gchristensen>
that is the first time the error was surprising.
<cole-h>
What does `--check --allow-recreate` do?
<gchristensen>
--check tells nixops to confirm with the API that those machines actually exist (if not, error unless --allow-rcreate is passed -- in which case, recreate them)
* LnL
is back
<cole-h>
o/
<LnL>
what did I miss?
<cole-h>
Just watching Graham fiddle with stuff to see if we can get it to deploy (:
<gchristensen>
grub-install: error: cannot find a GRUB drive for /dev/disk/by-id/ata-MICRON_M510DC_MTFDDAK480MBP_160511B060AD. Check your device.map.
<gchristensen>
I'm not understanding why this is happening
<cole-h>
Time to switch to systemd-boot? :D
<LnL>
oh, the actual deploy failed no something nixops related
<cole-h>
But it really is weird...
orivej_ has quit [Ping timeout: 260 seconds]
<LnL>
gchristensen: should we try to rollback to the the nixpkgs from before the recent update?
MichaelRaskin has quit [Read error: Connection reset by peer]
<{^_^}>
input-output-hk/nixops-packet#18 (by grahamc, 1 minute ago, open): Destroying a server with a bad API key deletes locally but doesn't destroy the machine
<cole-h>
And obviously 1.0.2u is outdated, so build fails without a shell providing 1.0.2u
<LnL>
gchristensen: what would you suggests as the next one?
<gchristensen>
hmm
<gchristensen>
maybe comment parser, what do you think?
<LnL>
sounds good
<cole-h>
+1
<{^_^}>
[ofborg] @LnL7 opened pull request #484 → lapin github-comment-filter → https://git.io/JflHE
<cole-h>
LnL: Oooh, look at that: net-negative by one line! :D
<LnL>
this one was pretty straightforward
<cole-h>
gchristensen: Considering GH Actions is free for public repos (I think the cost/"minutes" was something you had reservations about in the past), would you be open to a PR adding GHA?
<cole-h>
While I'm in the mindset of Actions thanks to me fixing lorri's Actions
<cole-h>
That darn cognitive complexity lint again...
<LnL>
if you don't know what to do, a rust update would be nice :)
<cole-h>
LnL: You sure that'll solve the problem? 1.43.0, clippy still picks up that cognitive complexity
<LnL>
huh
<cole-h>
However, it's happy with it in nightly clippy 0.0.212 (28197b6 2020-04-29)
<gchristensen>
by all means
<cole-h>
LnL: Maybe next stable -- beta also doesn't complain about complexity.
<LnL>
I have nothing nightly related tho
<cole-h>
You don't get the complexity warnings with `cargo clippy`?
<cole-h>
ofborg-evaluation-filter.service ofborg-github-comment-filter.service ofborg-github-comment-poster.service ofborg-stats.service <- all look dead
<LnL>
ah I see, my editor is building stuff in the background first so the warning doesn't show up anymore
<cole-h>
Your editor: "mmmmm tasty errors"
<LnL>
you could deploy a change to restart stuff :)
<gchristensen>
restarted
<cole-h>
LnL: You know what, you're right...
<cole-h>
gchristensen: Under what kind of situations should we NOT re-deploy? Is there ever a reason not to, if it would fix this kind of thing?
<LnL>
out of disk space wouldn't get you very far with this