Log file Viewer

[12:57:24] <travis-ci> pypa/pip#16653 (master - dd5e5c3 : Paul Moore): The build passed.

[12:57:24] <travis-ci> Change view : https://github.com/pypa/pip/compare/549a9d11a1f2...dd5e5c39e20b

[12:57:24] <travis-ci> Build details : https://travis-ci.org/pypa/pip/builds/694231181

[15:09:44] <dalley> cooperlees, techalchemy https://github.com/pypa/bandersnatch/issues/548

[15:10:10] <dalley> I'm not sure that it covers everything but hopefully it's enough to start a discussion

[15:10:18] <techalchemy> dalley, I don't think you wrote enough words

[15:12:03] <dalley> is that sarcasm I detect, lol

[15:25:06] <dalley> are your needs relatively similar?

[15:40:37] <techalchemy> dalley, will tell you in a few when i have a chance to read

[17:43:41] <cooperlees> dalley: Thanks - Will try take a look today and respond to get things moving.

[20:32:16] <travis-ci> pypa/pip#16662 (master - dd3672f : Greg Ward): The build passed.

[20:32:16] <travis-ci> Change view : https://github.com/pypa/pip/compare/df15e6414e8f...dd3672fe3412

[20:32:16] <travis-ci> Build details : https://travis-ci.org/pypa/pip/builds/694401846

[20:49:11] <travis-ci> pypa/pip#16663 (master - ebd331f : Stéphane Bidoul): The build passed.

[20:49:11] <travis-ci> Change view : https://github.com/pypa/pip/compare/dd3672fe3412...ebd331fb45f4

[20:49:12] <travis-ci> Build details : https://travis-ci.org/pypa/pip/builds/694406503

[23:10:52] <travis-ci> pypa/pip#16665 (master - cdeb377 : Pradyun Gedam): The build passed.

[23:10:52] <travis-ci> Change view : https://github.com/pypa/pip/compare/ebd331fb45f4994bc075a799e38252a0b77bd566...cdeb377a3633c9a79e4bd08f5e0026c8be7a7143

[23:10:52] <travis-ci> Build details : https://travis-ci.org/pypa/pip/builds/694448002

[23:15:02] <techalchemy> dalley, finally responded, no idea if i was remotely helpful in my response though

[23:17:15] <dalley> techalchemy, so I had a paragraph explaining why and decided it wasn't super relevant. the tl;dr is that one of our primary features is "lazy sync" which is basically a transparent on_demand cache

[23:17:39] <techalchemy> that'd be super cool to support

[23:18:07] <dalley> you 'mirror' PyPI (or an RPM repo, or a Debian repo, or a Docker registry), all the metadata gets ingested, but none of the packages are actually downloaded until a client requests it

[23:18:18] <techalchemy> yeah, makes perfect sense

[23:18:40] <dalley> and then once it's downloaded it sticks around

[23:18:58] <techalchemy> depending on how you're mirroring there's more configuration to do in the webserver etc potentially

[23:20:00] <techalchemy> for instance if you want to avoid redirects and still act like you have the bits

[23:24:00] <dalley> requirementslib looks like a nice library, I'll look into it

[23:24:56] <techalchemy> it's maybe not ideally suited for what you want

[23:25:59] <techalchemy> i'm currently ingesting all of the package metadata into a db and i think for requirementslib to download it you'd have to measure that time in days

[23:26:22] <techalchemy> aiohttp took hours and i didn't transform it at all or instantiate any objects from it

[23:29:09] <dalley> but yeah, our entire pipeline is set up around controlling the file downloads

[23:34:47] <techalchemy> i guess i could go read the code if i want to understand the flow a bit

[23:39:14] <dalley> I can explain it in a second

[23:50:27] <dalley> sorry, playing video games on the side :P

[23:59:55] <techalchemy> lol no worries i'm definitely checked out for the day i will likely read a bit of the code