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