samueldr changed the topic of #nixops to: NixOps related talk | logs: https://logs.nix.samueldr.com/nixops/
abathur has joined #nixops
abathur has quit [Ping timeout: 240 seconds]
abathur has joined #nixops
abathur has quit [Ping timeout: 260 seconds]
pbb has quit [Remote host closed the connection]
abathur has joined #nixops
abathur has quit [Ping timeout: 272 seconds]
abathur has joined #nixops
abathur has quit [Ping timeout: 240 seconds]
pbb has joined #nixops
abathur has joined #nixops
abathur has quit [Ping timeout: 272 seconds]
abathur has joined #nixops
abathur has quit [Ping timeout: 268 seconds]
psyanticy has joined #nixops
kalbasit has quit []
kalbasit has joined #nixops
kalbasit has quit [Ping timeout: 272 seconds]
sevanspowell has quit [Ping timeout: 258 seconds]
manveru has quit [Ping timeout: 264 seconds]
davidtwco has quit [Ping timeout: 246 seconds]
sevanspowell has joined #nixops
psyanticy has quit [Ping timeout: 272 seconds]
psyanticy has joined #nixops
kalbasit has joined #nixops
davidtwco has joined #nixops
abathur has joined #nixops
manveru has joined #nixops
psyanticy has quit [Read error: Connection reset by peer]
manveru has quit [Ping timeout: 272 seconds]
pbb has quit [Remote host closed the connection]
pbb has joined #nixops
pbb_ has joined #nixops
pbb has quit [Ping timeout: 272 seconds]
pbb_ has quit [Ping timeout: 272 seconds]
pbb has joined #nixops
<disasm> I'm debugging a rather weird nixops issue. we're storing some nix code in https://github.com/input-output-hk/nixops-packet/blob/cpr-support/nixopspacket/backends/device.py#L70. However, sometimes this returns back as None and I'm not sure why. Doing sqlite against the deployment, you can distinctly see the nix code in the database. It seems like sometimes it takes a different path through the code that
<disasm> doesn't load the state correctly. aminechikhaoui any thoughts as to how to debug this further?
abathur has quit [Ping timeout: 272 seconds]
<aminechikhaoui> disasm hm that sounds odd. No idea how to debug that unfortunately
<disasm> it looks like this is a problem of another instance lacking the data. We made some progress