/srv/irclogs.ubuntu.com/2017/05/25/#snappy.txt

niemeyercachio_afk: Yeah, definitely.. if it's properly designed I'd be happy to include it01:58
cachio_afkniemeyer, ok, I'll push it on friday, tomorrow is national holidays in argentina03:11
=== cachio_afk is now known as cachio
mupPR snapcraft#1334 opened: tests: use the fake apt cache in deb unit tests <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1334>05:35
mupBug #1693423 opened: initramfs error while loading Custom ubuntu core Image on X86 but it works fine in KVM <Snappy:New> <https://launchpad.net/bugs/1693423>06:01
pstolowskigood morning!07:11
zygahello :)07:53
* zyga is on his way to the airport07:53
Chipacamorning peeps07:59
mupPR core-build#13 opened: Androidboot support <Created by alfonsosanchezbeato> <https://github.com/snapcore/core-build/pull/13>08:00
zygaChipaca: hey, good morning08:12
zygaI was wondering if anyone is working today, lots of folks have a day off08:12
* zyga goes offline to conserve battery, ttyl08:23
pedroniszyga: hi, I woild be off, but I'm swapping with Monday08:29
pedronisinstead, so I'm working today08:30
pedronisChipaca: hi, I re-nitpicked a tiny bit, otoh I maybe confused08:52
Chipacapedronis: nicht genitpicken!08:54
Chipacapedronis: better now?09:01
mupPR snapd#3401 opened: tests: move static and unit tests to spread task <Created by fgimenez> <https://github.com/snapcore/snapd/pull/3401>09:02
nottrobinis there any way to list all available architectures & versions from the CLI? https://forum.snapcraft.io/t/list-available-architectures-versions-through-the-cli/78209:04
Chipacanottrobin: from snapcraft?09:07
Chipacaah, forum post09:07
Chipacaanswering there09:07
pedronisChipaca: thank you, +1ed09:10
Chipacanottrobin: there you go09:13
pedronisso sometimes some prepare project takes 300+ s , sometimes it timeouts taking 20mins09:21
Chipacayeap09:26
ChipacaI'd say we bump that timeout, but given that travis itself times out at ~50, it'd be making things worse09:27
pedronisdo we know which bit goes into taking 20+ minutes ?09:27
pedronisit seems we don't have inner timestamps09:27
pedronisso hard to tell09:27
ChipacaI myself do not09:27
ChipacaI wish spread split the project prepare out09:27
Chipacasomehow (*handwaves*)09:27
Chipacaso it can be done async ahead of time09:27
Chipacalike, have a pool of these things pre-prepared09:28
Chipacabut that's probably very hard :-)09:28
niemeyerHello!09:38
niemeyerJust spent the last 1.5h reviewing the general snapctl PR.. but will try to get some more sleep while I can! :)09:39
niemeyerSee you soon.09:39
Chipacaouch09:43
abeatopedronis, hey, mind removing the "Blocked" label from https://github.com/snapcore/snapd/pull/3353 ?09:46
mupPR snapd#3353: Add support for reboot parameter <Blocked> <Created by alfonsosanchezbeato> <https://github.com/snapcore/snapd/pull/3353>09:46
pedronisabeato: done09:47
abeatopedronis, thanks09:48
abeatoit looks like CI is failing btw, it gives me those ssh timeouts error all the time09:49
Chipacaogra_: i think you're off cavorting today, but if you happen to not be, https://askubuntu.com/questions/867121/snappy-ubuntu-core-64-bit could use a more authoritative answer i think09:51
Chipacaheh, should've linked https://askubuntu.com/q/867121/711 to get brownie points09:51
Chipaca¯\_(ツ)_/¯09:51
mupPR snapd#3363 closed: cmd: test everything (100% coverage \o/) <Created by chipaca> <Merged by chipaca> <https://github.com/snapcore/snapd/pull/3363>09:55
pedroniscool10:01
pedronisChipaca: have you seen an error about   linode:debian-unstable-64:tests/main/snapd-reexec ?10:04
ChipacaI don't think I have10:04
pedronisah10:05
pedronisit seems you changed in your branch10:05
pedronislet's see if merging master helps10:08
mupPR snapd#3400 opened: many: stop "snap refresh $x --channel invalid" from working <Created by chipaca> <https://github.com/snapcore/snapd/pull/3400>10:23
ondraogra_ ping10:47
Chipacaondra: holiday in the germanies10:55
ondraChipaca aha, ,makes sense as I can't see any of them online :)10:56
Chipacaslowly we might be learning to take time off, at least in small chunks10:56
* Chipaca curses at spread tests in the abstract11:07
mupPR snapd#3374 closed: partition: add directory sync to the save uboot.env file code <Created by mvo5> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/3374>11:08
pedronisChipaca: because they fail with abandon? or something else11:26
Chipacapedronis: because I can't just write a handwavy thing and have them dtrt :-)11:26
pedronisah11:26
zygao/11:50
zygaChipaca: how's the day?11:51
Chipacazyga: not bad! how's yours?11:51
zygaChipaca: the joys of travel from A to B11:52
zygaChipaca: I have an hour till boarding, time to do some work for a change11:52
Chipacaspeaking of work11:53
Chipacai'm going to go make myself some lunch11:53
zygaenjoy :)11:54
=== alan_g is now known as alan_g|lunch
=== alan_g|lunch is now known as alan_g
* zyga boards the plane13:22
Chipacafgimenez: if you look at https://codecov.io/bash13:27
pedronisniemeyer: snapd#338513:28
mupPR snapd#3385: cmd: add stub new snap-repair command and add timer <Created by mvo5> <https://github.com/snapcore/snapd/pull/3385>13:28
Chipacafgimenez: there's a check that looks like if [ "$CI" = "true" ] && [ "$TRAVIS" = "true" ] && [ "$SHIPPABLE" != "true" ]13:28
fgimenezChipaca: yeap and on it right now, searching for "TRAVIS_" :)13:28
niemeyerpedronis: Cheers13:28
Chipacafgimenez: and inside that it uses a bunch of TRAVIS_ vars13:28
Chipacayeah13:28
fgimenezChipaca: yep, thx13:28
pedronispstolowski: btw we can already see the problem we mentioned:  func (iface *serialPortInterface) AppArmorConnectedPlug, it gets a slotAttrs but inside is using slot.Attrs13:32
pedronisfor example13:32
pstolowskipedronis, every interface has this problem right now, because we only added placeholders in the API13:33
pedronis:(13:33
pedronisthat's a bit of a bad idea13:34
pedroniswhen do we plan to fix these ?13:34
pstolowskipedronis, these plug/slotAttrs are not even filled in right now13:34
pedronisyea, anyway we really to rethink when we pass Plug/Slot to interfaces13:34
pedronisor maybe rename Plug/Slot.Attrs to StaticAttrs and go from there or something13:35
=== chihchun is now known as chihchun_afk
pstolowskipedronis, I intended to re-factor all interfaces to use plugAttrs and slotAttrs after the current branch lands, but if we agree on changing all these methods to drop plug and slot, then I will do it first as a prerequisite for current PR13:39
pedroniswell before dropping we need to understand how they use those,  best would be to drop them and pass something else, second best is to at least rename Attrs on Plug and Slot13:40
pedronispstolowski: I'm also not sure how we use the *Permant* variants, are those called once?13:43
niemeyerpedronis: Reviewed13:43
Chipacapedronis: spread tests passed on snapd#3400 fwiw13:44
mupPR snapd#3400: many: stop "snap refresh $x --channel invalid" from working <Created by chipaca> <https://github.com/snapcore/snapd/pull/3400>13:44
pstolowskipedronis, what do you mean with 'are those called once' ?13:44
pedronispstolowski: I mean they can also use the static attributes it seems13:47
pedronisgiven they take only Plug and Slot13:47
pedronisor maybe they should use no attributes at all?13:48
pstolowskipedronis, I think it's ok for them to use static attributes from the yaml13:53
pedronisbut now we say that we can overwrite them13:53
pedroniswhat does that even mean then13:53
pedronisthe pieces still don't feel like they are clicking together right13:54
pedronispstolowski: anyway some permanent stuff is indeed using attrs, so I wonder what that means to the idea that hooks can override everything13:59
pstolowskipedronis, the Permanent* methods see whatever Sanitize* set. but on Connect hooks will be free to overwrite attributes and this will be visible to "connected" snippets.14:00
pedronispstolowski: yes, but that doesn't make a lot of sense for stuff that the Permanent* bits used/assumed14:00
pstolowskipedronis, indeed, i hear you14:01
pedronisunless we use validate somehow to check per interfaces that stuff that was used by permanent is overriden14:01
pedroniss/is/is not/14:01
pstolowskisounds complex14:02
pedroniswell something is off here14:02
ogra_jdstrand, i'd appreciate a manual approval of https://dashboard.snapcraft.io/dev/snaps/7691/rev/2/14:03
pedronispstolowski: maybe getting back to no overriding but solving the defaults problem differently might be better14:03
jdstrandheh, I was just going through store reviews now :)14:03
pstolowskipedronis, i was going to say that.. perhaps the idea of protecting attributes coming from yaml made sense14:03
ogra_hah, snap* :)14:03
pedronispstolowski: at least for a first iteration, we can relax later, but right now it feels a bit like boiling too much ocean in one go14:05
pedronisotherwise14:05
pstolowskipedronis, why don't we leave the problem of defaults to interfaces code? I mean, what's stopping interface code from having a "default-foo" attribute, and then using it as 'foo' if foo wasn't set at runtime?14:06
jdstrandogra_: done14:06
* ogra_ hugs jdstrand 14:06
* ogra_ goes back on vacation :)14:06
* jdstrand hugs ogra_ back14:06
jdstrandogra_: enjoy your holiday :)14:06
pedronispstolowski: we need the defaults in the attributes before we run the policy checks14:07
pedronisthat's what's about mainly14:07
pstolowskii see14:08
pedronispstolowski: the simplest thing I could think of, is we don't let override in general, but the interface can have an optional method to return a list of attrs that can be overridden (usually they will be ones with defaults that is ok to change later)14:18
pedronisas far as I know right now we have one interface with this need14:18
pedroniscontent14:18
* pedronis break14:21
ryebotIf I install a snap from a file, do they ever subsequently get updated from the store?14:27
ryebotor are they stuck at what I installed with?14:27
pedronisryebot: just the .snap without accompanying  assertions (as one can get with snap download) will be stuck14:31
ryebotpedronis: that's perfect14:31
pedronisryebot: I fear that sort of reaction, it also completely unchecked14:32
ryebothaha ;)14:32
Chipacaryebot: it's also how you build next year's botnet14:35
* ryebot learns how to mine btc14:35
pstolowskiniemeyer, +1 for SNAP_COOKIE and cookie;15:01
pstolowskiniemeyer, then /var/lib/snapd/cookie/ in the fs? (singular 'cookie', not plural)15:02
niemeyerpstolowski: Yeah, that sounds good I think15:02
pstolowskiniemeyer, ok, will change, thanks!15:04
=== chihchun_afk is now known as chihchun
pedronisChipaca: is it possible that I have a version too old of shellcheck?15:51
Chipacapedronis: maybe? why?15:51
pedronisI'm getting15:51
pedronis# shellcheck source=tests/lib/dirs.sh15:51
pedronis^-- SC1073: Couldn't parse this shellcheck annotation.15:51
Chipacapedronis: it's also possible it's too new :-)15:51
Chipacahrmm15:51
Chipacahadn't seen that one15:51
Chipacapedronis: in travis, or locally?15:52
pedronislocally15:52
Chipacaand if you're getting this, does this mean travis doesn't actually _have_ shellcheck :-)15:52
pedronispossibly15:52
Chipacapedronis: what version of shellcheck do you have?15:52
pedronis0.3.715:52
Chipacaah, i bumped mine to 0.4.4-2 to check some things mvo spotted15:54
Chipacapedronis: http://mirrors.kernel.org/ubuntu/pool/universe/s/shellcheck/shellcheck_0.4.4-2_amd64.deb15:54
Chipacapedronis: that one should work just fine15:54
pedronisI suppoe travis / spread is not running it at all15:55
Chipaca0.4.4-4 uses a newer ghc and needs a rebuild to work properly though, so avoid it (or rebuild it … but that needs a newer ghc … fun all around15:55
Chipacaspread almost certainly not, given this15:55
Chipacasadface15:55
pedroniswell, it's optional, not sure why you though it should be there ?15:55
Chipacapedronis: you assume i thought15:56
mupPR snapd#3402 opened: many: error types should be called FooError, not ErrFoo <Created by chipaca> <https://github.com/snapcore/snapd/pull/3402>15:57
pedronisChipaca: yes, that one from kernel.org works16:02
Chipacapedronis: it's from yakkety16:02
Chipacahttps://packages.ubuntu.com/yakkety/amd64/shellcheck/download16:02
Chipacajust thought i'd save you a click16:02
pedronisChipaca: I'll look at your refresh branch tomorrow at this point16:10
Chipacapedronis: fair enough16:10
zygaChipaca: hey16:23
zygaChipaca: do you have a moment?16:23
zygaChipaca: can you please refresh my memory on channels and tracks,16:24
zygaChipaca: is it a tuple like (2.x/stable) or am I missing something?16:24
zygaChipaca: and what are the precise terms (stability levels, risk levels, etc)16:25
Chipacazyga: every channel has four risk levels16:25
Chipacazyga: the default channel is called latest16:25
Chipacawait16:26
Chipacano, tracks16:26
Chipacagah16:26
Chipacaman it's a bad day for this16:26
zygahaha16:26
Chipacazyga: s/channel/track/ in the above :-)16:26
zygashould I use the word channel or track to describe the concept?16:26
Chipacazyga: channels come in four risk levels16:26
Chipacaah, you mean in an intro to somebody who's never seen it before sense?16:27
zygayes16:27
Chipacastart with channels as risk levels16:27
* zyga makes some slides16:27
zygaChipaca: are those tuples?16:27
zygaChipaca: can I say (risk-level, channel) ?16:27
Chipacano, just stable/candidate/potato/edge16:27
ChipacaI mean, growing the concept didactically in the same way it grew historically works16:28
Chipacatalk about channel and risk, and then take a step back and introduce tracks16:28
zygaok, can you give me four examples in growing measure of complexity?16:28
Chipacazyga: hypothetical, or actual?16:29
zygaChipaca: educational :)16:29
zygaI bet I will learn as much as my audience now16:30
Chipacazyga: as a first step, you could have a snap that is very low maintenance, that's not seeing active development16:31
Chipacazyga: so all you have is the snap in stable; everybody gets that16:31
Chipacazyga: a good example might be "hello-world", if we can convince mvo to close the spurious channels16:32
Chipaca(we've got the same revno in everything)16:32
zygahaha :)16:32
Chipacazyga: as a next step, you have something in active development, where there is a snap pushed into 'edge' for testing, and it moves through the channels16:33
Chipacafgimenez: are you a collaborator in hello-world?16:33
Chipacazyga: an example of this would be the core snap, for example16:34
Chipacazyga: 'snap info' shows you the progression nicely (when we haven't messed up)16:34
fgimenezChipaca: nope sorry16:35
Chipacazyga: there you can stop and wave your hands and introduce the idea of people doing this kind of qa for stable at the same time as working on the upcoming release16:35
Chipacazyga: or people having LTS as well as current releases16:35
Chipacazyga: and ask how they'd address this16:36
* zyga hears everyone chanting "PPAs"16:37
Chipacazyga: so you then show them the mysql snap16:39
Chipaca(snap info mysql)16:39
zygaooooh16:39
* zyga loves that16:39
zygaincluding the funky unicode arrow :)16:40
zygathanks!16:40
Chipacazyga: and then you talk about doing CI/CD16:40
Chipacazyga: and show them snap info etcd16:40
Chipacazyga: (note the 'ingest' track)16:40
zygawhat is ingest?16:41
Chipacathe burningest of burning edges16:41
* zyga is so glad he asked16:41
zygasounds like a title of a garbage album :)16:41
zyga"the burinest of the burn, the edgiest of the edge" (to queer music theme)16:41
=== chihchun is now known as chihchun_afk
zygathanks16:41
Chipacazyga: actually i think the ingest track there is old (note the revno)16:42
* zyga wonders why in 2017 dragging a slide to another position freezes the office suite for 30 seconds16:42
zygaChipaca: yes, looks like "gimme tasty but as safe as it gets"16:43
zygaanyway, I get the concept16:43
zygait's whatever people want16:43
Chipacaevery project gets to define what they mean, yes16:43
Chipacaalthough, AIUI, tracks are manual, and I think we ask for semantic versioning or sth like that? noise][ might know more16:44
zygaaha16:44
zyganoise][: ^^ do we have semantic versioning in track names?16:44
noise][zyga: https://forum.snapcraft.io/t/channel-terminology-and-policy/55116:45
zygaoh, great16:45
noise][you have some leeway, but that's the general guidance on policy16:45
zygalibreoffice, why is it hard to remove a slide... why do you suck watts doing so...16:46
zygaChipaca: suggestion, snap known <tab><tab> should complete on assertion types16:47
zygawould help in discoverability16:47
zygawe don't have a forum topic that discusses assertion types (an overview of each) do we?16:49
Chipacazyga: ooh, look at that, nicely documented instead of asking me :-)16:52
pedroniszyga: I do plan to move over and improve the assertion bits from the wiki to the forum in the next weeks16:55
Chipacapedronis: he's dead jim16:57
pedronisah16:58
Chipacareached out on telegram but he might not be there either :-)16:58
=== genii is now known as JuanValdez
=== JuanValdez is now known as genii
Chipacaanyway. EOD for me.17:01
jdstrandroadmr: hey, at your convenience can you pull r881 of the review tools?19:27
roadmrjdstrand: sure! as it happens it's super convenient right now, should have that rolled out early next week19:27
jdstrandroadmr: awesome, thanks!19:28
jdstrandroadmr: actually, gimme a sec. since we're doing this, let me update for the new interfaces19:29
roadmrjdstrand: hehe I have a script now which prepares the merge request for me and pushes the changes ready to merge-request. It even runs the tools against a small snap to ensure they are sane19:30
roadmrjdstrand: (remember that time a file was missing and they didn't even run?)19:30
roadmrjdstrand: and oh sure, let me know and I'll send another merge19:30
jdstrandroadmr: I do remember that time, and I have my own battery of test snaps19:31
jdstrandroadmr: nice!19:31
roadmrjdstrand: heh :) yes, mine is just a thin layer of protection. e.g. you could make the tools just return PASS all the time and I'd never notice ;)19:32
roadmrjdstrand: 882 or should I wait for more?19:51
jdstrandroadmr: that is the one, but I wanted to check the review-tools snap with that. just waiting for it to publish19:56
roadmrjdstrand: oh ok no rush :)19:57
* jdstrand kicks off the test19:57
jdstrandzyhey, fyi, https://forum.snapcraft.io/t/test-failures-with-cannot-create-lock-directory-run-snapd-lock/390/319:57
jdstrandmeh19:58
jdstrandroadmr: ok, yes, r88219:58
roadmrjdstrand: here I go19:59
=== JanC_ is now known as JanC
mupPR snapcraft#1335 opened: errors: Descriptive error message for bad parts named with uppercase … <Created by EduardoVega> <https://github.com/snapcore/snapcraft/pull/1335>22:54

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