The features page is online and accessible for admins and ambassadors to get feedback:
https://www.softwareheritage.org/features/
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 1 2021
I truly doubt that proceeding like this will optimize the memory consumption of the loader as objects in a pack file are gzip compressed and usually deltified to optimize size.
Your approach will store all git objects uncompressed in a dict so few chances that it will eat less memory than the pack file here, nevertheless it will optimize loading performance.
I truly doubt that proceeding like this will optimize the memory consumption of the loader as objects in a pack file are gzip compressed and usually deltified to optimize size.
I'm assuming it's just to demonstrate we could migrate to django3 right?
Not a "let's migrate to django3"?
Build is green
Adapt according to suggestion
what about naming the parameter create_snapshot instead?
Sep 30 2021
Prior to this
commit, it was implied that the store_data could only be called once. It's a limitation
that needs to change for some ongoing optimizations in the loader git.
what about naming the parameter create_snapshot instead?
cc @seirl
Build is green
Build is green
rebase
rebase
Hmm actually this might be harder than just using gunicorn, because the java subprocess needs to be shared between workers, hmm...
Deployed.
Deployed.
- some negative UTCs don't have the boolean set to true (the only example I have is also missing a space in the same line, so this might be why)
- "0000" as offset (with no sign), dulwich can't even parse this
- "+0575" as offset; parsed as "+0615"
- "\r" in an email address was stripped
Build is green
Realign commit message and diff description
Looks ok (not sure I really understand the fix however, more precisely, what was the purpose of the revision_start != 1 condition), but I really don't understand the commit message:
Looks ok (not sure I really understand the fix however, more precisely, what was the purpose of the revision_start != 1 condition), but I really don't understand the commit message:
Build is green
Drop no longer needs to rewind the packfile prior to read it
Build is green
Rework commit message/diff description
Sep 29 2021
Build is green
Assert snapshot is not null
Build is green
Fix
And it's now deployed.
Closing.
Looks good to me !
Build is green
Fix typo
Wrong variable used in code (see inline comment), I will accept the diff afterwards.
Build is green
Adapt to a better implementation
We should capture all svn errors in order to:
- raise exception based on an error code
- give more details about the failure by appending error messages to fallback exception
Build is green
Update test docstring
- "author xxx<yyy@googlemail.com> <xxx<yyy@googlemail.com>> 1282956323 +0200" parsed as "author xxx<yyy@googlemail.com> <xxx <yy@googlemail.com>> 1282956323 +0200" (yes there is a fullname in the email)
- a few commits with this timezone: "--700", parsed as "+0700"
- Some weird offsets parsed as "+0000": "+1400"/"+051800"/"+1558601"
- looks like old git loaders tried to decode and re-encode name and/or email, which messed it up when not UTF8