[08:37] hmm, github 500ing [08:37] good morning all! [09:00] i think it has something to do with that second octocat overtightening that nut: https://www.githubstatus.com/ [09:00] i could be wrong though [09:18] MarkMaglana: possibly related to a small github project being on frontpage of newsie [11:09] Muy buenos días a todos! [11:11] Chipaca, which project? [11:11] facubatista: https://github.com/dabeaz-course/practical-python [11:12] gracias [11:27] * facubatista brb [12:16] Chipaca: I'm going to go with that second octocat. [12:16] * Chipaca sets the octocat on fire [12:16] MarkMaglana: and now? [12:16] * Chipaca forgot to not be evil [12:16] See. Now Github is OK for me again. [12:16] now you know their secret [12:39] Chipaca, may you take a look (as in "initial light review") at https://github.com/canonical/charmcraft/pull/43 before our standup today? thanks! [12:39] PR charmcraft#43: First draft of interaction to the store [12:39] facubatista: i may :) [12:39] i june! [12:39] thanks [14:12] Chipaca, LWP crashed when trying to save the credentials :/ [14:12] File "/usr/lib/python3.6/http/cookiejar.py", line 1846, in lwp_cookie_str [14:12] keys = sorted(cookie._rest.keys()) [14:12] AttributeError: 'NoneType' object has no attribute 'keys' [14:13] welp :) [14:13] that answers that question i guess [14:15] uff, that thing pulls in protobuf :-( [14:16] and pynacl [14:22] Chipaca, nice things to know to avoid taking the "let's rewrite this" path [14:53] gah, why am i looking at macaroonbakery code instead of at yours :-( [15:03] facubatista: fwiw, wrt cookie jars, do you have the full traceback? i'm curious [15:04] Chipaca, https://paste.ubuntu.com/p/YKvgpzftsm/ [15:09] facubatista: charmcraft#33 needs a master merge and then it can land [15:09] PR charmcraft#33: Refactored all the message sending to the user, including storing everything in a file [15:09] Chipaca, thanks! [15:09] facubatista: a reminder that I'd really like you to not use branches on the project itself for development [15:09] Chipaca, ah, we forgot to talk about it [15:10] Chipaca, I mean, why? it's simpler [15:10] facubatista: it's untidy, and it dirties the project itself, meaning anybody cloning the project also pulls 'your' branches [15:11] Chipaca, we could delete those old branches... [15:11] facubatista: and when we start having release branches it'll make them harder to find [15:12] ('release branches' here i mean 'we need to cut 0.8.3 but just for this cherry-picked thing, not all of 0.9') [15:12] yeap [15:12] for now we've been lucky in that all releases have just been master, but that'll not last :) [15:13] ok [15:13] facubatista: i'd be interested to know what aspect of your workflow is harder because of this though, as locally it's no harder [15:14] maybe there's some extra configuration i do without thinking at this point? [15:14] Chipaca, I always considered "forks" to be something to be done when you didn't own the project [15:15] Chipaca, if the 99.9% of the branches come from a 2-4 people, just use the project's repository [15:21] facubatista: that seems like an arbitrary us-vs-them thing to me [15:21] anyhoo, i need to step out for a bit, need to get the boys over to their mum's [16:25] facubatista: also having it in branches fires a lot more traviseses [16:25] (that one we can fix -- but we haven't) [16:45] facubatista: i merged master into 33 and it's good to go, but i'll let you merge it [16:46] Chipaca, landed, thanks [16:57] i'm going for a run [16:57] facubatista: have a great weekend! [16:58] Chipaca, thanks! same for you [17:57] Chipaca, ajá! it looks some stuff from private internal modules are also exposed in the main module, publicly [17:57] Chipaca, this doesn't look so bad, now [18:00] and this is why documentation is important :p [20:55] * facubatista eods and eows! [20:55] see you all on Monday