[01:34] Is there an ova for snappy? [02:25] How can I stop snapcraft from pulling the source for a package every time I run it [02:29] PR snapd#3651 opened: update golang/x/net to version currently in Debian unstable [02:44] hmmm, found it :) [03:49] Does a snap compile inside of a qemu instance or something? I get a weird error trying to compile samba [03:55] libattr.a(syscalls.o): relocation R_X86_64_PC32 against symbol `syscall@@GLIBC_2.2.5' can not be used when making a shared object; recompile with -fPIC [03:56] Doesnt happen if I dont use snapcraft [04:28] I need some help. I'm trying to package a Python3 app, and I've got the following setup.py...https://bpaste.net/show/ae2837e13a50 [04:28] And this snapcraft.yaml: https://bpaste.net/show/b0a5a817f700 [04:28] Running 'snapcraft', everything seems to go fine, and then I slam into THIS: https://bpaste.net/show/687682e4738c [04:29] What is going on, and how do I get past this? [04:31] PR snapd#3652 opened: update gopkg.in/check.v1 to version currently in Debian unstable [04:33] PR snapd#3653 opened: update gopkg.in/yaml.v2 to version currently in Debian unstable [04:34] PR snapd#3654 opened: update github.com/coreos/go-systemd to version currently in Debian un… [04:36] PR snapd#3655 opened: update github.com/gorilla/mux to version currently in Debian unstable [06:57] good morning [06:58] Hey zyga-ubuntu [06:58] good evening [07:01] Hey! :) [07:02] what a day, after unending heat I was woken up by fierce rain [07:04] Just sprinkling here [07:27] pstolowski: good morning [07:30] Can you list the files in a snap file? [07:34] PhoenixMage: sure, unsquashfs -l foo.snap [07:35] thanks [07:36] * zyga-ubuntu looks after https://github.com/snapcore/snapd/pull/3609/files [07:36] PR snapd#3609: interfaces/builtin: add kvm interface [07:37] zyga-ubuntu: did you see my little pile of dep upgrade PRs? [07:37] mwhudson: yes [07:37] mwhudson: I want to do some diffs before/after though and this is something that requires more focus [07:37] * zyga-ubuntu wasn't sleeping till 2Am [07:37] zyga-ubuntu: fair enough [07:37] mwhudson: I would also like to have Chipaca around for 2nd opinion [07:38] the tests passed "enough" that i'm not expecting problems in this regard for the debian update [07:38] mwhudson: yes, I think it is okay as well [07:38] also this: [07:38] mwhudson@aeglos:~$ go get github.com/ojii/gettext.go [07:38] stat github.com/ojii/gettext.go: no such file or directory [07:38] mwhudson: I'll probably merge the test dependencies [07:39] does that happen for everyone? [07:39] hmm [07:39] mwhudson: yes [07:39] so weird [07:40] why do people name a repository .go? [07:40] i presume it's the trailing .go that screws it up [07:40] yep [07:40] means dh-make-golang won't work on it :( [07:41] just fork it [07:41] do the package [07:41] and sed [07:41] heh [07:41] and watch your fork gain in popularity [07:41] because 1) not insane 2) packaged ^_^ [07:42] not sure those are actual helps when it comes to popularity [07:42] mwhudson: if you cannot "go get" something that does count as an eyebrow-raiser to me [07:42] i'll file an issue for now [07:43] zyga-ubuntu, hey! [07:44] hej hej [07:44] mwhudson: working on arch update I found one thing I think we may need [07:44] https://github.com/snapcore/snapd/pull/3650 [07:44] PR snapd#3650: cmd/snap-confine: don't share /etc/nsswitch from host [07:44] I think all modern distros will have this problem [07:45] ah, forgot apparmor update [07:54] w00t got samba compiled as a snap, now to work out everything I need to do to get it to run [07:54] Thanks to launchpad for making sure it doesnt take a month to do on an actual pi [07:56] PhoenixMage: just build it on x86 first [07:56] then once it all works, cross compile [08:00] Bit of information leakage in a snap file [08:01] It lists my home directory path, etc [08:02] can you clarify? [08:04] the parts directory in the snap has a full path to where it was built, including my home directory [08:05] can you show me your snapcraft file? [08:06] squashfs-root/home/phoenix/samba/parts/samba/build/sbin/smbd [08:06] or the listing of files from the snap [08:06] aha [08:06] then it is built incorretly and will not work [08:06] incorrectly* [08:07] https://pastebin.com/3uVZ7y6Z [08:08] this looks ok [08:08] and the listing of files? [08:08] how did you build the snap in the end? [08:08] just running snapcraft or did you pass any arguments? [08:10] https://pastebin.com/JxDkFBs3 [08:10] This is the local one on my ubuntu instance [08:10] And all I did was run snapcraft with no arguments [08:10] Well after I ran a snapcraft clean [08:15] Anyway, I am out for dinner, will look into it more when I am done [08:16] o/ [08:16] PhoenixMage: looks very wrong but not sure if this is related to snapcraft or the environment you were in [08:16] Chipaca: hey [08:16] 'sup [08:17] Chipaca: reviews! [08:17] zyga-ubuntu: huzzah! [08:17] https://github.com/snapcore/snapd/pull/3650 [08:17] PR snapd#3650: cmd/snap-confine: don't share /etc/nsswitch from host [08:17] more arch-y thingfs [08:18] https://github.com/snapcore/snapd/pull/3648 [08:18] PR snapd#3648: release: remove default from VERSION_ID [08:18] uh [08:18] zyga-ubuntu: why not share nsswitch from host? [08:18] * Chipaca looks [08:19] because it depends on loadable modules core doesn't have [08:19] an host may have [08:19] and in practice: systemd-resolved [08:19] on arch you don't look at resolv.conf when you are using systemd-resolved [08:20] anyway, this makes wethr snap work [08:20] :D) [08:20] btw, I was looking for a snap with bash tab completion [08:20] I thought http had some [08:23] nope [08:23] i'll look into giving it some though [08:24] ooh, they already _have_ completion [08:24] i just need to plug it in [08:43] zyga-ubuntu I pushed some changes in, now all tests pass and also more changes to address rest of the comments [08:43] zyga-ubuntu let me know what you think [08:44] ondra: nice, I didn't get to it yet [08:44] ondra: though I'm churning through interface PRs today [08:44] zyga-ubuntu I just pushed it, panic was my mistake [08:45] zyga-ubuntu just don't know if I got right what you wanted to change about using snaptest.MockInfo, I did change it, as I saw it used in other tests, so curious if it is right :) [08:46] I'm still improving many interfaces [08:47] some use older style of tests [08:47] some use newer already [08:49] don't worry, I'll update it [08:50] * zyga-ubuntu is now happy about https://github.com/snapcore/snapd/pull/3499 and moves to the next PR [08:50] PR snapd#3499: interfaces/builtin: add the spi interface [08:56] * zyga-ubuntu -> break [09:13] zyga-ubuntu: want to try http from candidate/ [09:13] ? [09:14] httpie's completion is far from brilliant, but there you go [09:15] i'll offer them a patch if i ver get around to making this better [09:20] Good mornings! [09:21] niemeyer: o/! [09:23] Chipaca: \o [09:30] niemeyer: hi, should this be closed for now snapd#3526 ; didn't we decide in London to wait a bit before implementing this ? [09:30] PR snapd#3526: hooks: support for refresh hook [09:32] zyga-ubuntu: _now_ you can try it (testing ftw) [09:35] pedronis: Looking [09:35] pedronis, hey, afair we it was clear we don't want revert hook, not sure about refresh though [09:36] pedronis: Yeah, as pstolowski mentions I think it was refresh we were talking about [09:36] Erm [09:37] *revert [09:37] That was the one a bit confusing because we may want to call it on the opposite end [09:38] (call revert before reverting) [09:38] Or both? ... that's why we deferred [09:38] willcooke: Morning [09:39] hi niemeyer [09:41] Chipaca: trying [09:41] hmmm [09:42] openpgp invalid signature [09:42] hash tag doesn't match [09:42] woah [09:42] more weird stuff [09:43] Chipaca: look [09:43] https://paste.gnome.org/pb3e5ztde [09:44] Chipaca: http weirdness on 1.8? [09:44] *golang 1.8 [09:44] zyga-ubuntu: Its zesty server [09:45] zyga-ubuntu: seems for openpgp crypto weirdness with 1.8 [09:45] or whatever the moving part is here [09:45] this is snapd master on arch with vendorized everything and stock golang 1.8.3 [09:46] something looks broken there [09:46] but itnterestingly, it worked on 1st install of all the snaps I have [09:47] *interestingly [09:51] zyga-ubuntu: whaa? [09:51] zyga-ubuntu: context of this? [09:51] zyga-ubuntu: that looks like a pedronis one :-) [09:51] pedronis: “Cannot prepare auto-refresh change: cannot add some assertions to the system database:” [09:52] Chipaca: as I said something seems wrong with the data or the crypto code, a bit hard to judge from afar [09:52] ah i missed your response there [09:52] sorry [09:52] Chipaca: how did you get that error? [09:52] zyga-ubuntu: which error? [09:52] zyga-ubuntu: the one you pointed me to? [09:52] ah, sorry [09:52] right [09:53] :-) [09:53] I thought you reproduced it [09:53] zyga-ubuntu: do asserts unit tests pass ? [09:53] I wonder if it happens on zesty/artful [09:53] pedronis: yes [09:53] pedronis: all of them [09:53] zyga-ubuntu: what were you doing when doing that? [09:53] i mean, context of that error? [09:53] Chipaca: I wanted to install your http snap from candidate [09:53] so not in tests [09:53] in actual real life use [09:54] yes [09:54] but _your_ real life, so most people's zany fantasies :-p [09:54] arch uses gpg 2.1.21 [09:54] hahaha [09:54] nice [09:56] * zyga-ubuntu could not sleep much last night, was chasing and hunting mosquitoes [10:00] did you win at least ? [10:02] ogra: zyga-ubuntu: https://www.youtube.com/watch?v=DQeyjgSUlrk [10:04] yum [10:04] are they waiting for some to feed to make ketchup [10:04] ? [10:06] zyga-ubuntu: no, that's fake news: http://bangaloremirror.indiatimes.com/bangalore/others/fake-news-buster-blood-urine-and-cocaine-used-to-make-ketchup/articleshow/56922945.cms [10:08] I was actually making things up, I didn't hear about this [10:09] zyga-ubuntu: you make things up, the internet delivers [10:11] zyga-ubuntu: we don't use gnupg directly for anything but snap sign (and related commands) [10:13] so it must be a regression/change in the libraries we use [10:13] or golang proper [10:13] not fun :/ [10:13] pedronis: I'll check artful [10:16] PR snapd#3656 opened: store: don't call useDeltas() twice in quick succession [10:20] zyga-ubuntu: well at least autopkgtest pass on artful afaiu [10:22] hmm, good point [10:25] niemeyer: offtopic, if you feel like doing a review: https://github.com/snapcore/snapd/pull/3636 [10:25] PR snapd#3636: snap: add support for parsing snap layout section [10:25] just the syntax, I think nothin controversial, landing this will help with my experiments [10:25] zyga-ubuntu: I feel like doing many reviews.. putting my mail in order first [10:27] zyga-ubuntu, since you just reviewed the spi interface stuff today ... how about ack'ing https://github.com/snapcore/pi3-gadget/pull/12 as well ? :) [10:27] PR pi3-gadget#12: enable spidev by default [10:28] ogra: looking [10:28] (one liner config change) [10:28] ogra: done [10:28] thx [10:29] PR snapcraft#1434 closed: lxd: clean with no parts should only delete [10:34] * ogra sees the kernel ML and hugs ppisati [10:34] wohooo !!! [10:35] ogra: ? :) [10:36] zyga-ubuntu, fixed a hang of the spash screen on rpi when the kms driver is used [10:36] well [10:36] not a hang of the splash ... actually a hard hang of the board if you start the boot splash [10:37] pedronis: what is a SAS? [10:37] https://github.com/snapcore/snapd/pull/3632/files [10:37] PR snapd#3632: asserts,overlord/assertstate: auto refresh account-keys [10:37] ogra: who is the store guy nowadays? [10:37] zyga-ubuntu: snap assertions service [10:38] ah [10:38] thanks [10:38] ppisati, try cprov [10:38] ogra: k [10:38] your snapcraft.yaml looks nice btw ... [10:38] (for the pi kernel) [10:39] ogra: yep, and it builds locally (finally!) [10:39] ppisati, with the new gadget build system you theoretically dont need to tar up the overlays anymore [10:39] ogra: i still have one pet peeve with the snapdragon snapcraft.yaml, but i don't know how to fix it yet... [10:40] ogra: is that aleady in place? [10:40] (teh uboot build now pulls the kernel deb and extracts them from there) [10:40] not for all pi's yet ... still have the 2 and the cm on my todo [10:41] s/the uboot build/the gadget build/ [10:42] ppisati: hey, how can I help ? [10:43] cprov: i'm about to send an email, hold on [10:43] ok [10:53] PR snapd#3609 closed: interfaces/builtin: add kvm interface [10:58] ogra: do share! [10:58] wrt kernel ml [10:59] ah, kept reading and saw the rpi comment [11:02] PR snapd#3652 closed: update gopkg.in/check.v1 to version currently in Debian unstable [11:02] PR snapd#3653 closed: update gopkg.in/yaml.v2 to version currently in Debian unstable [11:03] PR snapd#3655 closed: update github.com/gorilla/mux to version currently in Debian unstable [11:12] Chipaca: interesting https://forum.snapcraft.io/t/snap-store-download-slow/1463 [11:18] sergiusens, i'm working on including https://github.com/ogra1/psplash-snap/ in the gadget by default and load it into the initrd on boot (which is a breeze with the split initrd stuff :) ) ... that hang was the blocker for me :) [11:29] zyga-ubuntu: yes, looking into that now [11:37] * zyga-ubuntu feels so so and takes a break [11:37] not enough sleep, too much coffee [11:37] ondra: I'm 50% through your PR, making some small test changes [11:42] zyga-arch: _right now_, i'm seeing up to ~80MB/s in linode, better than what i get from google's chrome archive [11:43] zyga-arch thanks :) [11:44] zyga-arch: actually no, gogole's archive is better [11:45] * Chipaca updated [11:45] anyway, luncheon [12:08] heya, can I somehow bypass the publisher constraint on content snap (i.e. I have a content snap from the store and want to connect it to a locally built snap) [12:20] sitter: we don't check the constraint if the snap is locally installed and unsasserted afair [12:21] it doesn't autoconnect either though I think [12:27] PR snapd#3656 closed: store: don't call useDeltas() twice in quick succession [12:27] zyga-arch: snapd#3654 is green if you want to take a look at that one (you +1'ed the others) [12:27] PR snapd#3654: update github.com/coreos/go-systemd to version currently in Debian unstable [12:28] PR snapd#3651 closed: update golang/x/net to version currently in Debian unstable [12:28] heh [12:28] zyga-arch: never mind :-D [12:28] Chipaca: things were green [12:29] PR snapd#3654 closed: update github.com/coreos/go-systemd to version currently in Debian unstable [12:29] pedronis: yep! they weren't at start-of-day [12:29] but i reran and they passed [12:29] now just crypto which maybe it's just a matter of splitting, if mwh doesn't get to look into that, I might, but many things on my plate === tinwood is now known as tinwood-afk [12:30] Chipaca: I added some comments to your PRs [12:30] * Chipaca looks === cachio is now known as cachio_afk [13:16] Bug #1661265 changed: [regression] sched_setscheduler denied with Qt/QML applications mvo> [13:19] Bug #1533265 changed: /dev/vchiq is inaccessible for unprivileged user [13:22] Bug #1600154 changed: Reading gsettings key don't work locally (writing does) [13:25] Bug #1604967 changed: Apparmor denies bind to abstract unix sockets such as @/var/lib/juju/mutex-/store-lock [13:28] Bug #1658298 changed: The (administratively maintained) mapping file /etc/iproute2/rt_tables is not writeable. [13:37] * zyga-ubuntu goes out of the part to work from a choffe shop [13:37] Bug #1603879 changed: Requesting additions to optical-drive interface for cdparanoia. [13:40] Bug #1602233 changed: "X11 connection rejected because of wrong authentication." when using snaps over ssh [13:40] Bug #1607763 changed: Interface to manage sudoers === tinwood-afk is now known as tinwood [13:43] Bug #1609499 changed: move interface-specific OS mounts to interface.SecurityMounts [13:43] Bug #1610211 changed: Interface to manage block devices [13:45] ogra: woah, we have first class split initrd support now? [13:45] sergiusens, not officiaylly yet, but soon :) [13:45] ogra: can we fix our kernel plugin to not "compose" an initrd? [13:45] tyhicks: jdstrand any idea why I get this: "[259955.380790] audit: type=1400 audit(1501720353.476:196): apparmor="DENIED" operation="capable" profile="/snap/core/2462/usr/lib/snapd/snap-confine" pid=7348 comm="snap-confine" capability=4 capname="fsetid"" [13:46] sergiusens, well, we will neeed it to create a modules.img then ... thats still on the TODO [13:46] Bug #1616833 changed: need new interface: time-hardware [13:46] Bug #1626359 changed: Cannot authorise quotactl syscall for Q_GETQUOTA Released> [13:46] Bug #1658793 changed: App needs resolvconf data access [13:47] i only focused on the gadget side for now ... but with the new setup you can theoretically assemble an initrd from unlimited amounts of img files (as long as the compression and cpio options were identical when creating them) [13:47] sergiusens, we'll still need to build the modules.img and snapd needs to learn to put the initrd from core into system-boot [13:48] so still a lot to do, but the basic concept works nicely [13:49] Bug #1664297 changed: Snapped indicators using custom themes or actions doesn't properly work [13:49] Bug #1664484 changed: Missing interface to record audio from pulseaudio [13:49] * ogra notes jdstrand has "paperwork cleanup day" today ... [13:50] zyga-arch: any idea about my snap-confine above? ^ [13:58] Bug #1577472 changed: The remapped $HOME directory shows as read-only to applications running in a snap [13:58] Bug #1607067 changed: Add a dotfiles / hidden files interface === cachio_afk is now known as cachio [13:59] zyga-arch, I try to install zeronet-js and I get this errror [13:59] https://paste.ubuntu.com/25233361/ [13:59] this is an snap in the store [13:59] one of the most popular ones [14:01] Bug #1630690 changed: A snap with git fails because it can't access /etc/mailname [14:02] Chipaca, I saw the log you sent me yesterday [14:02] ok [14:02] but no errors on there [14:03] cachio: i restarted the run as you didn't reply, so it's gone [14:03] Chipaca, ah, ok [14:03] cachio: howerver, 1sec [14:03] tx [14:03] cachio: today i got a different one; 2017-08-03 05:29:49 Failed project prepare: 1 [14:03] - linode:ubuntu-core-16-64:project [14:03] cachio: and this time i downloaded the log before restarting [14:04] cachio: want to see it? [14:04] yes [14:04] cachio: I'll tweet it to you, one line at a time [14:04] * Chipaca is super productive [14:04] Bug #1663175 changed: chroot interface needed [14:05] cachio: http://people.canonical.com/~john/failure_2017080301.txt [14:07] Chipaca, E: Package 'autoconf' has no installation candidate [14:08] i'll see if other branches are failig because of that too [14:09] cachio: it didn't fail again, fwiw [14:10] Chipaca, do you remember which error you saw in fedora? [14:10] cachio: no [14:11] Chipaca, did you see this error trying to install zeronet-js? https://paste.ubuntu.com/25233361/ [14:12] cachio: I looked, didn't understand whether it was important or not, pointed you at it, and moved on [14:12] cachio: I didn't retain anything about it, sorry [14:12] cachio: but I then remembered i should've downloaded the logs, which is why i did it with today's failure (which i didn't even look at beyond seeing that it was in prepare) [14:13] Chipaca: approved the branches [14:13] * pedronis break [14:13] pedronis: woo, thanks [14:13] * Chipaca break as well [14:13] Bug #1683364 changed: Cannot get properties of an Udisks2.Filesystem object [14:16] Bug #1684893 changed: "fonts", "themes" and "icons" interfaces for desktop apps [14:19] sergiusens: re fsetid> yes, https://github.com/snapcore/snapd/pull/3634 [14:19] PR snapd#3634: interfaces/many, cmd/snap-confine: miscellaneous policy updates [14:20] jdstrand: thanks, where does that profile end up in so that I can add this in [14:21] sergiusens: it is snap-confine's profile [14:21] sergiusens: in /etc/apparmor.d/ [14:30] jdstrand: how do I reload? [14:54] Chipaca, https://paste.ubuntu.com/25233684/ [14:54] something must be broken; the autopkgtests are only taking about an hour to run [14:55] cachio: ooh! pedronis ^ [14:55] Chipaca, any idea why it is happening (look at the paste) [14:55] cachio: not me, but pedronis and zyga were looking at something like that earlier [14:55] Chipaca: no [14:56] no? [14:56] different thing [14:56] this is not a signing problem [14:56] ah, not it says that too [14:56] mmmh [14:56] what system is this? [14:57] 16.04 [14:57] pedronis, also failing in 14.04 [14:57] it works here [14:57] fwiw [14:58] 16.04 [14:59] pedronis, I ran it in linode and in my machine and got the same error [14:59] I believe you [14:59] but it's not completely broken [14:59] :) [14:59] so I wonder what is going on [15:00] can you run it with SNAP_HTTP_DEBUG logging only [15:00] s/only/on [15:00] Chipaca can tell you more [15:03] cachio: SNAPD_DEBUG=1 SNAPD_DEBUG_HTTP=7 in /etc/environment, restart everything (including your shell) [15:03] cachio: "everything" == "snapd" fwiw :-) [15:03] ok [15:03] * Chipaca has a small everything [15:07] pedronis, https://paste.ubuntu.com/25233775/ [15:08] cachio: and journalctl -u snapd ? [15:09] https://paste.ubuntu.com/25233789/ [15:09] Chipaca, pedronis [15:11] cachio: that's truncated horizontally [15:11] cachio: how did you get it to be like this? [15:12] (asking because somebody else recently pastebinned a log with the same error, so i want to know what to say to get it right the first time) [15:13] Chipaca, https://paste.ubuntu.com/25233809/ [15:13] sorry, I didn't realize that [15:14] Chipaca, I need to leave for 30 minutes, I'll be back soon [15:14] Chipaca, do you need for info ? [15:14] pedronis: go [15:14] um [15:14] cachio: go [15:15] tx [15:15] so now is a spot the difference game (or if there's no difference wonder what is the other variable) === cachio is now known as cachio_afk [15:15] pedronis: do you have logs from when it worked also [15:15] no, but I can make some [15:15] pedronis: that log includes the full assertion, so spot-the-diff should be easy :-) [15:16] it's split between two lines, because ¯\_(ツ)_/¯ but still easy [15:16] pedronis: i'll get the assertion out of the logs while you do that [15:18] one sec, doing a bit too many things at the same time [15:18] k [15:18] http://pastebin.ubuntu.com/25233836/ is the assert from cachio's logs [15:19] there should be many? [15:20] d'oh. Give me a bit :-) [15:25] Chipaca: https://pastebin.canonical.com/195119/ [15:31] sergiusens: sudo apparmor_parser -r /path/to/profile [15:33] sergiusens: do keep in mind the denial is harmless and all the PR does is silence it [15:34] jdstrand: ok, maybe I am mislead [15:34] there is a denial for sure but it doesn't affect anything and leads to confusion (which is why the PR silences it) [15:36] jdstrand: in a container I get everything working just fine, on digital ocean, unless I cd $SNAP I get a 148 exit [15:38] sergiusens: you can try adding 'capability fsetid,' instead of a deny rule and see if it fixes it, but I suspect that it is something else [15:41] pedronis: http://paste.ubuntu.com/25233928/ from cachio's logs [15:44] pedronis: this from yours: http://paste.ubuntu.com/25233937/ [15:44] Chipaca: this is what "snap dowload": gives me https://pastebin.canonical.com/195120/ [15:45] pedronis: one thing missing from cachio's are the odd numbers [15:45] dunno what they are :-) [15:45] like the 994 [15:45] no clue [15:45] not those aren't part of assertions [15:45] or needed [15:45] it might be a bug in my script :-) [15:46] pedronis: nope, they're there [15:46] not a bug in my script i mean [15:46] pedronis: “X-Vcs-Revision: 137\r\n\r\n994\r\ntype: account-key\nauthority-id” [15:46] that 994 [15:47] I have no clue [15:47] ok [15:47] don't think they belog [15:47] belong [15:47] I mean, there's nothing like that in my other paste [15:48] nor is it expected [15:48] might be a weird bug in api though [15:48] not sure why I'm not breaking then though [15:50] Chipaca: ah, but I'm still using assertions and caio is using api [15:50] wondering if api is flaky and we didn't notice so far [15:53] but flaky would mean something would be different/truncated [15:53] I don't if it's the case [15:54] ooooooohhhhh [15:54] there's a buuu uuu uuuhg [15:54] buuuuhhhhhhhhhhh*cough* [15:55] where? [15:55] in 2.27 or your script? [15:55] or logging? [15:55] 1 secv [15:57] pedronis: http://pastebin.ubuntu.com/25233999/ [15:57] pedronis: but not every time === cachio_afk is now known as cachio [15:58] Chipaca: api has an encoding bug? [15:59] pedronis: would that make an assertion not load? [15:59] a flaky one though? [15:59] of course [15:59] we take the hash of the stuff [15:59] so there's some double encoding or something going on [15:59] pedronis: i assumed so , but checked [15:59] pedronis: yes, something somewhere is double-encoding [15:59] pedronis: can you reproduce this? [16:00] i tried a second time but being a little smarter and failed, let me try with the dumb way again just in case [16:00] Chipaca: so assertions gives back correct utf8 , right? [16:00] afaict [16:01] yes [16:01] and api is now consistently returning double-encoded utf8 to me [16:01] yep [16:02] mmh, not here [16:02] pedronis: fun for all the family [16:02] one sec [16:02] let me do it with curl, in case it's GET doing something wrong [16:03] curl gives me same output (with bad enc) [16:03] Chipaca: yes, sorry, spotted it [16:05] Chipaca: 2.26 was still talking to assertions, 2.27 starts talking to api it seems [16:05] export u=assertions/account/7xN2sMCILuFk10e6DxrTrQWprdmV0Vi9?max-format=0 h='Accept: application/x.ubuntu.assertion'; diff <(curl -sH "$h" https://api.snapcraft.io/api/v1/snaps/$u) <(curl -sH "$h" https://assertions.ubuntu.com/v1/$u) [16:06] ^ just so it's super clear it's the same thing it's getting [16:06] Chipaca: thanks for digging [16:06] pedronis: I don't envy the person having to figure out where it's doing this :-/ [16:07] my hands are firmly by their sides there's no way to interpret this as volunteering [16:07] well we added a layer of proxying [16:07] now [16:07] that seems the obvious candidate [16:08] it's probably even python3 likely, which makes me sad, because is supposed to avoid exactly that [16:08] pedronis: sorta-kinda-maybe. the three-types-of-text in the http stack in python3 flies against the intention i think [16:09] I know [16:09] PR snapd#3630 closed: many: implement "snap logs" [16:10] PR snapd#3640 closed: store: do not resume a download when we already have the whole thing [16:11] Chipaca: I pinged the relevant people, I can dig myself if they don't have time [16:18] PR snapcraft#1433 closed: core: cache FileBase entries when a checksum is provided [16:26] pedronis, Chipaca do you need anything else from me? [16:26] can I help you with something? [16:28] cachio: send criollitos [16:29] Chipaca, hehhe [16:30] cachio: we've determined it's probably because there is a bug in the server [16:31] Chipaca, snapd server? [16:32] cachio: assertions [16:32] good [16:38] Chipaca: not assertions, snap device gateway [16:38] the new kid [16:38] durn new kid [16:53] Chipaca: I created also a bug: https://bugs.launchpad.net/snapstore/+bug/1708490 [16:53] Bug #1708490: there is some kind of encoding/double encoding bug in the proxying of assertions by snapdevicegw [16:57] * pedronis eods [17:10] pedronis: ok [17:11] niemeyer: you got a sec? [17:12] Chipaca: Heya [17:12] Chipaca: Yeah, still fighting my email.. 100+ now [17:12] niemeyer: hi [17:12] niemeyer: good man [17:12] Wassup? [17:12] niemeyer: I'm trying to get the last bit of services out, and was wondering about how you saw the rest api working for this [17:13] Chipaca: Ok [17:13] niemeyer: should there be individual endpoints for each operation? [17:13] Chipaca: Which ops? [17:13] niemeyer: or should there be an "op" struct that client and server both know about? [17:13] start, stop, restart [17:14] Chipaca: I think we need a single operation, otherwise we get into that issue of lack of atomicity [17:15] ok. This means there'll be a, say, client.ServiceOperation that's public but marked as "not for clients" [17:15] that ok with you? [17:16] this would be separate from, say, client.StopOptions (but it'd embed them all i guess) [17:16] Hmm [17:16] How would that look? What do we need to pass in? [17:17] Chipaca: The public but not for clients is strange [17:17] niemeyer: each op has a different option [17:17] Chipaca: There's a sane expectation that anything public in client is supposed to be for clients [17:17] and the server doesn't know the op until it's read the request [17:17] Chipaca: Do you have some examples? [17:18] niemeyer: sure. StopOptions{Disable: false} vs StartOptions{Enable: false} vs RestartOptions{Reload: false} [17:19] Hmm [17:19] so the service operation would be e.g. ServiceOperation{Names: ["foo"], Operation: "frobble", PertinentOptions: false} [17:20] Chipaca: snap operation itself is a bit like that, no? [17:20] not all the bits always apply [17:20] pedronis: yes [17:21] pedronis: but to make it more magic and mysterious snap ops are not shared between client and daemon, and half of the time go via a post form so they don't exist as a struct anywhere [17:22] but as that's a little bit insane i'd rather not go that way :-) [17:22] That sounds okays.. the two ends really have different goals.. [17:22] okayish [17:22] well they are organic grown as much as anything [17:22] One end evolves and needs to support compatibility with crazy old code.. [17:22] The other end is supposed to be a sane abstraction for writing a client with [17:23] Doesn't mean we should design the server to be terrible, though :) [17:24] I _could_ drop ServiceOperation in internal/client/apps.go [17:24] or sth like that? [17:25] I honestly don't think it's worth the trouble for a type with two or three fields [17:25] they all start with two or three fields [17:25] look at daemon/api.go's snapInstruction [17:26] (which is the snap op on the daemon side) [17:26] eh, if the answer isn't immediately obvious, i think i'd rather go forward with dupe'ing them and resolving this later [17:27] don't want to block any more (and hoping to wrap this up before my eod) [17:27] Yeah, I was just looking at SnapOptions in snap_op.go.. I find it quite nice [17:29] niemeyer: you'll notice that that one is missing things like Snaps [17:29] ie it's not the one used for multi [17:29] look for actionData [17:29] Chipaca: snapInstructions comes still from 15.04 I think, it was just evolved, there's even a couple of fields kept there because we thought we would get back to support them quickly *cough* [17:31] Chipaca: That's because we specifically blacklisted the use of options with multiple snaps.. [17:31] return "", fmt.Errorf("cannot use options for multi-action") // (yet) [17:31] This is actually a bug/missing feature [17:31] Makes sense to have "snap install foo bar" [17:31] as I say, I'll go ahead with having duplicated structs [17:32] Chipaca: So how would the API look like? [17:32] niemeyer: which api [17:32] Chipaca: For these actions [17:32] niemeyer: REST, or client? [17:32] Chipaca: REST [17:32] "REST" [17:33] niemeyer: you POST a JSON document to /v2/apps [17:33] (how we ended up calling HTTP as REST tells a lot about how we do things in general) [17:33] niemeyer: with e.g. {"action": "start", "names": ["foo"], "enable": true} [17:34] Chipaca: Sounds good [17:34] Chipaca: We may want mixed mode at some point, but that's less obvious and can wait [17:34] niemeyer: "mixed mode"? [17:35] start+stop [17:35] /o\ [17:35] easy enough to add later [17:36] Chipaca: Yeah [17:54] Chipaca, I am runnig a new install snap tests with release/2.27 and I am reproducing this error with many snaps [17:58] cachio: yes [17:58] cachio: any snap with a non-ascii character [17:59] Chipaca, opps [17:59] cachio: yes [17:59] cachio: (in any assertion in the snap's chain) [17:59] anyway, got service ops working, now need to stop for dinner and such [17:59] EOD, mostly [17:59] yes [18:16] cachio: it's getting fixed in the server [18:17] cachio: it affects 2.27/master but not 2.26 (because 2.26 was not talking to the proxy involved here) [18:20] pedronis, ah, ok [18:20] pedronis, I am testing 2.27 beta validation :) [18:35] hi pmcgowan [18:40] hi, I'm getting this INFO message after installing my first snap: [18:40] 2017-08-03T18:39:15Z INFO cannot auto connect core:core-support-plug to core:core-support: (slot auto-connection), existing connection state "core:core-support-plug core:core-support" in the way [18:40] full paste: http://pastebin.ubuntu.com/25234781/ [18:40] anything to worry about? Is that known noise? [18:40] cachio: yep, fix in progress, wasn't actually too hard [18:42] cjwatson, awesome [18:42] thanks [18:47] ahasenack: known noise I think [18:53] niemeyer, there? [18:53] cachio: Still here [18:54] niemeyer, nice, [18:54] niemeyer, I have created a new test which installs popular snaps [18:54] niemeyer, Jammie talked to you about this? [18:54] cachio: Nope [18:55] niemeyer, ok, he asked to me to consider a test which installed most popular snaps [18:56] I implemented this and found the issue in the assertions because of that [18:56] my question is where to put it? [18:56] I already added it to the main suite but not sure if it is the correct place for that [18:57] I think this test comes from the last sprint in Polland [18:58] cachio: That feels a bit like crossing a line.. we don't want to make snapd depend on every single snap out there [18:58] it seems the thing that we should run nightly [18:58] cachio: Sorry, that's a bit extreme.. [18:58] but not part of the suite for earch commit [18:58] cachio: We don't want to make snapd depend on a random set of snaps [18:58] we don't really know what is their quality [18:58] over time [18:58] cachio: Even if they are popular, they have their own schedule, and their own terms [18:59] cachio: Our tests are supposed to ensure that the *features* they need are properly covered [18:59] niemeyer, agree with that [18:59] cachio: Please feel free to open a forum topic and I'll reply there as well with the rationale [18:59] niemeyer, sure [19:00] cachio: We already depend on way too many external factors in our suite, as you know better than I do :) [19:02] hey kyleN [19:02] niemeyer, ok, lets discuss it in the forum [20:21] Bug #1708527 opened: Add /proc/partitions to system-observe [22:42] cachio: the assertions thing should all be better for you now [22:59] cjwatson, perfect [22:59] cjwatson, is it already merge in master? [22:59] or a PR? [22:59] or a PR? === nacc_ is now known as nacc [23:10] cachio: it's on the production store [23:10] cachio: no change in snapd required [23:10] cjwatson, great! [23:33] What is a correctly formatted snap structure supposed to look like? [23:34] ie, what dirs are supposed to be in the root [23:36] I have found this https://snapcraft.io/docs/snaps/structure but thats not what mine looks like