/srv/irclogs.ubuntu.com/2020/04/09/#smooth-operator.txt

=== max__ is now known as Guest14293
Dmitrii-Sho/04:43
jammorning Dmitrii-Sh05:41
Dmitrii-Shmorning jam06:35
Dmitrii-Shregarding https://github.com/canonical/operator/pull/216#discussion_r405455364 - we'll need to change our copyright header checks then06:36
Dmitrii-Shas for serialization, I converted the interface code to use json instead https://github.com/canonical/operator/pull/216/commits/68152461b5b104ccf4aaea3c04ea36e9d1fd5c7b06:37
jamDmitrii-Sh, indeed, it really depends how we want to do it as a project, and then update the source checks, etc to match that.06:38
jamI think I clarified that my preference is to keep Copyright as a comment and put the docstring after copyright comment06:38
jamwhich wouldn't require changes06:38
Dmitrii-Shjam: ok, I reverted the change. Might be good to discuss during the standup06:48
niemeyerGood morning all08:24
jammorning08:25
Chipacagooood morning team!08:32
* jam steps away for lunch, bbaib08:45
Chipaca'be back after i burp' 👍08:48
jamI thought I was the one that made up backronyms. I did realize once I hit submit that it was a typo, wasn't sure it was worth a second message :)09:47
jamI just came across this https://www.theonion.com/nasa-launches-vengeance-rover-to-pay-back-mars-for-kill-184275016610:22
jamDmitrii-Sh, Chipaca : thoughts on parameter formatting. 'git annotate' says that I use ":param foo: description" style, while the two of you have used more "foo -- description" style.10:31
jamwe should probably get shared agreement on that style (possibly based on what Sphinx/readthedocs renders)10:31
Chipacajam: agreed10:31
jams/we should probably/we need to get/10:31
Chipacaso, questions10:31
Chipacado we want to use python type annotations or not?10:31
Chipaca(if we did, we could then use mypy to do static analysis while not requiring it to run)10:32
jamI've never used them, my primary Python time was in the 2.* era. AIUI they are just documentation as well, right?10:32
jameg, not actually enforced.10:32
Chipacaright, except mypy can check for them10:32
Chipacaie you can do static analysis10:32
jamI don't have enough experience with them to know whether they feel good or feel like noise.10:32
Chipacawhen running with plain python, they're just metadata10:33
Chipacato me they feel more natural than the :type: docstrings10:33
Chipacabut I don't have a super-strong preference :)10:33
Chipacalet's talk about it on tuesday when facu is back10:34
Chipacafacu and myself, that is :)10:34
jamGiven the language has built-in support for them, I'd tend to go with that over :type:, It also depends heavily on how well supported they are in editors10:34
Chipacai'll set up a meeting so we remember10:34
jambut PyCharm seems to support either.10:34
Chipacasphinx supports either also (with a plugin)10:34
Chipacai need to check if readthedocs supports that plugin but it should (and i have a friend working on the readthedocs backend so i might be able to influence that if they don't)10:35
jamMy main concern with "foo --" is that it is missing the "bulleted list" indicator. (start of new section is after the section has started)10:35
Chipacajam: 1 sec10:37
Chipacajam: http://www.sphinx-doc.org/en/master/usage/extensions/napoleon.html10:37
Chipacajam: I'd prefer either of those styles (google or numpy) to the default rst style10:38
Chipacajam: in any case 'foo --' is wrong :)10:38
Chipacajam: and, 1 further sec for me to find the other extension10:38
jamChipaca, interestingly, their statement "Compare the jumble above to this alternative". I actually find it easier to read the "jumble" but that is likely just lots of usage of that style. :)10:39
jamI can imagine that practice with an alternative will similarly improve my ability to read it.10:39
Chipacajam: https://github.com/agronholm/sphinx-autodoc-typehints would be the extension that gets type from the annotation, and it supports napoleon also10:39
jamfor some reason I don't like "foo (type):"10:40
jamI would have preferred it "foo: (type)"10:40
niemeyerI'm not a big fan of the :type: etc notation.. I've never seen it being worth the cost of having to write and read it, compared to normal English text in the summary10:40
jamIn that, I prefer Numpy, though it feels rather spaced out.10:40
niemeyerWe generally end up re-stating the type in the sentence anyway10:41
Chipacajam: note that with the typehints thing we'd just write foo: in the google style10:41
niemeyer:type:FooBar:  The FooBar used to process it.10:41
Chipacamaybe we should write them out in full for a single realistic docstring for the meeting tuesday10:42
Chipacai'll get on that after finishing dispatch support10:42
niemeyer+110:42
niemeyerThanks for that10:42
jamChipaca, sounds like some nice examples to have on hand10:42
niemeyerAre we skipping the standup today?10:43
Chipacawe can do it on IRC just to make sure we're aware of what we're doing10:43
niemeyerWell.. :)10:43
Chipaca:-D10:43
Chipacabut, no, i don't think we should (it's just facu that's away)10:44
Chipacai did delete it and then re-created it because i thought we'd do the bug revue today (but facu's away)10:44
Chipacaotoh i don't mind doing it on irc because introvert10:44
niemeyerI don't have it in my calendar.. if it's just Facundo out, we should do it10:49
jamso the weekly operator sync meeting that collided on Tues got moved to Friday evening....10:50
Chipacajam: yeap10:50
Chipacajam: don't worry about it10:51
jamI was going to say that it isn't a time that I think I'll be attending regularly.10:51
niemeyerBest time for regular weekly meetings.. Friday evening..10:53
ChipacaI've emailed Anthony about it being sub-ideal, we'll see10:53
Chipacameanwhile, don't fret it10:53
niemeyerBetter than that only if it was a Good Friday..10:56
Chipacathey're all good fridays bront10:59
Chipacaoh drat 12pm and i didn't have mah mid-morning protein11:10
Chipacalunch is gonna be a big thing11:10
* jam heads to help my son study Spanish12:29
ChipacaI think this is relevant to our interests: https://mobile.twitter.com/fasterthanlime/status/124802533723521024313:08
niemeyerWeeeeee13:09
Chipacaniemeyer, Dmitrii-Sh, jam, 👋13:33
Dmitrii-Sho/13:33
ChipacaI came back from getting a cup of tea to find my desktop wouldn't un-map the lock screen13:33
Chipacaannoying13:33
niemeyerWe're in the standup..13:33
Chipacaomw13:33
jamChipaca, Dmitrii-Sh https://meet.google.com/fqw-mdqc-dsf13:33
Chipacata13:33
jamhttps://github.com/canonical/operator/pull/221 reviewed13:52
jam'osp' is that supposed to be 'ops' ?13:52
pekkariHi, anybody can take a quick read to this pastebin to see what I'm doing that wrong settinga relation data? https://pastebin.canonical.com/p/sJGfT8Cx7v/13:55
jampekkari, you are setting "admin_url" to a tuple (url,) is that intended?13:56
pekkarijam: no those commas are not intended, I was trying to set a full dictionary first, and then moved to key by key assignment, thanks for the hint13:57
jampekkari, the other bug is that "event.unit" is the *remote* unit whose data has changed13:57
jampekkari, you're not allowed to write to the remote unit's data13:57
jampekkari, you want event.relation.data[self.model.unit]13:58
jampekkari, event.relation.data[event.unit] is to read the data that the remote side is telling you about during relation-changed13:58
pekkariI see, yeah, I was suspecting it was a newbie issue here13:58
pekkarithanks jam! I'll test it this way13:59
Chipacajam: thanks for the review13:59
Chipacajam: the "run the hook _as well_" was not what I had understood... but that's ok :)14:00
jamChipaca, so we had a number of discussions about it, where I ended up was that the operator framework already likes to have multiple event handlers14:01
jamlots of things can listen for 'install'14:01
jamthe hooks/* is just another one of them14:01
Chipacaright, so that seems in tune with that14:01
Chipacai'll fix14:01
jamIf you don't do that, then it ends up that dropping a shell script ends up breaking all the components that you're using14:01
Chipacayou say that like it's a bad thing14:01
* Chipaca hides14:01
jamChipaca, no worries, I was originally more in favor of what you implemented. It was when I realized the multi-event thing that it clicked in my head.14:02
Chipacajam: and yes i seem to have been in more of a hurry than needed when writing the commit message, will fix that also14:02
ChipacaI think I'm going to go for a run now, and return to this after14:15
* Chipaca goes14:26
niemeyer#21816:07
mup_PR #218: Add relation-created events <Created by dshcherb> <https://github.com/canonical/operator/pull/218>16:07
Chipaca#waat16:26
Chipacacockroachdb-operator#116:27
mup_PR cockroachdb-operator#1: initial cockroachdb-operator charm for review <Created by dshcherb> <https://github.com/canonical/cockroachdb-operator/pull/1>16:27
Dmitrii-Shreworked #21216:32
mup_PR #212: Harness: do not emit extra relation changed events <Created by dshcherb> <https://github.com/canonical/operator/pull/212>16:32
Dmitrii-Shnice ^16:32
Dmitrii-Shthanks for making mup_ work niemeyer16:33
niemeyerMy pleasure.. this is still not 100% online as it's running in my laptop for now, but hopefully next week I can finish the migration16:34
niemeyerThis is a separate instance from mup.. eventually mup will die and this will get renamed to it16:35
ChipacaOK guys, i'm off, mostly. Will checkback from time to time to poke at things, but other than that, see you Tuesday!17:14
niemeyerChipaca: Have a good evening and a good holiday17:26
Chipacai've got a slow-cooking pork shoulder going since breakfast time17:26
Chipacathe whole house smells of it17:26
Chipacaso it's off to a good start i reckon :-)17:26
niemeyerPoor neighbors :P17:27
Chipaca:-D17:27

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