Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Repository appears to advertise refs that reference missing objects (fetch/push failing: "not our ref" / "promisor remote" / index-pack failed)#1954

Unanswered
berkaykrc asked this question inQuestions
Discussion options

First Check

  • I added a very descriptive title here.
  • I used the GitHub search to find a similar question and didn't find it.
  • I searched in the documentation/README.
  • I already searched in Google "How to do X" and didn't find any information.
  • I already read and followed all the tutorial in the docs/README and didn't find an answer.

Commit to Help

  • I commit to help with one of those options 👆

Example Code

git remote add upstream git@github.com:fastapi/full-stack-fastapi-template.gitgit fetch upstream --prune --verbosegit fetch --all --prune --verbose

Description

When fetching this repo as upstream I get errors showing refs that reference missing objects and server-side pack/index failures. I cannot fetch or push due to these missing objects. I have local corruption symptoms (some objects unreadable) and cannot recover them from the upstream clone.

fatal: remote error: upload-pack: not our ref 03e4ba1ef625116d28e3a920f6902977dca3631bfatal: could not fetch 3c918968c2f249bd3bac0da1335672be1d566188 from promisor remotefatal: fetch-pack: invalid index-pack output# when pushing from a local repo (pack creation failed due to unreadable object)fatal: unable to read d322e9d8a96cf1fcc767e15803ee28a598e0fe19remote: fatal: early EOFerror: remote unpack failed: index-pack failed

Requested server-side checks / actions
Please run these checks and maintenance steps on the upstream repository (or provide guidance / a healthy bundle):

git fsck --full — identify broken/missing objects
git repack -a -d
git gc --prune=now
If the repo is a mirror or backed by replication, check replication/pack transfer logs for missing objects or interrupted repacks.
If you cannot repair the current pack files, please consider providing:
a server-generated bundle (git bundle create repo-recovery.bundle --all) or
a fresh pack (pack-*.pack/.idx) that contains the missing objects, or
a fresh clone/mirror that others can fetch from.
If you prefer, you can also point me to an alternate mirror or provide the bundle and I will fetch and repack locally.

Why this matters

The fetch/push failures prevent forks and downstream users from syncing and make it impossible to recover missing objects locally. A server-side repair or a provided bundle will let me (and others) restore history and continue work.
Logs / environment notes

I can provide full GIT_TRACE output and git fsck output on request. Local git version: git/2.51.0 (if you need specific details I can paste the trace).
Thanks — please advise what you can run on the server or provide (bundle / mirror / fix).

Operating System

Linux

Operating System Details

Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.17.4-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ i5-14400F
Memory: 32 GiB of RAM (31,2 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 4070 SUPER
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7E02
System Version: 2.0

Python Version

3.12.10

Additional Context

git push -u origin feature/cart-promo-orderEnumerating objects: 5523, done.fatal: remote error: upload-pack: not our ref 002cc769c0c23753315cc5db755492008062ce04fatal: could not fetch d322e9d8a96cf1fcc767e15803ee28a598e0fe19 from promisor remoteremote: fatal: early EOFerror: remote unpack failed: index-pack failedTo github.com:IchibaOrg/basuketto.git ! [remote rejected] feature/cart-promo-order -> feature/cart-promo-order (failed)
You must be logged in to vote

Replies: 0 comments

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
questionFurther information is requested
1 participant
@berkaykrc

[8]ページ先頭

©2009-2025 Movatter.jp