Comments (12)
What are you trying to achieve here? What is the goal? I ask because this specific solution would be quite an engineering effort as the files are stored in the S3 object store (so accessing each one is not as easy as reading off a disk...) and this file would surely be /enormous/?
from buildinfo.debian.net.
from buildinfo.debian.net.
Perhaps I'm misunderstanding something but there are 11,887,190 .buildinfo
files on buildinfo.debian.net right now. I suspect this will be larger than a gigabyte, even compressed. :)
from buildinfo.debian.net.
from buildinfo.debian.net.
This very much smells like an Xy problem and additionally I think getting this right will require some actual thought into how folks (not just yourself) will want to access these files, rather than "just" adding an endpoint and being done with it.
My gut feeling is that simply adding a 'n buildinfo at once' is not sustainable as 'n' will never be large enough. What, really, are you doing with the data you return? Just checking whether something matches? If so, one doesn't need the entire buildinfo. BUT that's just one possible may example of an access pattern, we should try and work out how to do this at real scale. :)
from buildinfo.debian.net.
from buildinfo.debian.net.
Good morning. Unfortunately I am just about to go offline until at least tomorrow afternoon CET, possibly Sunday. But regardless of that I think we are on different pages about the scope of this particular issue. I believe it requires quite a considerable discussion to understand the potential access patterns to whatever data is stored within buildinfo files and furthermore IMHO these sorts of discussions come to much much better results if they can be done async — in other words, the "latency" you decry (although I have been replying quickly, no?) is actually a feature. Rushing this bit is a bit silly anyway as implementing (any) solution will take some thought and attention too, possibly rebuilding indices on the server, etc. etc. which may take days (no, really!) to run.
(re. #54, this is far more straightforward; whilst this one actually has lots of nuance, including how reproducible-check
/ apt
can sanely use the same pattern.)
from buildinfo.debian.net.
from buildinfo.debian.net.
so can we maybe discuss this on Monday or Tuesday? I suppose 30min will
be plenty and wouldnt be surprised if we'd only need half the time.
30 minutes? I think we have very different ideas about the scope of the problem. :) Even IRL would not be great for me - this thing really requires some "walking" or "shower" time. :p
from buildinfo.debian.net.
from buildinfo.debian.net.
from buildinfo.debian.net.
I've got two usecases, there are probably more and others.
1.) a user wanting to rebuild all the binaries they are using. For that they need to know all the buildinfo files of all installed packages. (a user can be a real user like you and me or also the tails projects who want to verify all the binaries on their images)
2.) a service which wants to verify all binary packages which Debian offers as part of their 'Buster' release or all packages currently in unstable/main/arm64 (as an example).
from buildinfo.debian.net.
Related Issues (20)
- Compress .buildinfo files HOT 1
- Store original .buildinfo files on S3? HOT 1
- report stronger checksums on web interface
- Add support for .buildinfo 1.0 ("Only Format: 0.2 is supported")
- Parses all building files as having a source version 1.0 regardless of actual version HOT 1
- certificate on buildinfo.debian.net expired HOT 1
- Include .buildinfo files from ftp.debian.org HOT 2
- API to fetch specific .buildinfo files for a certain package/arch/builder HOT 11
- ability to search for buildinfo's by hash HOT 5
- please default to showing sha256 hashes HOT 7
- .onion service
- Cache expensive query on homepage
- Move to salsa.debian.org HOT 1
- API endpoint for getting all new buildinfos since a particular timestamp
- check for match against debian archive HOT 5
- Rejecting submission: Could not determine GPG uid HOT 8
- Batch uploads/import HOT 1
- Duplicate submissions are accepted HOT 2
- add a way to query for .buildinfo files from official debian builds only HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from buildinfo.debian.net.