[05:24] morning all [09:02] morning all! [10:56] Muy buenos días a todos! [10:57] facubatista: heyy [11:01] Chipaca, meeting? [11:03] facubatista: omw [12:29] Chipaca, so, there's no "easy" or "integrated" way to make argparse to support a longer help for the command alone [12:29] facubatista: i'm listening [12:31] I mean, if I do `charmcraft version -h`, the machinery of argparse triggers in, not allowing us to have contron on the output (unless we keep digging with hacking its internals), and it doesn't have a field to show a "long description" [12:32] Chipaca, so, we could keep digging, but maybe is to first understand which are all the changes we'll need to do regarding help messages... we may totally craft a HelpFormatter if it's very different than the default [12:32] Chipaca, IOW, what I propose is to forget about charmcraft#3 until we have news and directions from UX [12:32] Issue charmcraft#3: Support for long help texts from each command [12:33] facubatista: we already have that direction [12:33] facubatista: but i'm ok with slipping charmcraft#3 due to it turning out to be more work [12:33] Issue charmcraft#3: Support for long help texts from each command [12:36] Chipaca, ok [12:46] i'm going to go figure out lunch before it's tea time [13:11] Chipaca, please remember this: https://github.com/canonical/charmcraft/pull/57 [13:11] PR charmcraft#57: Make pip list current packages before proceeding with the install [13:11] (note I re-did the PR, now from the forked project) [13:11] PR operator#338 opened: ops/storage.py: Move SQLiteBackend [13:19] facubatista: how could i forget [13:19] (answer: easily) [13:19] dramatically [13:19] libnghttp2.so.14 [13:19] sounds a bit rude [13:20] poor http2 [13:21] * Chipaca close to having a working snap [13:29] woooo [13:30] 9.1MB for a working snap including git and enough helpers to pull https [13:34] facubatista, jam, standup? [13:35] oops [14:14] Chipaca, I'll need your +1 on #338 at some point :) [14:14] PR #338: ops/storage.py: Move SQLiteBackend [14:22] jam: you've got it [14:23] jam: facundo'll need your +1 on charmcraft#57 also :-D [14:23] PR charmcraft#57: Make pip list current packages before proceeding with the install [14:32] facubatista: meeting? [14:46] facubatista: booooooo you missed the meeting boo [14:46] * Chipaca boos [14:49] Chipaca, ugh [14:49] there's something wrong with my notifications today [14:49] * Chipaca boos some more [14:50] damn, I super wanted to be in that meeting [14:52] ok, pulseaudio is sending the irc audio notification through the headset [14:52] even if there's no headset connected :/ [14:53] ufa [14:54] * facubatista will need to reboot, probably, to fix this [15:01] Chipaca, any particular outcome/progress? [15:18] facubatista: the good news is, there is another one next week [15:19] facubatista: also, we should probably consider moving to click [15:25] Chipaca, ack [15:25] facubatista: big asterisks on the click thing though :) [16:56] facubatista: charmcraft#58 might be of interest to you [16:56] PR charmcraft#58: changes to snapcraft.yaml, and version, for 0.2.0 [16:56] might [16:56] facubatista: my devious plan is to land charmcraft#57 to master before landing that [16:56] PR charmcraft#57: Make pip list current packages before proceeding with the install [16:57] Chipaca, I'm *so* glad you're doing the snapcraft part :p [16:58] facubatista: I am too. At this point I have Opinions about it. [16:58] Chipaca, I wonder how much of that hardcoded listings will change in time; it will be a maintenance problem? [16:59] facubatista: worst case, we delete the whole stanza and the snap grows 5× [16:59] not a terrible end [16:59] ack [16:59] facubatista: for now, it works like this [16:59] facubatista: at some point maybe there'll be a better way [16:59] (like being able to call out to a git snap) [16:59] yeap [17:00] almost all the really ugly bits is git [17:00] although picking and choosing python libs is also a pain, it's not as random [17:01] facubatista: for reference, I've done this with the icdiff snap, and it hasn't broken nor needed updated since I created it a couple of years ago [17:01] needed updating* [17:01] Chipaca, nice [17:01] for 0.3, tab completion [17:02] icdiff, since 2018-09 (so just under 2 years) [17:03] filed charmcraft#59 for that [17:03] Issue charmcraft#59: tab completion in-snap [17:35] PR operator#338 closed: ops/storage.py: Move SQLiteBackend [17:39] Chipaca, facubatista operator#323 updated [17:39] PR #323: 317 state get [17:51] Chipaca, I don't like pointing the user to the logfile when CommandError [17:53] Chipaca, or at least we need another exception that is "ended in error", but more gentle [17:53] for example, it doesn't make sense to point the user to the logs when: raise CommandError("the requirements file was not found: {!r}".format(str(fpath))) [17:54] but it does make sense when: raise CommandError("problems installing dependencies") [17:54] maybe we need a CommandCrashed (pointing user to the logs) and CommandError (more gentle) [17:55] what do you think? [18:46] facubatista: sounds like it, yes [18:47] facubatista: the difference being, i think, that in one case we can easily summarise the problem in Human, whereas in the other we can't [19:04] Chipaca, the difference for me, which I'm not finding how to express in the name of the error class, is "here's a problem that I can explain you and give you some hint about how to solve", and "we found a problem because something exploded beneath us and we don't know really what or why" [19:04] facubatista: KnownError(CommandError)? [19:05] the only case so far for the second case is when installing dependencies [19:05] even a error from the store is a "controlled" one [19:06] mmm... IF the store is really telling us an error in a field, it's a controlled one [19:06] if the store explodes in unpredictable ways, is also the second case [19:06] CommandControlledError vs CommandUnknownError [19:07] ThisIsSomewhatExpectedError vs WhatWillWeDoWithAllThisBloodError [19:58] Chipaca, so, release? [20:45] facubatista: looks like it [21:30] facubatista: think you can write up a release blurb? [21:30] facubatista: for https://github.com/canonical/charmcraft/releases/edit/untagged-c8c90d68c4d08c8e2547 === ChanServ changed the topic of #smooth-operator to: general discussion of the operator framework || github.com/canonical/operator || ops 0.6.1 || charmcraft 0.2.0 [21:35] facubatista: edit https://github.com/canonical/charmcraft/releases/tag/0.2.0 when you can (or i can do it tomorrow) [21:38] Chipaca, I can do it, but tomorrow [21:40] 0.2.0 in github, pip, and snap [21:40] facubatista: ⁵ [21:43] EOD here [21:45] * facubatista eods too