/srv/irclogs.ubuntu.com/2019/07/23/#juju.txt

achilleasajam: I have pushed some commits to the charm.v6 PR to make the tests easier to read. If it looks good I will push a cleaned up commit log and merge08:40
stickupkidjam, you got 5 minutes to discuss the following https://github.com/juju/python-libjuju/pull/321#discussion_r30590067308:41
jamstickupkid: sure, I need about 10min then we can chat08:41
jamachilleasa: lgtm09:01
jamstickupkid: heading to HO09:01
stickupkidjam, here is the pinned version of the facades https://github.com/juju/python-libjuju/pull/321/commits/3ecc14fcc65bebfcebe402892b7074b14c2fa4f711:43
stickupkidjam, the client now very roughly (v1) states which version it knows how to talk about - if you want the latest and greatest, you have to bump this and understand the changes11:44
achilleasaCan I get a quick CR on https://github.com/juju/charm/pull/285? It's just a spelling typo fix12:10
manadarthml: All caught up with rebasing/merging. Latest one is for review here: https://github.com/juju/juju/pull/1045512:21
hmlmanadart:  good news. looking12:22
hmlmanadart: did my pr get closed when the merge completed on your pr?12:26
manadarthml: Yeah: https://github.com/manadart/juju/pull/112:28
hmlmanadart: darn it, it won’t let me change the  backing.  oh well12:29
hmlmanadart:  i can review for you.  it’d be easier if someone else could qa though12:30
achilleasahmmm bringing my charmrepo.v5 changes into juju breaks stuff as some of the code needs macaroon-bakery.v2 and other parts need macaroon-bakery.v2-unstable... does anyone have a bit of time to pair with me to help?12:40
jamachilleasa: presence lgtm12:51
jamstickupkid: minor tweak in that we need a way to specify that we could support >1 version. so the version pointer needs to be a list, and we should pick the highest version that is in both lists.12:52
jamstickupkid: otherwise, I like it a lot12:52
stickupkidjam, right yeah, ok makes sense12:53
jamstickupkid: I think it is "max(set(known).intersect(set(discovered)))" with caveats for things like "no set overlap"12:55
jamunlikely to happen in practice so we can be a bit jankier there as long as seeing a facade we don't know about doesn't kill us from using all the ones we *do* know about12:55
jamstickupkid: speaking of, should we set "facades[-1]" for ones we don't know, or should we just pretend they don't exist ?12:56
stickupkidjam, nice, ok12:56
stickupkidjam, so i think they shouldn't exist, but people use the clients directly so i'm unsure12:56
jamstickupkid: k, so to the Shim, I would say they don't exist. to the list of what is available for someone using a client directly I'm less concerned. It would be good to have something like "available facades"12:57
stickupkidagreed12:57
jamall the versions the libjuju could give you intersected with the versions the server supports12:58
stickupkidyeah12:58
jamstickupkid: 10453 reviewed13:10
hmlstickupkid: there were some FAILs in the test with the weird make end.  trying again13:13
stickupkidjam, replied https://github.com/juju/juju/pull/1045313:15
stickupkidjam, https://github.com/juju/python-libjuju/pull/321/commits/e4d7279f91e1792a3b1afd5bab1b7fe3735c4a96 pylibjuju now picks the best between what it knows and what the api server knows \o/13:35
hmlmanadart:  slice of az is now rebased and ready for review:  https://github.com/juju/juju/pull/1045614:04
manadarthml: OK.14:05
manadarthml: Trade you for forward-merge: https://github.com/juju/juju/pull/1045814:16
hmlmanadart:  i have one more pr for 2.6 if you don’t mind waiting an hour.  had to fix a merge conflict,  pushing up now to merge the pr.  :-D14:18
hmlmanadart: and yes i’ll review the merge into develop14:18
stickupkidah damn it, not this again go install github.com/juju/juju/acceptancetests/repository/trusty/fill-logs/actions: build output "/home/ubuntu/go/bin/actions" already exists and is not an object file14:31
stickupkidhml, you're right https://github.com/juju/juju/pull/1042414:47
hmlstickupkid: the bug says it’s reproducable in 2.6 which makes me wonder about the clouds.yaml and credentials.yaml.14:49
hmlstickupkid: i never added credentials for local anywhere14:49
stickupkidhml, yeah... i did fix this when i re-wrote the LXD credentials stuff a long time ago, so was surprised it broke14:49
stickupkidhml, i think something broke 2.5 and then anastasia fixed it with her credentials work for 2.614:51
stickupkidhml, maybe not worth fixing tbh14:51
hmlmanadart:  sequence for spaceid is on a per model basis yes?14:54
manadarthml: Yes, same collection/mechanism as machine IDs etc.14:54
hmlmanadart: does the sequence for a model migrate too?14:55
manadarthml: Yes. The sequences collection is imported early, so everything works - later migration logic can add entities with the next available IDs and such.14:57
hmlmanadart:  if i migrate a model from develop to pr base controller, the spaces ids go from 1-4 to 5-8.  if i migrate again from a pr based controller to other pr based controller, the ids stay 5-8.15:03
manadarthml: Yes. Because develop got the IDs before juju/description was updated, so they were not transported in the serialised model.15:09
manadartSo new ones get created at the other end.15:09
manadartMigrations between stable releases should be OK though.15:10
hmlmanadart:  right… between stable releases they stay the same.15:10
* manadart nods.15:10
manadarthml: Approved the AZ patch too.15:11
hmlmanadart: approved the merge15:11
hmlty15:11
manadarthml: Ta.15:12
stickupkidhml, fixed 2.5 issue :) https://github.com/juju/juju/pull/1045915:23
hmlstickupkid: ack - will look at it this afternoon if that’s okay15:24
stickupkidhml, fine by me, if it works can you $$merge$$ it for me15:24
hmlstickupkid: :-)15:24
stickupkidhml, ta15:25
achilleasacan I get a CR on https://github.com/juju/juju/pull/10460? This touches the deploy code so please take your time and try to break it ;-)17:24

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