From: "Antoine R. Dumont (@ardumont)" <ardumont@softwareheritage.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: Simon TOURNIER <simon.tournier@inserm.fr>,
"swh-devel@inria.fr" <swh-devel@inria.fr>,
"guix-devel@gnu.org" <guix-devel@gnu.org>,
"ludovic.courtes" <ludovic.courtes@inria.fr>,
julien@malka.sh
Subject: Re: [swh-devel] Call for public review - SWH Nix/GNU Guix stack
Date: Fri, 19 Jan 2024 17:44:36 +0100 [thread overview]
Message-ID: <87zfx1nuh7.fsf@gmail.com> (raw)
In-Reply-To: <871qahc8rr.fsf@ngyro.com>
[-- Attachment #1: Type: text/plain, Size: 2546 bytes --]
Hello,
> Is that because the changes you describe were done after the staging
> data was loaded or is it a bug?
Our staging instance inherits its append-only property from our main
archive. In the staging case (for "prototypes", soon-to-be-deployed new
feature or so), that makes it hard to see through the "old bug" noise.
It's old origins that were ingested initially with a first version of
the lister (which got iteratively fixed).
----
@anlambert made a pass this week in docker (from scratch) to check (thx ;)
> Excellent! I believe this addresses a problem we recently reported
> regarding tarballs published with our own content-addressed URLs, which
> look like:
>
> https://bordeaux.guix.gnu.org/file/BiocNeighbors_1.20.0.tar.gz/sha256/0a5wg099fgwjbzd6r3mr4l02rcmjqlkdcz1w97qzwx1mir41fmas
As a result, he actually enhanced the listing so the urls mentioned
earlier ^ is treated correctly out of the data in the url. (@me That
needs a bump in deployment [for next week])
Early on, I was referring to another heuristic using a HEAD query to
parse header informations [if any]. As that specific url does not
provide any, so it passed through.
----
Note: cc-ed julien@malka.sh instead of community@nixos.org (as asked in
the thread)
Cheers,
--
tony / Antoine R. Dumont (@ardumont)
-----------------------------------------------------------------
gpg fingerprint BF00 203D 741A C9D5 46A8 BE07 52E2 E984 0D10 C3B8
Timothy Sample <samplet@ngyro.com> writes:
> Hello,
>
> This is very exciting work, thanks everyone!
>
> "Antoine R. Dumont (@ardumont)" <ardumont@softwareheritage.org> writes:
>
>> FWIW, in the "new" lister [1] implementation, there are a bunch of extra
>> computations done [1] to try and resolve those situations. It's trying
>> to fetch more information from upstream server (e.g. crates urls which
>> ends in /download, ...) now. It's probably not exhaustive though.
>>
>> [1] https://gitlab.softwareheritage.org/swh/devel/swh-lister/-/blob/master/swh/lister/nixguix/lister.py?ref_type=heads
>
> I was just looking over some of the new results and noticed that crates
> are being treated as ‘content’ rather than ‘tarball-directory’. E.g.:
>
> https://webapp.staging.swh.network/browse/content/sha1_git:e05b33b2d3b40254ceaaa5fe4c501d1b15c75ea6/?origin_url=https://crates.io/api/v1/crates/diff/0.1.12/download
>
> Is that because the changes you describe were done after the staging
> data was loaded or is it a bug?
>
>
> -- Tim
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
prev parent reply other threads:[~2024-01-19 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKFPOSwdnSgjtOSW2CbaNyDEivGqan-gJaE_GVrZ7tbj83zRhg@mail.gmail.com>
2024-01-11 12:32 ` [swh-devel] Call for public review - SWH Nix/GNU Guix stack Ludovic Courtès
2024-01-12 18:42 ` Simon TOURNIER
2024-01-15 9:04 ` Antoine R. Dumont (@ardumont)
2024-01-15 11:22 ` Ludovic Courtès
2024-01-16 20:39 ` Timothy Sample
2024-01-19 16:44 ` Antoine R. Dumont (@ardumont) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zfx1nuh7.fsf@gmail.com \
--to=ardumont@softwareheritage.org \
--cc=guix-devel@gnu.org \
--cc=julien@malka.sh \
--cc=ludovic.courtes@inria.fr \
--cc=samplet@ngyro.com \
--cc=simon.tournier@inserm.fr \
--cc=swh-devel@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).