In T4549#91850, @vlorentz wrote:

Hmm, strangely, file/dir names are missing from the response even when omitting the mask when querying the graph server on granet; but based on the .proto file, they should be available via the successor field of Node.

Here is a dump of my design notes on this task.

Polished up and shared the tool built to produce the refined list priority.list.github.
It is now available at https://github.com/rdicosmo/swh-check-repositories

@ardumont here is the subset of the repositories on GitHub, ordered by number of stars, that are:

• still on GitHub
• not a fork

In T4400#88794, @ardumont wrote:

I took the opportunity to retrieve large origins [7] out of the sentry issue listing [6] (cf. description) [8].
And schedule those in the large queues after the one scheduled out of the scanoss exchange.

If it's considered useless at some point, feel free to dismiss them (by purging the queue).

[7] 28310 unique origins ->

loader-git.pack-file-too-big-issue-5823.urls.txt.gz288 KBDownload

[8] command used to create the listing out of sentry, in a venv (snippets repository) in worker1.staging:

(sentry-U52ipwI-) ardumont@worker1:~/snippets/ardumont/sentry% python -m list-urls-from-issue --project-name swh-loader-git --event-id 5823 | tee loader-git.pack-file-too-big-issue-5823.urls.txt
...

As of version 0.5.1, the updateswh extension is now stable, and released, with development on https://github.com/rdicosmo/updateswh, and landing page on https://www.softwareheritage.org/browser-extensions/

Ongoing on https://github.com/rdicosmo/updateswh, landing page is on https://www.softwareheritage.org/browser-extensions/

Nice catch.... actually, the GitLab API uses the project slug (e.g.: checkscale-gitlab/git-wtf) without the .git, we should make sure we can handle this same slug

Is this fixed now, or is the issue still open?

In T3230#83166, @VickyMerzOwn wrote:

Hey, I would like to work on this issue.

Sometimes these variants site side by side with the plain text ones

I didn't understand what site here means.

Thanks! LGTM :-)

Dec 31st is now past, so I asked Marla to remove the "until Dec 31st" from the image,
and we can leave the banner up for a month more.

In T3134#75077, @anlambert wrote:

SWHID v2 should also prevent the hash collision issues we are currently facing (some related to the SHAttered attack on SHA1), see T3775 and SWH-LOADER-GIT-JT.

Updated task name and description to reflect the findings from @anlambert

Thanks a lot @anlambert for looking into this.
It is possible that more key cryptographic software will include these files.
We need a strategy to handle this situation, may you add this example to the SWHID v2 task?

+1, and ok to put the Events entry in the News menu

A task to add to this hackaton:

• add to https://github.com/citation-file-format/ruby-cff/tree/main/test/files/formatted a few examples of Bib(La)TeX entries for software and their corresponding .cff
  • this will ensure that the cff-latex exporter produces proper biblatex-software entries, and uses all the available fields in biblatex-software
  • since .cff is not able to handle BibTeX's crossref fields, use the expanded entries attached to this task