- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 8 2023
Oct 19 2022
Jan 28 2021
It's ok now.
Yes, I completely forgot about your diff that fixed it.
My guess is that swh-scheduler 0.9.2 is not installed on staging, issue has been fixed in rDSCH2906b4e8a08517f5e3d86272232ad8ba926a43d7.
Oct 26 2020
And now it's here
We don't have database backups going back 10 months (nor 8 months, which was the horizon we would have needed at the time the task was submitted).
Aug 31 2020
Aug 28 2020
and what happened to the visits?
and what happened to the visits?
This comment seems to back up my hypothesis on what happened [1]
I don't find data to back me up right now but i would think something like that happened:
...
I don't find data to back me up right now but i would think something like that happened:
Looks like a previous version of the cran loader which did not yet unify the origins, most likely.
Nice! Thanks. One confusing point down, cool.
softwareheritage-scheduler=> select task, type, arguments from task where type='load-cran' and arguments->'kwargs'->>'url' like '%mljar%';
task | type | arguments
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-----------+------------------------------------------------------------------------------------------------------------------
(251148056,load-cran,"{""args"": [], ""kwargs"": {""url"": ""https://cran.r-project.org/src/contrib/mljar_0.1.1.tar.gz"", ""version"": ""0.1.1""}}","2020-01-09 12:45:08.56447+00","1 day",disabled,oneshot,3,) | load-cran | {"args": [], "kwargs": {"url": "https://cran.r-project.org/src/contrib/mljar_0.1.1.tar.gz", "version": "0.1.1"}}Hmmmm... so it could mean that earlier versions of the CRAN lister/loader didn't create origins?
Hmmmm... so it could mean that earlier versions of the CRAN lister/loader didn't create origins?
I don't think it matters but still. I checked all the packages listed (up to bclust) and they are no longer listed over the html listing page reached from the r-project site [1].
So far, i'm confused by this.
Aug 27 2020
Aug 26 2020
Aug 24 2020
tbh, I only used one data point to claim it "always" sets it to None (0000d4ef5e166122aee6862ad38a18ce5386cc3e, which is the first CRAN commit in id order)
(tag removed by mistake, adding it back)
the CRAN loader always sets revision dates to None.
Jan 22 2020
Jan 21 2020
This should take care of [1]
Deployed.
Jan 17 2020
Jan 16 2020
Dumps [1] stored on belvedere on file format:
In the [2] page, there is an archive link (or something) which lists the old associated artifacts (so apriori, no more need for the mran mirror).
In T2029#40500, @ardumont wrote:
Heads up.
Jan 9 2020
Deployed.
Jan 6 2020
Build is green
See https://jenkins.softwareheritage.org/job/DLDBASE/job/tox/302/ for more details.
Rebase to master
Build is green
See https://jenkins.softwareheritage.org/job/DLDBASE/job/tox/301/ for more details.
Rebase to latest origin/master
Build has FAILED
Build has FAILED
Build has FAILED
- cran.loader: Simplify filename computation
did only a quick review, lgtm. Note however my comment on using path.basename() instead of path.split()[-1]
Dec 20 2019
Build is green
See https://jenkins.softwareheritage.org/job/DLDBASE/job/tox/291/ for more details.
- Resolve revision from already seen artifacts
- Improve loading tests