[02:59] kelvinliu: no rush, here's a small juju run fix for the new actions UX https://github.com/juju/juju/pull/11978 [05:01] kelvinliu: when you get a chance, no rush https://github.com/juju/juju/pull/11979 [05:02] looking [08:52] are we always required to have a metadata in a charm? [08:56] do we have any documentation about what a charm is, at it's raw basic form? [08:56] so i can crib from it [09:47] achilleasa, https://github.com/juju/charm/pull/318 [09:48] if I can't find it, then it might help if I write what I found [09:59] approved; you also need to land against V2 [10:00] ah... nvm it's charm not bundlechanges... doh! [10:20] stickupkid: https://github.com/juju/bundlechanges/pull/67 [10:20] with lots of extra tests :D [10:24] achilleasa, https://github.com/juju/bundlechanges/pull/67/files#diff-f447f119094ea333680948095a672515R769 [10:24] can't you using thisSet.Difference()? [10:24] or are you wanting to exit early? [10:28] difference allocates and populates a new map. Given that the comparison process for the grouping is pretty much O(n^2), I opted for early exit plus 1 less allocation [10:28] though in principle it shouldn't matter much as the number of endpoints is usually small [10:29] achilleasa, i'd say, lets use difference and if performance is an issue swap to that [10:29] premature optimisation etc [10:33] ok, let me amend the last commit [10:38] ok, why does GUIArgs change when doing the exposed related stuff? [10:40] it seems that the general pattern is that we add new fields to guiargs as well [10:40] question is whether that is being used now by the new gui or not [10:40] GUIArgs are dead aren't they [10:40] ? [10:40] jam, will know [10:41] not sure :D [10:41] so I just add extra things to be consistent [10:44] considering we're bumping bundlechanges, we should consider if GUIArgs is required anymore? [10:45] as this is V3, we can land this if it looks OK and I can raise it in standup. If we don't need it we can kill it in master [11:15] achilleasa, got one for you https://github.com/juju/charm/pull/319 [11:15] achilleasa, this encompases the changes we discussed yesterday (dropping the ch: prefix for urls) [11:16] * when using String() [12:01] stickupkid: you bumped the application facade to V13 on develop right? (to add CharmOrigin) [13:27] erm... [13:27] yeah [15:48] achilleasa, no idea why they didn't just go with https://github.com/juju/charm/pull/319#discussion_r485717169 [15:49] achilleasa, they would have been named as well to make it much more readable [15:56] I bet this will come back and bite us some time in the future and we will have to use versioned URLs... [16:08] achilleasa, we have 3 already [16:08] haha [16:37] stickupkid, achilleasa : 'username@" wouldn't work there, because that would be "who am I connecting to the store as" not "who owns this charm". [16:38] jam: couldn't that simply be another query param? e.g. &author=foo [16:39] achilleasa, it certainly could, though in the end we're moving to the Snap model where the namespace itself doesn't show off the author [16:39] eg, it isn't jameinel/juju it is just 'juju' and the owner is off in the details of the project