/srv/irclogs.ubuntu.com/2017/11/13/#juju-dev.txt

thumperwallyworld: are you looking at the pinger issue?00:13
wallyworldthumper: i had a brief look and will look again a bit later after standup, but need to get some other stuff done first00:13
thumperack00:14
wallyworldthumper: ostensibly our logic should not have changed between .2 and 2.3 so hopefully it's just a simple bug or something00:14
thumperwallyworld: I'm not convinced that it isn't in 2.200:14
thumperit fits the behaviour we see with status taking longer over time00:15
wallyworldcould be, i was just going by what's been commented on te bug00:15
thumperyeah00:15
thumperI've read it too00:15
thumpermore poking needed00:15
wallyworldyup00:15
thumperwallyworld: I'm going to also start looking at the pinger bug02:53
wallyworldthumper: righto, i'm just about to start as well, finished other things02:53
thumperwallyworld: let me know if you want to talk things through03:13
thumperI'm making some progress, but it is slow, and experimental based03:13
wallyworldthumper: just poking around atm to grok the code - about to add some debugging etc03:13
thumperwallyworld: same03:13
thumperI have found that we can trigger it with no charms03:14
thumperjust enable-ha03:14
wallyworldi thought i'd try and undertand it before adding debugging but it's messy so i think debugging it is03:14
thumperso... weird03:14
wallyworldthumper: one initial thought OTTOMH, could be wrong. regardless of the controller vs agent connection, it seems we start a pinger each time an agent logs in, regardless of whether we have previously done so; it seems when we do, we never stop any previously created ones03:21
wallyworldso if an agent bounces say, we just keep on creating new pingers03:21
thumperpossibly03:21
wallyworldjust a thought, i'll try and prove it etc03:22
thumperalthough I'm seeing pingers being created without connections bouncing03:22
thumperalthough now you mention it, I should make sure they aren't bouncing03:22
wallyworldright, that would be for any login03:22
wallyworldi think any connection may create a ne wpinger03:22
thumperwallyworld: HO?03:34
thumperI have some ideas I want to talk through03:34
wallyworldok03:34
thumper1:103:34
wallyworldaxw: small PR for when you get a moment https://github.com/juju/juju/pull/805405:44
axwwallyworld: LGTM05:46
wallyworldty05:47
jamaxw: looks like your Log at TRACE got hung up on a test that was testing that we created a DEBUG message for Wrench06:11
jamhttp://ci.jujucharms.com/job/github-merge-juju/494/console06:11
axwjam: yeah, that's just the forward port to develop - will come back to it when I've got a spare minute06:24
axw1.25 has landed06:24
axw1.25 change*06:24
jamright06:25
thumperjam: I remembered why we had two api connections for the apiservers06:54
thumperhmm...06:54
thumpernope that doesn't work06:54
thumpernm06:54
thumperwallyworld: https://github.com/juju/juju/pull/805507:04
wallyworldlooking07:05
wallyworldthumper: lgtm, one bug down  or 3 to go07:07
wallyworld*207:07
thumperah fark07:24
thumperwe do register the pinger as a worker on the resources07:24
thumperjust on the wrong thing07:24
* thumper digs07:24
thumperat least I *think* it is07:24
thumpermaybe not...07:26
=== frankban|afk is now known as frankban
axwwallyworld: for tomorrow, if you can: https://github.com/juju/juju/pull/8056. back to enable-ha (it's *possible* merging this manifold rejigging into develop will help, but I'll avoid that if possible)09:10
kjackalaxw: wallyworld: Truely sorry for today. Never saw I had to start earlier today. The weekly calendar view does not help much. Appologies09:13
axwkjackal: no dramas, can you make it tomorrow?09:14
kjackalYes, I will be there axw09:14
axwcool09:14
wallyworldaxw: no worries, i'll take a look09:24
wallyworldaxw: reviewed09:49
axwwallyworld: thanks09:49
axwwallyworld: when are we planning to go to rc1?09:51
wallyworldaxw: end of this week10:00
wallyworldif bugs are fixed10:00
axwokey dokey10:00
axwta10:00
rogpeppe1wpk: FYI i just noticed this PR in passing and made a comment: https://github.com/juju/names/pull/8616:02
wpkrogpeppe1: 1. it doesn't have to be 'crypto' safe, and if you're not trying to deliberately get a collision 4 bytes from SHA256 are as good as 4 bytes from CRC3216:08
wpkrogpeppe1: (and it's still quite easy to get a 4 byte collision using sha256)16:08
rogpeppe1wpk: i'd use 16 bytes not 416:08
wpkrogpeppe1: then we loose the name16:09
rogpeppe1wpk: and i wouldn't rule out the possibility of someone deliberately trying to get a collision16:09
wpkrogpeppe1: if an user wants to shoot himself in the foot it's his choice and his right16:09
rogpeppe1wpk: why so? 16 bytes of hash still leaves 32 bytes for the name16:10
rogpeppe1wpk: i mean, why would we lose the name?16:10
wpkrogpeppe1: and 2. we reserve 4 chars for unit id, so 'longlonglongname/0'.ShortenedString() has the same 'name' as 'longlonglongname/1000'16:10
rogpeppe1wpk: ah, so that's the source of the extra truncation?16:11
wpkrogpeppe1: 17 bytes for the name (juju-unit-{name}{32charsofhash}-{4charsforid})16:12
wpkrogpeppe1: yes16:12
rogpeppe1wpk: ok, so 17 bytes for the name is still a reasonable amount16:13
wpkrogpeppe1: I still can't imagine a situation in which user would deliberately try to shoot himself in the foot (and only himself, that's important)16:14
rogpeppe1wpk: the problem might come if unit names might be created based on user-provided data16:14
rogpeppe1wpk: which isn't impossible16:15
wpkin shared model?16:17
rogpeppe1wpk: or a model-as-a-service in some way16:18
wpkit'd have to be single machine in a single model shared between users, do we support that?16:20
rogpeppe1wpk: well, the model doesn't have to be directly accessible - just that the names that some user chooses are used for an application name somehow16:26
rogpeppe1wpk: i know of at least one client where juju is used as an intermediate layer between a high level abstraction and the actual job16:27
rogpeppe1wpk: BTW i just tried with four digits of id, and it "shortens" a 19 byte unit tag to 26 bytes.16:28
rogpeppe1wpk: i think we can probably avoid shortening when the name doesn't actual reach the limit16:29
rogpeppe1wpk: also, i think it might be worth separating the name part from the hash part, otherwise it's not easy to tell which bit is which16:30
rogpeppe1wpk: (i'd probably use a separator char that's not part of a valid unit tag, so there's less danger of mixing them up)16:30
=== frankban is now known as frankban|afk
hmlis ci for pr-merge okay?  i’m getting a message that it’s scheduled to run later? when i click on the link, nothing has run for 3 hours?17:57
mupBug #1732004 opened: arm64 shows 1 vs. 96 cores via Juju GUI version 2.10.2 <juju-core:New> <https://launchpad.net/bugs/1732004>19:11
=== TikTok is now known as michealb
=== rick_h_ is now known as rick_h
=== icey_ is now known as icey
=== arosales_ is now known as arosales
=== wpk_ is now known as wpk
thumperanastasiamac, babbageclunk: I have a couple of PRs up that are in dire need of a review.22:14
babbageclunkthumper: I guess jam should take another look at #8057 - I'll look at #805822:15
babbageclunkthumper: was there another one?22:17
babbageclunkthumper: #8058 approved.22:27
thumperta22:45
wallyworldbabbageclunk: long time no see22:47
babbageclunkwallyworld: hey22:47
babbageclunkwallyworld: wanna have a quick chat?22:48
wallyworldsuppose so22:48
wallyworldif i must22:48
wallyworld:-P22:48
* babbageclunk looks sad22:48
babbageclunkin 1:1?22:48
wallyworldsure22:48
blahdeblahIt must be great to have such a supportive and friendly manager.23:07
thumperblahdeblah: true23:08

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