[09:08] <bthomas> Mo-yawning all
[11:22] <gnuoy> Morning all, I just had to write a fairly sizeable patch for an interface written in the ops framework. The operator framework testing harness is awesome and saved me hours, thank you!
[11:23] <facubatista> ¡Muy buenos días a todos!
[11:23] <facubatista> gnuoy, it's glad to hear that you find it useful!
[13:30]  * bthomas -> lunch
[13:45]  * bthomas -> back
[14:18] <justinclark> hello o/
[14:18] <facubatista> hola justinclark
[14:30]  * facubatista -> errands
[15:02]  * facubatista is back
[15:21]  * facubatista -> lunch
[15:56]  * facubatista is back
[16:58] <dstathis> Is it considered good practice to leave breakpoints in production charm code?
[20:35] <facubatista> dstathis, if you use self.frameworks.breakpoint() the code will be interrupted ONLY if you're in a juju debug session
[20:36] <facubatista> dstathis, so it's "safe" (don't know if a good practice, though... note that you can always jump into "pdb mode" inspecting Python code for any event callback, no need to leave explicit breakpoints for that)
[21:34]  * facubatista eods