public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dilyan.palauzov at aegee dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/114223] New: Utilize filtering for git://gcc.gnu.org/git/gcc.git
Date: Sun, 03 Mar 2024 20:18:02 +0000	[thread overview]
Message-ID: <bug-114223-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114223

            Bug ID: 114223
           Summary: Utilize filtering for git://gcc.gnu.org/git/gcc.git
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: web
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dilyan.palauzov at aegee dot org
  Target Milestone: ---

I want to create a treeless-copy of the git://gcc.gnu.org/git/gcc.git . 
https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/
explains what treeless is.


> $ git clone --filter=tree:0 git://gcc.gnu.org/git/gcc.git 
> Cloning into 'gcc'...
> warning: filtering not recognized by server, ignoring
…

When I utilize https://github.com/HaleTom/git-bloblessify/ to strip the
unneeded git blobs, eventually it reports

…
Fetching tags and HEAD's trees...
warning: filtering not recognized by server, ignoring
remote: Enumerating objects: 2342589, done.
remote: Counting objects: 100% (316017/316017), done.
remote: Compressing objects: 100% (20610/20610), done.
remote: Total 2342589 (delta 307150), reused 295435 (delta 295402), pack-reused
2026572
Receiving objects: 100% (2342589/2342589), 929.71 MiB | 6.40 MiB/s, done.
Resolving deltas: 100% (1915402/1915402), done.
warning: filtering not recognized by server, ignoring
remote: Enumerating objects: 2622955, done.
remote: Counting objects: 100% (301209/301209), done.
remote: Compressing objects: 100% (21051/21051), done.
remote: Total 2622955 (delta 293664), reused 280316 (delta 280149), pack-reused
2321746
Receiving objects: 100% (2622955/2622955), 1.01 GiB | 5.50 MiB/s, done.
Resolving deltas: 100% (2148507/2148507), done.
fatal: bad object 31ff5e249df46ff122b115c86af04022307fafa4
error: git://gcc.gnu.org/git/gcc.git did not send all necessary objects

git-bloblessify: clean-up: previous git objects have been restored
git-bloblessify: check remote origin config remains correct
remote.origin.url=git://gcc.gnu.org/git/gcc.git
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
remote.origin.promisor=true
remote.origin.partialclonefilter=blob:none
git-bloblessify: exiting with error code: 1

I guess the 

fatal: bad object 31ff5e249df46ff122b115c86af04022307fafa4
error: git://gcc.gnu.org/git/gcc.git did not send all necessary objects


means some network error and retrying might help.  However retrying takes very
long, and might also not work, because of some other network error.

Please utilize server-side filtering on git://gcc.gnu.org/git/gcc.git  , so
that

> $ git clone --filter=tree:0 git://gcc.gnu.org/git/gcc.git 

does not print

> warning: filtering not recognized by server, ignoring

             reply	other threads:[~2024-03-03 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-03 20:18 dilyan.palauzov at aegee dot org [this message]
2024-03-03 21:01 ` [Bug web/114223] " mark at gcc dot gnu.org
2024-03-04  2:07 ` fche at redhat dot com
2024-03-04 10:30 ` redi at gcc dot gnu.org

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-114223-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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.
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).