From: Nik Garza <nikolas@applied.co>
To: git@vger.kernel.org
Subject: bug report - BUG: builtin/pack-objects.c:4310: should_include_obj should only be called on existing objects
Date: Fri, 25 Apr 2025 11:14:53 -0700 [thread overview]
Message-ID: <CA+ODqj2s68nPWzd1KHH3vUm3SiFHuf2b=+hmNuWesi-bo3c8_g@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 154 bytes --]
reporting the attached bug:
--
*Nikolas Garza*
Software Engineer
nikolas@applied.co
(209) 499-1193
Applied Intuition, Inc. <https://applied.co/>
[-- Attachment #1.2: Type: text/html, Size: 1774 bytes --]
[-- Attachment #2: git-bugreport-2025-04-24-1725.txt --]
[-- Type: text/plain, Size: 1905 bytes --]
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
Continually hitting a oack-objects error when fetching tags in my repo. This occurs in CI during critical jobs. The issues is flaky but leads to an unreliable system.
The Error:
ERROR: Failed to fetch git tags from origin!
Stdout:
Stderr:
BUG: builtin/pack-objects.c:4310: should_include_obj should only be called on existing objects
error: pack-objects died of signal 6
fatal: could not finish pack-objects to repack local links
fatal: index-pack failed
What did you do before the bug happened? (Steps to reproduce your issue)
ran the following:
git fetch origin refs/tags/<version-identified>.*refs/tags/<version-identifier.*
What did you expect to happen? (Expected behavior)
tags to be fetched to the CI machine running this command
What happened instead? (Actual behavior)
error above was thrown causing the job to fail
What's different between what you expected and what actually happened?
pretty simple...we expect the fetch to work as expected
Anything else you want to add:
we are pretty sure retries will resovle the issue but that shouldn't bne necessary.
we upgraded git from version 2.47.0 -> 2.49.0 and then started seeing the issue so we believe this is a low level git issue itself and not our use of git in our repo
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.49.0
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
libcurl: 8.5.0
zlib: 1.3
uname: Linux 5.15.0-134-generic #145~20.04.1-Ubuntu SMP Mon Feb 17 13:27:16 UTC 2025 x86_64
compiler info: gnuc: 13.3
libc info: glibc: 2.39
$SHELL (typically, interactive shell): <unset>
[Enabled Hooks]
post-checkout
post-commit
post-merge
pre-commit
pre-push
next reply other threads:[~2025-04-25 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 18:14 Nik Garza [this message]
2025-04-25 18:30 ` bug report - BUG: builtin/pack-objects.c:4310: should_include_obj should only be called on existing objects Elijah Newren
2025-04-28 19:23 ` Jonathan Tan
2025-04-28 22:55 ` Nik Garza
2025-10-17 15:57 ` Sam Estep
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+ODqj2s68nPWzd1KHH3vUm3SiFHuf2b=+hmNuWesi-bo3c8_g@mail.gmail.com' \
--to=nikolas@applied.co \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).