Build is green
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 22 2021
make parallelism level configurable
Build is green
Yeah I'm not a huge fan either, that's why I started with the async approach; but that's a lot of trouble so I'd rather do this.
rebase
Thanks a lot!
If i'm not mistaken, there has been some more work about this.
This got deployed with the v0.10 package btw.
Making an async swh-storage (or RPC client for our framework, in general) turns out the not be worth it, threads are just as efficient and don't require complex hacks
Looks like we're almost done.
Nov 21 2021
In D6396#173266, @vlorentz wrote:We also tweaked the values of various fields to be consistent across loaders (especially the message), see: https://docs.softwareheritage.org/devel/swh-loader-core/package-loader-specifications.html#release-fields
Hi @vlorentz, I've fixed the code for the new release object and for the loader fields. I also updated the loaders spec documentation. Good for me.
Build is green
- maven-loader: fixes after ardumont's review in D6396
- maven-loader: fix release instead of revision
Nov 20 2021
Build is green
- maven jar-loader: Initalise files.
- maven-loader: fixes after ardumont's review in D6396
- maven-loader: Fix copyright in header
- maven-loader: Fix extId to include url and timestamp
- maven-loader: fix release instead of revision
In D6396#173266, @vlorentz wrote:In D6396#173260, @borisbaldassari wrote:Arg, changes on the master now break the build, throwing "NotImplementedError: build_release".
What happened to build_release, any idea?I replaced "build_revision" with "build_release" in the core loader. You need to rename your "build_revision" function, and change the object it returns.
We also tweaked the values of various fields to be consistent across loaders (especially the message), see: https://docs.softwareheritage.org/devel/swh-loader-core/package-loader-specifications.html#release-fields
oops, wrong link, that's the old fields. See https://forge.softwareheritage.org/D6629#change-PjtKhodzSu0H for the list of changes
In D6396#173260, @borisbaldassari wrote:Arg, changes on the master now break the build, throwing "NotImplementedError: build_release".
What happened to build_release, any idea?
Arg, changes on the master now break the build, throwing "NotImplementedError: build_release".
What happened to build_release, any idea?
In D6395#173250, @ardumont wrote:I'd say if we are confident enough it does the right thing and it's well covered (I
think it is right now) you should be able to rebase all your diffs on latest master. And
then "land" [1] them!
Fine. I'll wait for your review and land the diff when you tell me to then.
Build has FAILED
- maven-loader: Fix extId to include url and timestamp
Nov 19 2021
I will let you know when the full chain is executed.
Well, if works well enough to fill up my vm's hard drive. I'm not sure how to check
the actual loaded content, but it took Gigabytes silently running behind my back.
remove useless response code update
Listing and submission view with a standard user (or anonymous):
Nice catch.
And now giverny seems to refuse to boot back. Stopping a bit that part as I cannot check further yet.
Nov 18 2021
Build is green
Update: Skip redundant post_load check when revisions are identified as identical in prepare
Awesome!
- journalbeat and filebeat are migrated on all the nodes
- after the lag recovery and the fix of the closed indexes script, everything looks good