[03:02] <thumper> very quiet monday here
[03:29] <ec0> now you've done it
[04:50] <hpidcock> wallyworld: for the grade field in the snapcraft.yaml, should this be stable or devel depending on if it's a release snap? see https://snapcraft.io/docs/snapcraft-yaml-reference and also your pr https://github.com/juju/juju/pull/11138/files
[04:51] <hpidcock> do we currently just manually build the dev snaps?
[04:52] <hpidcock> current release scripts just use default grade: to stable
[04:52] <hpidcock> I guess I could sed the snapcraft.yaml to change it
[09:18] <achilleasa> can I get a quick CR on this tiny PR? https://github.com/juju/charmrepo/pull/160
[09:56] <nammn_de> achilleasa: can take a look
[09:57] <nammn_de> stickupkid: up for a 5 min hangout regarding the race conditions a mentioned? May need a pointer or an idea
[09:57] <stickupkid> nammn_de, daily
[09:58] <stickupkid> achilleasa, we should ping wgrant about this
[09:59] <achilleasa> stickupkid: I will when the change lands in juju 2.7 branch
[10:04] <achilleasa> stickupkid: have you brought in your charmrepo changes from last week?
[10:08] <achilleasa> stickupkid: arghh.. 2.7 still uses charmrepo.v3; gotta backport the change
[10:35] <nammn_de> stickupkid: https://github.com/juju/juju/pull/11198
[10:46] <stickupkid> nammn_de, done
[10:51] <nammn_de> stickupkid: ta! I see you are working on the not finding artefacts thing on lxd. Any updates on that one? This one seems to be a great help to me.  Need a helping hand?
[10:52] <stickupkid> nammn_de, ah, not actively atm
[10:52] <nammn_de> stickupkid: small pointers for me, so that I can take that over?
[10:53] <stickupkid> nammn_de, when the test suite bombs, we need to work out why we don't create a output tar.gz file
[10:54] <nammn_de> stickupkid: got it, lookin
[11:07] <achilleasa> nammn_de: or stickupkid quick CR for bringing charmrepo changes into juju: https://github.com/juju/juju/pull/11199 and https://github.com/juju/juju/pull/11200
[11:08] <nammn_de> achilleasa: approved
[11:11] <achilleasa> stickupkid: have you seen this error before? https://github.com/juju/juju/pull/11200/checks?check_run_id=435919954
[11:13] <achilleasa> is charmrepo.v4 gomod-only now?
[11:14] <stickupkid> achilleasa, why does dep care about gomod though
[11:14] <stickupkid> achilleasa, shouldn't it just be a code repo?
[11:17] <achilleasa> stickupkid: yeah... don't get it. The juju .lock file has been updated but the digest looks empty: https://github.com/juju/juju/pull/11200/files#diff-bd247e83efc3c45ae9e8c47233249f18R1436
[11:17] <stickupkid> haha, lol wat
[11:18] <stickupkid> can you rebuild it?
[11:18] <achilleasa> Let me try with modules off...
[11:30] <achilleasa> stickupkid: second time worked... go figure
[13:15] <rick_h> morning party folks
[13:24] <manadart> Morning rick_h
[13:29] <achilleasa> nammn_de: I think we have a flaky test (TestConstraintsOpsForSpaceNameChange). Was that added by the recent work for space renaming? If that's yours you may want to throw in a strings.Sort prior to comparing https://paste.ubuntu.com/p/pnmnxrdBpQ/
[13:30] <nammn_de> achilleasa: yeah thanks! Added that in the next spaces patch
[13:30] <manadart> achilleasa nammn_de: Or use jc.SameContents.
[13:31] <achilleasa> manadart: thanks for the tip; didn't know that was a thing!
[13:31] <nammn_de> manadart achilleasa: sorted it was put in the bigger patch here: https://github.com/juju/juju/pull/11186/files if pressuring I can exclude and put in seperate patch
[13:31] <nammn_de> manadart: ohh did not know that one
[15:23] <stickupkid> rick_h, so the schema tests won't work because both juju 2.7 and develop target the pylib master branch and we don't know if there are breaking changes
[15:24] <stickupkid> rick_h, the easy fix is to add branches back to pylib
[15:24] <rick_h> stickupkid:  boooooo, maybe
[16:17] <stickupkid> manadart, nammn_de maybe we should just push all artifacts to s3
[16:17] <stickupkid> be done with it
[16:22] <manadart> stickupkid: Sounds like a plan.
[16:22] <nammn_de> stickupkid: that sounds like something great.  I can look into that next ci day (may need here and there some consideration points)
[16:23] <stickupkid> nammn_de, we'll still need to get it out of the container though...
[16:23] <nammn_de> stickupkid: yeah thats something i am looking today, if not next week =D
[16:56] <stickupkid> rick_h, ho?
[17:21] <rick_h> stickupkid:  /me jumps in
[17:21] <rick_h> oh wait, that was 30min ago sorry
[17:21] <rick_h> stickupkid:  what's up?
[17:21] <stickupkid> in ho:)
[20:11] <timClicks> morning juju
[20:11] <rick_h> morning timClicks
[20:12] <hml> howdy timClicks
[20:15] <timClicks> it looks like we're starting to see more and more lively discussions on discourse
[20:15] <rick_h> chit-chat
[21:30] <timClicks> where is the source code for the k8s charms in https://jaas.ai/u/juju/#charms? we should flesh out their readmes
[22:03] <babbageclunk> easy review for someone? https://github.com/juju/juju/pull/11202
[22:03] <timClicks> babbageclunk: love those
[22:04] <timClicks> babbageclunk: the old shortwait to longwait switcheroo
[22:08] <babbageclunk> timClicks: ha, thanks!
[23:28] <timClicks> remind me again why there's no default model provided with k8s clouds? I did know once
[23:29] <hpidcock> default is a namespace that exists in a kube cluster
[23:29] <hpidcock> and may be used by stuff already deployed in a cluster
[23:29] <hpidcock> so we
[23:29] <hpidcock> would need a new name
[23:30] <hpidcock> easier to just not create one atm
[23:31] <hpidcock> or if we did, the default model would need special behaviour so it doesn't create the namespace nor delete it. It would also have to be able to play nice with what is already in there/share with another juju controller etc
[23:31] <hpidcock> just too much to deal with.
[23:31] <timClicks> hpidcock: I thought it was to do with the namespace issue
[23:32] <hpidcock> yeah, thats the root of the issue
[23:32] <hpidcock> but whatever way you try to work around it isn
[23:32] <hpidcock> 't nice
[23:33] <hpidcock> a user could delete the namespace then create a model called default
[23:33] <hpidcock> but that still has issues