IRC channel logs
2021-10-14.log
back to list of logs
<zimoun>rekado: guix environment --ad-hoc peek then peek returns (peek:2737): GLib-GIO-ERROR **: 10:15:53.886: Settings schema 'org.gnome.desktop.interface' is not installed on foreign distro <zimoun>rekado: what could be other formats where the constraints are: light, work on any plateform with a few knowledge on what is installed, and self-contained (I do not know if the machine will have access to network for instance) <zimoun>It is for showing prepared demos for a tuto running in conf <zimoun>byzanz is nice except the duration fixed apriori <civodul>you often have to do the same thing several times <zimoun>rekado: when peek works, it is nice. Thank you for the tip. :-) <civodul>there's a surprise there for you workflow people! <civodul>i'm not entirely sure what their motivation was, but i guess it's a good idea to explore the design space <zimoun>Me neither. :-) I have not watched or read all. I miss how the binaries are controlled. Anyway. :-) <zimoun>civodul: how does http-request used by guix/shw.scm represent #:headers? I would like to pass "Authorization: Bearer eyJh…" but « #:headers (('authorization . "Bearer eyJh…")) » fails. <rekado>e.g. like this `(authorization . (,algorithm (Credential . ,foo) (SignedHeaders . ,signed-headers) (Signature . ,signature))) <rekado>I cons that onto the existing headers for the AWS authorization header. <rekado>what I often do is to use netcat to listen on a local port and then use http-request against that local server <rekado>I’m embarrassed to admit how much time I lost due to the format of header lists… <zimoun>yeah, I agree. Hopefully, you saved me some time with your example. :-) <zimoun>then I have tried the buggy example (parse-header 'authorization "Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==" <zimoun>buggy because missing closing parens :-) <rekado>does the generated HTTP request look correct, though? <rekado>in my tests I eventually had to override the authorization header definition in the web server, because of an API quirk on the side of AWS <rekado>(they don’t like the way a value was quoted) <rekado>re ccwl: I think the GWL should also have ‘pipe’ and ‘tee’, and perhaps other combinators to hook up processes. <zimoun>I do not understand how the web module works. The server answers code: 403 reason-phrase: "Forbidden" so something should be wrong with the header. Because it perfectly works using “curl -H”. I give up for this evening <zimoun>because sometimes writing temporary files then reading them right after could avoided. <rekado>zimoun: I really recommend comparing the actual text of the generated request by sending them to http://localhost:1234 and having “nc -l localhost 1234” in another terminal. <rekado>the request that appears in your nc terminal should look the same as what “curl -H” prints <zimoun>rekado, thanks. Indeed. Found why. I will post the solution :-) <zimoun>however, nc -l does not print something <zimoun>civodul: Authentication and SWH made a step this evening. :-) Thanks to rekado! *civodul looks at the backlog <civodul>zimoun: so you're looking at authentication because you have a magic SWH token without rate limiting? :-) <zimoun>civodul: for now, I have a token with 1200 instead of 120 <zimoun>I am asking to them if I could have more :-) <civodul>the missing SWH directories are worrisome <civodul>i guess we'll need their help to understand why some things are missing <zimoun>yep, as you said, we are making progress. :-) <zimoun>now, I want a “special“ token ;-) <civodul>yeah it's nice that we can already get a slightly better view of the archival status