- User Since
- Sep 9 2015, 9:17 PM (307 w, 2 d)
Mon, Jul 26
Thanks for looking into this.
What about sending logs to a separate dedicated logging machine instead of storing them locally?
Thu, Jul 22
Wed, Jul 21
I am a bit puzzled by the numbers shown: eeally we have only 200k origins for GitLab.com.?
And we know we had some 1.5m origins for Google code, why only 700k shown here?
Tue, Jul 20
Jun 26 2021
Jun 22 2021
Nice to see this moving forward!
Jun 18 2021
Jun 14 2021
Jun 11 2021
Great, it seems we are getting there :-)
Jun 7 2021
Thanks @ardumont for investigating this. The fact that the IA does not provide the LastModified information may make sense for their specific case (it is possible that they do not have kept the LastModified info from the original location).
May 29 2021
May 28 2021
May 25 2021
That will be helpful in general (to answer questions likes: which endpoint is over/underused for specific use cases) and also in view of seeing who over/underuses rate limits (e.g., to identify the need of having more generous rate limits for specific use cases).
May 20 2021
May 19 2021
May 12 2021
May 11 2021
May 10 2021
A lot has changed since this was opened:
May 8 2021
May 7 2021
@anlambert ; ping me when this is done, so we can answer some pending requests :-)
Apr 29 2021
Apr 28 2021
> I also recall now that vincent added a graph  recently enough.
This to try and compare a bit the counter approaches together.
So that's still using the old plumbing at least for that part.
Apr 27 2021
Apr 26 2021
Apr 24 2021
Apr 21 2021
Thanks @ardumont ... so it appears that adapting the logic is easy... may you do it?
@anlambert may you look into the needed modification of the UI, to enable the new type of save code now payloads for selected authenticated users?
Apr 20 2021
Thanks, this is quite useful indeed.
Thanks for looking into this. If I look at https://grafana.softwareheritage.org/d/WXRVVc_Mz/save-code-now?viewPanel=4&orgId=1&from=1617954242247&to=1617975842247&var-environment=production&var-instance=moma.internal.softwareheritage.org&var-status=All&var-load_task_status=All&var-visit_type=All it seems there are also some 255 requests "not yet scheduled". Maybe it's the same issue?
Apr 19 2021
Thanks, it is indeed an urgent matter, as various journals depend on this!
Well, it seems we have been hit by this again, in a different form:
Apr 16 2021
Thanks to all of you for this dicussion and proposals.
Great. In addition to the content of the free form field, the standard answer should contain proper boilerplate reminding what is expected in a Save Code Now request, along the lines of what is written in the "Help" tab of https://archive.softwareheritage.org/save/
On a related note, it may be useful to regularly report requests that did not complete (either as success or failure) in a reasonable amount of time after being scheduled.
Apr 15 2021
Apr 14 2021
Great news :-)
Apr 13 2021
Ok, this is converging with the discussion in T3234: we fully agree that having proper errors reported to the user is the way to go, so let's forget about the "sanitization" approach.
Ok, so no need to change the specification document for SWHIDs.
I wonder if this is not overkill: SWHID may evolve in the future, and maintaining two implementations (one of them in JS!) may be source of headaches down the line.
A simple "sanitization" phase in the frontend catching the most common issues (trailing slashes, leading or trailing tabs or spaces, etc.) would probably be enough for our purpose.
Apr 10 2021
As a compromise, we could accept this trailing slash, but show a warning on the interface and/or codify in the SWHID specification an exhaustive list of "fixes" that user interfaces can/should do.
There are already many URLs in the open, so even if we remove the trailing slash now, that does not solve the problem.