Update from 1.14.1 to 1.15.0-rc "This pull request is broken due to missing fork information." after updating PR

[JHenneberg]

I am running gitea within a docker.

1. 1.14.1 create PR
2. update gitea to 1.15.0
3. update branch which is already an PR
4. "This pull request is broken due to missing fork information."

Also branches with PRs created post gitea update have the same issue.

There were already similar problems (#11105, #11196) and I followed the suggested solution if possible but without success.

• Gitea version (or commit ref): 1.15.0-rc1
• Git version: 2.32.0
• Operating system: Debian 10
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No

[6543]

@JHenneberg we need logs gitea print out to specify the issue

[JHenneberg]

Is there any easy way to sanitize the logs automatically?

Edit: Here is a short log:
gitea - Copy.log

• I created a fresh repo gitea_bug
• made a branch innocentFeature and immediately a PR
• pushed smth. ('changed smth') new onto the branch

and the result is:

although:

[6543]

There is no ...[E]… entry so gitea did not log an issue

[6543]

Does pushing an empty commit fix it?

[JHenneberg]

There is no ...[E]… entry so gitea did not log an issue

I realised this too.

Does pushing an empty commit fix it?

I did git commit --allow-empty -m "Empty commit"
Did not fix the problem

[zeripath]

Is this docker?

[JHenneberg]

Is this docker?

Yes it it.

[zeripath]

I bet this is an alpine 3.14 seccomp related issue.

[zeripath]

See https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.14.0

[zeripath]

We're hopefully about to release RC2 where we've reverted back to 3.13 because of these issues.

As alpine 3.14 percolates through the docker ecosystem users are going to be forced to update their docker installations to take account of its requirements, however, it's not our intention to force our users to do that right now.

[sigma-schn]

Updated installation to 1.15.0-rc2 (it's the same as @JHenneberg ones) and it worked again, thanks!

BTW: "latest" on Docker Hub points to 1.15.0-rc2, should be 1.14.5 ?

[zeripath]

That is a long story you can search our issues db for things relating to that and look at #16421

However, this problem is fixed therefore I'm closing and marking as a duplicate of #16428

(You really should look at how you upgrade your docker infrastructure because whilst we will downgrade/avoid 3.14 for 1.15 we will have to upgrade to it at some point and the rest of the docker ecosystem will use it.)