[04:36] <jam> morning all
[05:01] <Chipaca> jam: moin moin
[05:01] <jam> Chipaca, are you ok? I don't ever see you this early
[05:03] <Chipaca> jam: saw an email from tim saying we're doing the 6am meetings
[05:03] <Chipaca> but now not finding them on the calendar
[05:03] <jam> Chipaca, yeah, I don't see anything in the next couple of weeks
[05:03] <Chipaca> hmmm
[05:03] <jam> he's likely around now, though
[05:10] <Chipaca> jam: i pung him but no answer, i think i'll go back to bed for a bit
[05:10] <jam> Chipaca, sleep well
[05:10] <Chipaca> sounds like a good idea
[05:27] <jam> Chipaca, I just saw it show up on the calendar
[08:23] <Chipaca> jam: great success
[08:29] <jam> Chipaca, that we got the meeting scheduled?
[08:29] <Chipaca> jam: yes :)
[08:30] <Chipaca> jam: you need to read it with borat accent though
[11:26] <facubatista> Muy buenos días a todos!
[11:43] <jam> morning facubatista
[11:49] <facubatista> hola jam
[12:30] <Chipaca> facubatista: 'sup :)
[12:30] <facubatista> hola Chipaca :)
[14:18] <mup> PR operator#336 opened: main: log ops version on startup <Created by chipaca> <https://github.com/canonical/operator/pull/336>
[16:12] <Chipaca> jam: tbh i _had_ forgotten about #282
[16:12] <mup> Issue #282: Harness: Unable to assert if framework was called correctly by charm <Created by relaxdiego> <https://github.com/canonical/operator/issues/282>
[16:53] <facubatista> Chipaca, ctrl-c will always be ugly, unless we do something about it! not only when hitting the store, where I could put a specific exception handler there, think for example if you do Ctrl-c while it's zipping the build directory
[16:54] <facubatista> Chipaca, we could have a generic catcher for Ctrl-c and present a nice message to the user, like "interrupted by you" or whatever
[16:55] <facubatista> (IOW: it's something we should probably improve, it's more generic than my branch, let's open an issue about this)
[17:04] <Chipaca> facubatista: i guess before now there never has been a situation where i've wanted to hit ^c because it was always fast enough :-D
[17:05] <Chipaca> facubatista: filing an issue now
[17:07] <Chipaca> facubatista: if i have time today i'
[17:07] <Chipaca> ll play with that
[17:07] <Chipaca> but i'm behind on my charm reviews
[17:07] <Chipaca> we'll see
[17:07] <Chipaca> but right now, i'm stepping away for a while
[18:10] <facubatista> Chipaca, jam, when/by whom will be `remove_unreferenced_events` called?
[18:55] <facubatista> Chipaca, jam, is this what you had in mind? https://github.com/openstack-charmers/charm-ceph-iscsi/issues
[20:56]  * facubatista eods
[21:48] <Chipaca> facubatista: remove_unreferenced_events is meant to be called by the charm author if/when they need it
[21:50] <Chipaca> facubatista: and, those issues seem spot on to me
[21:54] <Chipaca> facubatista: it would be nice to include the code when you're talking about it but i know it's faffy wory
[21:54] <Chipaca> work*
[21:59] <facubatista> Chipaca, "seem spot on"?
[21:59] <facubatista> what that means?
[22:00] <Chipaca> facubatista: que parece que la clavaste al ángulo
[22:00] <Chipaca> facubatista: that you hit the nail on the head
[22:00] <facubatista> Chipaca, and what "faffy wory" means? :p
[22:01]  * facubatista searches "faffy wory" and find links like "My daddy is a policeman. What is he doing at work?"
[22:01] <Chipaca> facubatista: faffy work, something overcomplicated compared to the benefits it brings
[22:01] <facubatista> ah, ok
[22:55]  * Chipaca EODs