/srv/irclogs.ubuntu.com/2017/06/16/#juju-dev.txt

menn0axw: I wasn't going to tackle the statemetrics bit so if you've already started on that then great00:18
axwmenn0 wallyworld_: I'm back if you want to chat00:54
wallyworld_meeting in today's standup HO?00:54
menn0axw, wallyworld_: sounds good00:55
axwwallyworld_: what's a sensible upper bound on the flush interval? 10 minutes?02:33
wallyworld_i was thinking more like seconds02:33
wallyworld_since we need to not lose errors if agent is killed02:34
wallyworld_and actually, we should maybe flush immediately if there's an error02:34
wallyworld_or a warning or ciritical02:34
axwwallyworld_: it'll flush when the agent shuts down02:34
wallyworld_what about when it is killed02:34
axwand it'll go to logsink.log immediately anyway02:34
axwwallyworld_: what do you mean by killed?02:35
wallyworld_hard stopped via kill -9 or something02:35
wallyworld_do we catch signals02:35
axwwallyworld_: I can't recall if we catch the signal, but we should if we don't02:35
wallyworld_yep, and systemd restart etc02:36
axwwallyworld_: SIGTERM should lead to graceful shutdown, which would involve flushing02:36
wallyworld_ok, all that aside, i think 5 or 10s max for flush interval, IMO02:36
axwwallyworld_: I'll make it 10 seconds. if we get to 10 seconds then you've basically got no logging happening, and you shouldn't have the flush interval that high anyway02:38
wallyworld_exactly, hence the desire to not allow the user to do something dumb by mistake02:39
axwmenn0: on the allwatcher frame size thread: doesn't the first response have to have all the records? i.e. like the other watchers, the first response gives you the initial state02:42
menn0axw: gah, good point02:43
menn0axw: maybe there needs to be some special handling for the allwatcher02:43
axwmenn0: yeah, it could get pretty huge02:43
axwmenn0: perhaps some kind of continuation flag02:43
menn0axw: exactly02:44
menn0wallyworld_: ping03:21
wallyworld_hey03:21
menn0wallyworld_: I have some questions about your PR. quick hangout?03:21
wallyworld_sure03:21
menn0wallyworld_: standup again?03:22
wallyworld_yep03:22
wallyworld_menn0: with where the interface lives, it may be used multiple places so saying it needs to live where it is used doesn't always work. For state, because it's a bit of a ball of mud, we to date have tended to include interfaces for entity foo in the state/foo.go file. For other things like Environ, we have a separate interfaces.go file, but if we were to do that for state as it exists now, it wouldn't be pretty03:57
menn0wallyworld_: understood but for this interface it seems like it might be better to be defined at point of use.03:58
menn0wallyworld_: happy to defer to your judgement03:58
wallyworld_menn0: i guess i'm saying "point of use" could be many places not just one place in the code03:59
menn0wallyworld_: fair enough03:59
wallyworld_but the other place, i should return a concrete type though03:59
anastasiamacaxw: ping05:35
=== frankban|afk is now known as frankban
rogpeppeaxw, anastasiamac: looking for a second review of https://github.com/juju/juju/pull/7507 if you fancy it...07:46
rogpeppewallyworld_: ^07:47
axwrogpeppe: sure07:47
rogpeppeaxw: ta!07:47
axwrogpeppe: ah, I was wondering what the context of your tweet was :)07:50
rogpeppeaxw: :)07:50
axwrogpeppe: LGTM, thanks!07:55
rogpeppegit diff07:56
rogpeppeaxw: tyvm07:56
rogpeppeaxw: another (tiny) one - I just noticed I missed out a return statement in the ContextWithDeadline code https://github.com/juju/utils/pull/28308:00
axwrogpeppe: LGTM08:01
rogpeppeaxw: thanks08:15
=== freyes__ is now known as freyes
=== freyes__ is now known as freyes
=== cory_fu_ is now known as cory_fu
=== frankban is now known as frankban|afk
=== mup_ is now known as mup
=== mup_ is now known as mup
=== mup_ is now known as mup
=== Spads_ is now known as Spads
=== jcsackett_ is now known as jcsackett
=== JoseeAntonioR is now known as jose

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!