#376 PR broken for »This pull request is broken due to missing fork information«

Open
opened 2 weeks ago by blizzz · 7 comments
blizzz commented 2 weeks ago

I have PR by me against a repo of my own. During further work, I amended a commit, added another one, and force-pushed everything to the related branch. The branch also is fine – the latest commit is present – but the PR says "This pull request is broken due to missing fork information.". Sounds like https://github.com/go-gitea/gitea/issues/11196, the affected PR is https://codeberg.org/blizzz/harbour-nextcloud-talk/pulls/19

I suppose I can recreate, no biggie, unless someone would like to have a look at this?

I have PR by me against a repo of my own. During further work, I amended a commit, added another one, and force-pushed everything to the related branch. The branch also is fine – the latest commit is present – but the PR says "This pull request is broken due to missing fork information.". Sounds like https://github.com/go-gitea/gitea/issues/11196, the affected PR is https://codeberg.org/blizzz/harbour-nextcloud-talk/pulls/19 I suppose I can recreate, no biggie, unless someone would like to have a look at this?
hw added the
bug
label 2 weeks ago
hw added the
gitea-related issue
label 2 weeks ago
hw commented 2 weeks ago
Poster
Owner

Where exactly do you see this error message?

Where exactly do you see this error message?
blizzz commented 2 weeks ago
Poster

Where exactly do you see this error message?

Yesterday it looked like on the screenshot.

Now it is not the case anymore, so it appanretly healed overnight somehow, I guess?

And a happy new year :)

> Where exactly do you see this error message? Yesterday it looked like on the screenshot. Now it is not the case anymore, so it appanretly healed overnight somehow, I guess? And a happy new year :)
6543 commented 2 weeks ago
Poster
Collaborator

I experienced something similar ... is codeberg running multible inctances behind a loadbalancer, if so it could be a "kind of race" condition ...

(on reloading a other instance did not recived the update from the other instance jet ...)

just some thoughts ...

I experienced something similar ... is codeberg running multible inctances behind a loadbalancer, if so it could be a "kind of race" condition ... (on reloading a other instance did not recived the update from the other instance jet ...) _just some thoughts_ ...
hw commented 2 weeks ago
Poster
Owner

One instance only atm

One instance only atm
blizzz commented 2 weeks ago
Poster

Might it be some background processing that just takes a bit?

Might it be some background processing that just takes a bit?
Poster
Owner

Could that happen when restarting gitea while something is happening?

Could that happen when restarting gitea while something is happening?
6543 commented 1 week ago
Poster
Collaborator

@ashimokawa

Could that happen when restarting gitea while something is happening?

should not but posible, depends on witch queue backend is used ...

@ashimokawa >Could that happen when restarting gitea while something is happening? should not but posible, depends on witch queue backend is used ...
Sign in to join this conversation.
No Milestone
No Assignees
4 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.