releng

Clone
Source Code
GIT

#11968 Get some error message when push the private branch to the fork google-noto-sans-cjk-fonts repo
Closed: upstream a year ago by jnsamyak. Opened a year ago by pwu.

Closed: upstream
Reopen Issue

I plan to add CI tests to the google-noto-sans-cjk-fonts repo.

Here are my steps to add the CI tests:
1. fedpkg clone google-noto-sans-cjk-fonts
2. fedpkg fork
3. git branch ci-tests and git checkout ci-tests
4. add one git commit for the CI tests
5. git push pwu ci-tests

I think the git push pwu ci-tests updated the fork repo,
but I got one error message from the remote log.

Here are the git push pwu ci-tests log:

epico@localhost:~/build/fedpkg/google-noto-sans-cjk-fonts$ git branch 
* ci-tests
  rawhide
epico@localhost:~/build/fedpkg/google-noto-sans-cjk-fonts$ git push pwu ci-tests 
The pre-push script can't check private branches. Push operation continues.
Enumerating objects: 17, done.
Counting objects: 100% (17/17), done.
Delta compression using up to 8 threads
Compressing objects: 100% (11/11), done.
Writing objects: 100% (16/16), 6.64 KiB | 6.64 MiB/s, done.
Total 16 (delta 1), reused 15 (delta 0), pack-reused 0
remote:   - to fedora-message
remote: 2024-02-19 05:48:24,637 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.branch.creation
remote: Sending to redis to log activity and send commit notification emails
remote: ERROR: ['git', 'diff', '--name-status', '-z', '^0000000000000000000000000000000000000000', '6a72681f0228f0dae29d649a5a9e04f62e0cff7f'] =-- 128
remote: 
remote: fatal: bad object 0000000000000000000000000000000000000000
remote: 
remote: * Publishing information for 1 commits
remote:   - to fedora-message
remote: 2024-02-19 05:48:24,819 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.receive
remote: 
remote: Create a pull-request for ci-tests
remote:    https://src.fedoraproject.org/fork/pwu/rpms/google-noto-sans-cjk-fonts/diff/rawhide..ci-tests
remote: 
To ssh://pkgs.fedoraproject.org/forks/pwu/rpms/google-noto-sans-cjk-fonts.git
 * [new branch]      ci-tests -> ci-tests
epico@localhost:~/build/fedpkg/google-noto-sans-cjk-fonts$ git push pwu ci-tests 
Everything up-to-date

Metadata Update from @jnsamyak:
- Issue tagged with: investigation
a year ago

Hi @pwu!

Thanks for opening the issue, I'll need to debug more on this issue as to why it happened, but from the first sight it seems the push went through without needing to do a force push but returned an error, need to debug on Repository Integrity or if there is any Pagure Configuration that leading to this :/

On debugging more the object ID mentioned (0000000000000000000000000000000000000000) seems like a placeholder which often is used in Git operations to signify a non-existent object. In this context, it likely refers to an attempt to compare changes against a base that doesn't exist or is inaccessible, possibly due to the branch's privacy settings or because the branch is new and does not have a common ancestor with the branch it's being compared against.
Edited a year ago by jnsamyak

Metadata Update from @kevin:
- Issue tagged with: low-gain, low-trouble
a year ago

I've seen this error on multiple occasions recently. Will try to check if it still happens and if it happens every time.

yep +1 @churchyard; I recently encountered it several times

 
[python3.12 (expat2.6 %)]$ git push -u churchyard expat2.6 
Enumerating objects: 30, done.
Counting objects: 100% (30/30), done.
Delta compression using up to 8 threads
Compressing objects: 100% (25/25), done.
Writing objects: 100% (25/25), 10.68 KiB | 3.56 MiB/s, done.
Total 25 (delta 15), reused 0 (delta 0), pack-reused 0
remote:   - to fedora-message
remote: 2024-02-21 10:58:45,153 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.branch.creation
remote: Sending to redis to log activity and send commit notification emails
remote: ERROR: ['git', 'diff', '--name-status', '-z', '^0000000000000000000000000000000000000000', '8003a0743841d0fa13246365e4a22172fb4cebcc'] =-- 128
remote: 
remote: fatal: bad object 0000000000000000000000000000000000000000
remote: 
remote: * Publishing information for 45 commits
remote:   - to fedora-message
remote: 2024-02-21 10:58:46,154 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.receive
remote: 
remote: Create a pull-request for expat2.6
remote:    https://src.fedoraproject.org/fork/churchyard/rpms/python3.12/diff/rawhide..expat2.6
remote: 
To ssh://pkgs.fedoraproject.org/forks/churchyard/rpms/python3.12.git
 * [new branch]      expat2.6 -> expat2.6
branch 'expat2.6' set up to track 'churchyard/expat2.6'.

Actually, I think the bug might be at this line:

            elif set(oldrev) == set(["0"]):
                oldrev = "^%s" % oldrev

I wonder if there's a typo in there, and the second line should be oldrev = "^%s" % newrev.
When the oldrev is 0000000, why would you want to replace it with ^000000? Using ^newrev seems more logical (you want the old rev to be the one prior to the new rev).

Has that changed anytime recently? Or has this been happening all along?

I think I meet this issue again for the pango package with f39 branch.

$ git push pwu f39 
Enumerating objects: 54, done.
Counting objects: 100% (54/54), done.
Delta compression using up to 8 threads
Compressing objects: 100% (46/46), done.
Writing objects: 100% (50/50), 10.73 KiB | 10.73 MiB/s, done.
Total 50 (delta 19), reused 13 (delta 4), pack-reused 0
remote:   - to fedora-message
remote: 2024-03-01 06:01:56,314 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.branch.creation
remote: Sending to redis to log activity and send commit notification emails
remote: ERROR: ['git', 'diff', '--name-status', '-z', '^0000000000000000000000000000000000000000', '24a79f1dab549f3f1878dfd61a9bcbc4b9a87c38'] =-- 128
remote: 
remote: fatal: bad object 0000000000000000000000000000000000000000
remote: 
remote: * Publishing information for 13 commits
remote:   - to fedora-message
remote: 2024-03-01 06:01:56,663 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.receive
remote: 
remote: Create a pull-request for f39
remote:    https://src.fedoraproject.org/fork/pwu/rpms/pango/diff/rawhide..f39
remote: 
To ssh://pkgs.fedoraproject.org/forks/pwu/rpms/pango.git
 * [new branch]      f39 -> f39

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak
a year ago

As we discussed in our releng meeting before, this looks and needs more of an upstream intervention rather than a releng impact; For the same, I have opened an issue at pagure repo.

Please feel free to watch that at this link: https://pagure.io/pagure/issue/5472

Metadata Update from @jnsamyak:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
a year ago

Metadata Update from @jnsamyak:
- Issue close_status updated to: upstream (was: Fixed)
a year ago

Log in to comment on this ticket.

Metadata

investigation low-gain low-trouble

None
None
None
None
None
None
Powered by Pagure 5.14.1
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.