/srv/irclogs.ubuntu.com/2018/07/18/#juju.txt

babbageclunkveebers: do we need to be able to build on go 1.8 any more? Is it safe for me to use a type alias?00:57
babbageclunkI don't absolutely need it, would just simplify some tests I'm writing that need to pass around a lot of funcs taking map[corelease.Key]corelease.Info.00:58
anastasiamacbabbageclunk: m not veebers, but I do not think so... should 1.10 be backward compatible anyway? i would have though we only have 1 mayb 2 releases in 1.9 like 2.1 and mayb 2.2 ...01:09
babbageclunkanastasiamac: well, I'm trying to use syntax that was introduced in 1.10, and I *vaguely* remember someone needing to remove a type alias for some reason... not sure whether it's still needed.01:11
anastasiamacbabbageclunk: ah.. ur memory is better than mine :)01:11
babbageclunkoh sorry, introduced in 1.901:12
anastasiamacbabbageclunk: my first feeling is "no, don't worry about prev go vesions" :) we r on 1.10, developing for 1.10 and ci uses 1.10 as well...01:16
veebersbabbageclunk: sorry I'm AFK for the arvo. Um yeah I agree with anastasiamac go with 1.10, especially on develop. I can't think of a reason to need 1.8 compat at this stage01:18
babbageclunkveebers: oh right, forgot sorry! Thanks both of you - I'll use it then. Worst case, I can remove it if needed later.01:28
=== CyberJacob_ is now known as CyberJacob
=== jacekn_ is now known as jacekn
stickupkidmanadart: when you've got a sec https://github.com/juju/juju/pull/894508:57
manadartstickupkid: Commented.09:39
stickupkidmanadart: so rick noted that he wanted to see this, but having done it, I'm with you, I just think it was a safety net that said if you wanted clustering, then we can make sure that we're talking the same thing09:40
manadartstickupkid: If your server is clustered, then its API supports clustering (> 3.0).09:42
manadartI'd put it on ice and talk to Rick when he's better.09:42
stickupkidmanadart: i think this is superfluous in the end, and by the very nature the underlying nature will return false for everything < 3.009:44
manadartstickupkid: Ja.09:44
stubcory_fu: I'm not sure if this is the same issue I saw before?  https://pastebin.ubuntu.com/p/XrByccMWyd/ . I think here the relation is gone (it is during teardown), and the endpoint lookup returns None, and it falls over10:05
stubActually, the failure is in the install hook so the relation certainly doesn't exist at that point10:09
stubcory_fu: https://pastebin.ubuntu.com/p/fR8kjtvJQT/ does work, and  is better anyway. But it would be nice if we could handle this better.10:23
stubWould be ugly though.10:26
stubsome special case rule 'if the handler accepts a single, required parameter and the relation used for RelationBase style handler invokation is None, skip calling the handler'10:29
stubOr fail better if silently skipping isn't an option.10:29
stubMaybe better for endpoint_from_state to never to return None if a suitable relation is defined, even if it hasn't been joined yet.10:31
=== wpk_ is now known as wpk
stickupkidDmitrii-Sh: your PR failed with ProxyUpdaterSuite.TestSnapProxyConfig14:13
stickupkidlink http://ci.jujucharms.com/job/github-check-merge-juju/2412/consoleFull14:13
Dmitrii-Shstickupkid: ok, I will check the test out and modify it14:19
Dmitrii-Shstickupkid: should be easy enough14:19
jamexternalreality: manadart: now that we have a hash, you're building the snap into the 2.4 or latest candidate channel?14:22
manadartjam: I believe it will go to candidate channel in the 2.4 track.14:24
=== ryebot_ is now known as ryebot
domcHello, I've installed charm 2.3.0 and charm-tools 2.2.4 and I'm trying to create a simple charm using command "charm create vanilla", is that supposed to still work? I am unable to get it to work, I keep getting "TypeError: a bytes-like object is required, not 'str'" in /snap/charm/158/lib/python3.5/site-packages/charmtools/templates/reactive_python/template.py14:55
Dmitrii-Shstickupkid: just modified the PR15:41
stickupkidJuju cloud instructions for setting up a LXD Cluster can be found here: https://discourse.jujucharms.com/t/setting-up-lxd-cluster-as-a-juju-cloud/7316:17
rick_h_stickupkid:  woot!17:02
stickupkidrick_h_: manadart spent some time cleaning it up and verifying it for me - so thanks to him :D17:02
rick_h_bdx: magicaltrout cory_fu ^17:03
rick_h_zeestrat: ^17:03
rick_h_Ty too manadart. Solid team effort17:03
rick_h_So awesome17:03
cory_fuNice17:04
rick_h_kwmonroe: as well ^17:04
rick_h_Any chance to.bang on it feedback welcome17:04
Dmitrii-Shstickupkid: could you trigger another build? :^)17:13
stickupkidDmitrii-Sh: sure17:13
Dmitrii-Shthx17:13
Dmitrii-Shstickupkid: looks like the test went well, thanks again17:46
bdxstickupkid, mandart: that is just awesome! thanks!18:06
babbageclunkhey hml, did you see my answer about the featureflag worker?20:33
hmlbabbageclunk: i did…20:33
hmlbabbageclunk: have to circle back to see what can be done for a non controller machine agent20:33
babbageclunkhml: you signed out before I could say, I don't think it would be *too* hard to change it to work via the api20:34
hmlbabbageclunk: hmm20:35
babbageclunkhml: the main difficulty is just the mismatch between the state.NotifyWatcher and watcher.NotifyWatcher (I think)20:36
hmlbabbageclunk: would it require a new featuretag manifold type?  or just modifications to the current?20:38
babbageclunkI think you could paper over the differences in the manifold with only minor changes to the ConfigSource interface. The manifold would need to switch between different input sources - either the APICaller or State, and wrap them differently to be ConfigSources.20:40
babbageclunkhml: want to have a hangout to chat about it?20:44
hmlbabbageclunk: can we do it tomorrow?  my brain is on other topics right now.  :-)20:45
babbageclunksure sure20:46
hmlbabbageclunk: ty20:50

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