/srv/irclogs.ubuntu.com/2021/06/08/#snappy.txt

mborzeckimorning06:05
mardy'morning!06:18
mborzeckimardy: hey06:26
mborzeckihmm i have surprisingly few prs open, time to fix that06:51
mborzeckimvo: hey06:59
pstolowskimorning07:03
mborzeckipstolowski: hey07:04
mvogood morning mborzecki and pstolowski 07:09
mborzeckianything intersting happened during the long weekend or yesterday?07:10
mborzeckimvo: do you have more info from pedronis about the lxd issue mwhudson had on thursday?07:33
mborzeckithere seems to have been some confusion about / not being shared and the tricks that we do to fix it07:34
mborzeckipstolowski: can you take a look at https://github.com/snapcore/snapd/pull/10338 ?07:49
pstolowskimborzecki: sure07:49
mborzeckithanks!07:50
mborzeckiquick errand, back in 3007:53
mborzeckire08:45
pedronismborzecki: hi, you saw I commented on golangci-lint again, my worry about goimports is when our current gofmt and goimports will disagree on new code09:19
pedronismborzecki: I also created this:  https://github.com/snapcore/snapd/pull/1034509:20
mborzeckipedronis: yes thanks, i'll be looking at this next, wanted to push out the tweaks to #1033809:21
mborzeckipedronis: as for gofmt, not sure what going on there, i suppose we can either ignore it or disable goimports, although it's quite useful even if there's some misdetection09:22
pedronismborzecki: as I said we could switch to use it instead of gofmt ourselves, but we need to compile it like golangci-lint does09:22
mborzeckipedronis: tbh maybe there's anothe imports linter, bit unfortunate that goimports does the same as gofmt, otoh they do mention it09:30
mborzeckipedronis: fwiw, there's https://github.com/daixiang0/gci which doesn't try to do it all09:32
pedronismborzecki: but then is not compiled into golangci-lint, no?09:32
mborzeckipedronis: it is09:33
pedronisconfused :)09:33
pedronisI pushed anothe daemon refactor PR, this one is very small: https://github.com/snapcore/snapd/pull/1035609:35
mborzeckipedronis: look at the output at the bottom https://paste.ubuntu.com/p/VVQM9TSYkF/ almost ok, the line number seems to be n+1, but emacs highlights it correctly for some reason09:38
mborzeckithat's with gci instead of goimports09:39
mborzeckipedronis: pushed out a change to use gci with a canary in the file that was flagged due to non-gofmt formatting to https://github.com/snapcore/snapd/pull/1008209:52
pedronismborzecki: so in theory after this if we add to ignore the currently non-compliant testpackage files, we should be ok?09:58
mborzeckipedronis: yup, but let's see what the github run shows09:59
pedronisok, almost lunch time here09:59
mborzeckinice, the note was added after github run finished10:18
mardygithub avatars are currently broken, and possibly something else too: https://www.githubstatus.com/10:35
mardytime to switch to gitlab...10:47
mardy...except that it's also affected: https://status.gitlab.com/10:48
mardy:-)10:48
mborzeckimvo: pstolowski: can you take a look at https://github.com/snapcore/snapd/pull/10357 ?10:51
mborzeckiafaict we're not locking the mutex again, once defers run there's an attempt to unlock it again10:52
mborzeckialso a missing test case, i'll try to add one now10:52
mborzeckianyone recall whether there's a common way to inject backend errors in snapstate tests?11:09
pedronismborzecki: it's not used a lot but SetSnapManagerBackend exists11:38
pedronisin export_test.go11:38
mborzeckipedronis: i've pushed a little hack in https://github.com/snapcore/snapd/pull/1035711:41
mborzeckipedronis: suggested a little comment tweak in https://github.com/snapcore/snapd/pull/10345 otherwise it looks good to me12:11
mardyany hints on how to debug a configure hook? I'd like to see its stderr and stdout12:41
mborzeckimvo: can you land https://github.com/snapcore/snapd/pull/10338 ?12:42
mborzeckimardy: hm the output should be collected in task log, `snap change <id>` ?12:42
mvomborzecki: sure12:43
mvomborzecki: done12:43
mborzeckimvo: thanks!12:48
mardymborzecki: nope, that only shows that the hook was executed, but it does not show its output12:58
ogramardy, it usually just goes to the journal ... but only if it exited nonzero ... else you have to use logger inside the hook to get output12:59
mardyogra: ah, I see, thanks!13:25
pstolowskiijohnson: i updated #1029013:50
ijohnsonpstolowski: thanks I'll have another look 13:58
pstolowskiijohnson: i hope my explanations make sense. btw i wouldn't necessarily go with hold/gating renaming right now because it would probably mandate changes in other places too (and this PR is close to land). I can propose a separate PR to unify the naming when the feature is close to completion14:04
ijohnsonpstolowski: yeah that's fine to not rename things in the PR, I just meant it more as a general comment about the concept in general 14:06
ijohnsonpedronis: I'm going to wait for your review before merging #10354 just FYI since there was confusion there before14:10
pedronisijohnson: going to do some reviews now including your PRs, had quite a few meeetings so far14:35
ijohnsonpedronis: no worries thanks for the reviews14:35
ijohnsonpstolowski: thanks for the explanation I think it makes sense now, just one clarifying comment about how gating is organized 14:37
ijohnsonbut the PR has my +1 now14:37
pstolowskiijohnson: thanks!14:42
pedronisijohnson: I did review a couple of PRs, the next one will need the prereq to land and a master merge then I will re-review it14:58
ijohnsonpedronis: thanks looking now14:58
pedronismborzecki: what's the status https://github.com/snapcore/snapd/pull/10241 ? did it ever get the change to apparmor cpu use merged into it?14:59
pedronishttps://github.com/snapcore/snapd/pull/10345 needs 2nd reviews15:01
ijohnsonpedronis: regarding conflicts, I was hoping to first land the task handlers and wire them up to be used, then after that to add the conflict checking code, is that okay?15:04
ijohnsonotherwise 10347 will get big again15:05
pedronisijohnson: yes15:14
ijohnsonok, thanks15:14

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