Strange action errors in mirrored projects?!

[somera]

Description

After update to 1.22.3 I see many of errors

in many mirrored projects?!

And than I saw this

or

or

or

What was activated with 1.22.3 release? What happens here?

Gitea Version

1.22.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.47.0

Operating System

Ubuntu 22.04.3 LTS x86_64

How are you running Gitea?

gitea-1.22.3-linux-amd64

Database

PostgreSQL

[somera]

I see that

are activated. But not for all mirror.

And I didn't activate it.

I have currently 319 mirrors with

select
	*
from
	repository
where
	is_mirror = true
and
	(num_action_runs > 0 or num_closed_action_runs > 0);

How can I check in the DB which mirrors has activated actions? I don't know the structure and I didn't find other corresponding columns.

[somera]

How can I fix it?

I can't go over the whole list and do it manualy.

When I deacticate the Actions in one specific project than I see the error

and when I click on the x I get 404 error.

[somera]

@lunny ?

[lunny]

@lunny ?

I will take a look today

[somera]

@lunny I see more and more mirrors with ...

[lunny]

I have no idea, maybe it's related to #32120 . @yp05327 @Zettat123

[Zettat123]

I see that

are activated. But not for all mirror.

And I didn't activate it.

Do you mean that the "Actions" unit of some repositories are automatically enabled after upgrading to v1.22.3? If so, I think this issue is not related to #32120. Did you upgrade from v1.22.2 to v1.22.3?

[somera]

I see that

are activated. But not for all mirror.
And I didn't activate it.

Do you mean that the "Actions" unit of some repositories are automatically enabled after upgrading to v1.22.3? If so, I think this issue is not related to #32120. Did you upgrade from v1.22.2 to v1.22.3?

Yes. After upgrade from 1.22.2 to 1.22.3 I see

And Actions are for the Mirrors activated. It makes no sense.

[somera]

Example

I didn't activate the Actions for all the affected projects.

And the red x is now after upgrade to 1.22.3.

When I add new mirror, Actions are activated -> is this right? Was this activated in 1.22.2 too?

• Should the Actions be activated or not? If yes, what happens here for mirrors?
• Why I see the whole failed old history?
• Why will be the red x shown for mirrors? Looks like an error for me. What changed here from 1.22.2 to 1.22.3?
• Is something broken is the main question for me.

[somera]

I compared 1.22.2 (older mirror status) and 1.22.3 instances for same mirrors.

1.22.2 -> actions tab is not activated, no red x visible
1.22.3 -> actions tab is activated, red x visible for "failed" actions in some projects

[somera]

Strange.

I imported an existing mirror in 1.22.2 in other orga on the same gite instance. And the new mirror has activated actions tab. In the old mirror the actions tab is not activated. When I update the old mirror the actions stay disabled.

What happens here?

[Zettat123]

When I add new mirror, Actions are activated -> is this right? Was this activated in 1.22.2 too?

Yes. New repositories (including mirrors) created in versions after v1.22 will have "Actions" enabled by default. See #27482. However, I don't think repositories created before v1.22 will automatically enable "Actions" after upgrading. I'll do some testing to confirm.

---

I've done my testing and can now confirm that mirror repositories created before v1.22 will not have "Actions" enabled after Gitea upgraded to v1.22. So I think repositories with "Actions" enabled should be created after v1.22.0

---

There is a proposal to disable "Actions" for mirror repositories by default. I support this idea.

• Disable Action unit by default when mirroring a repo? #30350

[yp05327]

When does these jobs start being triggered?

I can see some of them, but I'm sorry I don't know the language in your screenshot.

Does this mean last month?

And when did you upgrade the instance?

If the jobs are triggered before the update, it make sense. And I think this means before the update, the action unit is already enabled. But you said, they are disabled before the update, and enabled after the update, which is strange. And I have no idea about it yet.
But if they are all triggered after the update, it means during the update, action units was forcibly enabled. Then it should be a bug or something was wrong from Gitea side.