Strange action errors in mirrored projects?! #13585

New Issue

Closed

opened 2025-11-02 10:47:00 -06:00 by GiteaMirror · 38 comments

GiteaMirror commented 2025-11-02 10:47:00 -06:00

Owner

Copy Link

Originally created by @somera on GitHub (Oct 10, 2024).

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

Originally created by @somera on GitHub (Oct 10, 2024). ### 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

GiteaMirror added the topic/gitea-actionstype/bugissue/workaround labels 2025-11-02 10:47:00 -06:00

GiteaMirror closed this issue 2025-11-02 10:47:00 -06:00

GiteaMirror commented 2025-11-02 10:47:01 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 10, 2024):

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 commented on GitHub (Oct 10, 2024): 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.

GiteaMirror commented 2025-11-02 10:47:01 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 10, 2024):

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 commented on GitHub (Oct 10, 2024): 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.

GiteaMirror commented 2025-11-02 10:47:01 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 10, 2024):

@lunny ?

@somera commented on GitHub (Oct 10, 2024): @lunny ?

GiteaMirror commented 2025-11-02 10:47:02 -06:00

Author

Owner

Copy Link

@lunny commented on GitHub (Oct 10, 2024):

@lunny ?

I will take a look today

@lunny commented on GitHub (Oct 10, 2024): > @lunny ? I will take a look today

GiteaMirror commented 2025-11-02 10:47:02 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 12, 2024):

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

@somera commented on GitHub (Oct 12, 2024): @lunny I see more and more mirrors with ... 

GiteaMirror commented 2025-11-02 10:47:02 -06:00

Author

Owner

Copy Link

@lunny commented on GitHub (Oct 13, 2024):

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

@lunny commented on GitHub (Oct 13, 2024): I have no idea, maybe it's related to #32120 . @yp05327 @Zettat123

GiteaMirror commented 2025-11-02 10:47:02 -06:00

Author

Owner

Copy Link

@Zettat123 commented on GitHub (Oct 14, 2024):

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?

@Zettat123 commented on GitHub (Oct 14, 2024): > 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?

GiteaMirror commented 2025-11-02 10:47:03 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 14, 2024):

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 commented on GitHub (Oct 14, 2024): > > 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.

GiteaMirror commented 2025-11-02 10:47:03 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 14, 2024):

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 commented on GitHub (Oct 14, 2024): 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.

GiteaMirror commented 2025-11-02 10:47:03 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 14, 2024):

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 commented on GitHub (Oct 14, 2024): 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

GiteaMirror commented 2025-11-02 10:47:03 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 14, 2024):

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?

@somera commented on GitHub (Oct 14, 2024): 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?

GiteaMirror commented 2025-11-02 10:47:04 -06:00

Author

Owner

Copy Link

@Zettat123 commented on GitHub (Oct 15, 2024):

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.

• #30350

@Zettat123 commented on GitHub (Oct 15, 2024): > 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. - #30350

GiteaMirror commented 2025-11-02 10:47:04 -06:00

Author

Owner

Copy Link

@yp05327 commented on GitHub (Oct 15, 2024):

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.

@yp05327 commented on GitHub (Oct 15, 2024): 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.

GiteaMirror commented 2025-11-02 10:47:04 -06:00

Author

Owner

Copy Link

@Zettat123 commented on GitHub (Oct 15, 2024):

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.

This is where I suspect a bug exists. But I can't find any evidence that Gitea forcibly enabled the "Actions" unit.

@Zettat123 commented on GitHub (Oct 15, 2024): > 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. This is where I suspect a bug exists. But I can't find any evidence that Gitea forcibly enabled the "Actions" unit.

GiteaMirror commented 2025-11-02 10:47:04 -06:00

Author

Owner

Copy Link

@yp05327 commented on GitHub (Oct 15, 2024):

@Zettat123
Yes. I think it is the point, as there are several possible cases, so I asked, and then we can know what happened.

@yp05327 commented on GitHub (Oct 15, 2024): @Zettat123 Yes. I think it is the point, as there are several possible cases, so I asked, and then we can know what happened.

GiteaMirror commented 2025-11-02 10:47:04 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 15, 2024):

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?

It's German. And it mean last month.

I'm wondering too, that I see this actions.

And when did you upgrade the instance?

~2 days aftrer 1.22.3 was released.

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.

But i didn't enable any actions. I checked a lot of mirrors and most of them has no activated actions.

@somera commented on GitHub (Oct 15, 2024): > 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`? It's German. And it mean last month. I'm wondering too, that I see this actions. > > And when did you upgrade the instance? ~2 days aftrer 1.22.3 was released. > 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. But i didn't enable any actions. I checked a lot of mirrors and most of them has no activated actions.

GiteaMirror commented 2025-11-02 10:47:04 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 15, 2024):

This https://github.com/auth0/go-auth0 is an mirror.

2 months ago

And 1.22.3 was upgraded on 09.10.2024

And here othe mirror with activated action but wihout any errors

Other mirror ...

I don't know how many are affected.

@somera commented on GitHub (Oct 15, 2024): This https://github.com/auth0/go-auth0 is an mirror. 2 months ago  And 1.22.3 was upgraded on 09.10.2024  And here othe mirror with activated action but wihout any errors  Other mirror ...  I don't know how many are affected.

GiteaMirror commented 2025-11-02 10:47:05 -06:00

Author

Owner

Copy Link

@yp05327 commented on GitHub (Oct 15, 2024):

And here othe mirror with activated action but wihout any errors

This is because the trigger of these 2 workflows are creating PR to main branch and workflow_dispatch (manually excute)

ps: for @Zettat123, the workflow files:
https://github.com/stanford-oval/storm/tree/main/.github/workflows

@yp05327 commented on GitHub (Oct 15, 2024): > And here othe mirror with activated action but wihout any errors This is because the trigger of these 2 workflows are creating PR to main branch and workflow_dispatch (manually excute) ps: for @Zettat123, the workflow files: https://github.com/stanford-oval/storm/tree/main/.github/workflows

GiteaMirror commented 2025-11-02 10:47:05 -06:00

Author

Owner

Copy Link

@yp05327 commented on GitHub (Oct 15, 2024):

So IMO, actually, there's no bug and the only thing you need is #30350

@yp05327 commented on GitHub (Oct 15, 2024): So IMO, actually, there's no bug and the only thing you need is #30350

GiteaMirror commented 2025-11-02 10:47:05 -06:00

Author

Owner

Copy Link

@Zettat123 commented on GitHub (Oct 15, 2024):

And here othe mirror with activated action but wihout any errors

This is because the trigger of these 2 workflows are creating PR to main branch and workflow_dispatch (manually excute)

ps: for @Zettat123, the workflow files: https://github.com/stanford-oval/storm/tree/main/.github/workflows

I see. Actually, the "Actions" unit was enabled for all repositories, but only some of them had actions runs due to workflow triggers.

@Zettat123 commented on GitHub (Oct 15, 2024): > > And here othe mirror with activated action but wihout any errors > > This is because the trigger of these 2 workflows are creating PR to main branch and workflow_dispatch (manually excute) > > ps: for @Zettat123, the workflow files: https://github.com/stanford-oval/storm/tree/main/.github/workflows I see. Actually, the "Actions" unit was enabled for all repositories, but only some of them had actions runs due to workflow triggers.

GiteaMirror commented 2025-11-02 10:47:05 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 15, 2024):

Will the patch make it like it was before or does something still need to be fixed in the database?

@somera commented on GitHub (Oct 15, 2024): Will the patch make it like it was before or does something still need to be fixed in the database?

GiteaMirror commented 2025-11-02 10:47:06 -06:00

Author

Owner

Copy Link

@yp05327 commented on GitHub (Oct 15, 2024):

In another way, it is not difficult to implement a new options when migrating the repo.
But how to handle these existing mirrors, adding a migration or a maintenance operation or doctor command?

@yp05327 commented on GitHub (Oct 15, 2024): In another way, it is not difficult to implement a new options when migrating the repo. But how to handle these existing mirrors, adding a migration or a maintenance operation or doctor command?

GiteaMirror commented 2025-11-02 10:47:06 -06:00

Author

Owner

Copy Link

@Zettat123 commented on GitHub (Oct 15, 2024):

To batch disable the "Actions" unit of existing mirrors, users can use the API PATCH
/repos/{owner}/{repo} to update repos.

@Zettat123 commented on GitHub (Oct 15, 2024): To batch disable the "Actions" unit of existing mirrors, users can use the API [PATCH /repos/{owner}/{repo}](https://gitea.com/api/swagger#/repository/repoEdit) to update repos.

GiteaMirror commented 2025-11-02 10:47:06 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 15, 2024):

In another way, it is not difficult to implement a new options when migrating the repo. But how to handle these existing mirrors, adding a migration or a maintenance operation or doctor command?

Doctor commands sounds good. I have ~20000 mirrors.

How can I check in the DB how many mirrors are at the moment affeced?

And when I disable Actions for some mirrors in the UI the red x and orange o stay.

@somera commented on GitHub (Oct 15, 2024): > In another way, it is not difficult to implement a new options when migrating the repo. But how to handle these existing mirrors, adding a migration or a maintenance operation or doctor command? Doctor commands sounds good. I have ~20000 mirrors. How can I check in the DB how many mirrors are at the moment affeced? And when I disable Actions for some mirrors in the UI the red x and orange o stay. 

GiteaMirror commented 2025-11-02 10:47:06 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 15, 2024):

And today I see first system messages

I missing here info to the project.

2024/10/15 19:50:18 ...eb/routing/logger.go:102:func1() [I] router: completed GET /repo/search?sort=updated&order=desc&uid=1&team_id=undefined&q=&page=1&limit=15&mode=&archived=false for 192.168.178.21:0, 200 OK in 95.1ms @ repo/repo.go:556(repo.SearchRepo)
2024/10/15 19:50:22 ...ns/schedule_tasks.go:87:startTasks() [E] CreateScheduleTask: SetJob: yaml: line 15: did not find expected key
        /source/services/actions/schedule_tasks.go:87 (0x1ec5678)
        /source/services/actions/schedule_tasks.go:24 (0x25858bc)
        /source/services/cron/tasks_actions.go:63 (0x25858bd)
        /source/services/cron/tasks.go:111 (0x25824c7)
        /source/modules/graceful/manager.go:92 (0xaa9d26)
        /source/services/cron/tasks.go:88 (0x258223a)
        /source/services/cron/tasks.go:67 (0x2586d93)
        /usr/local/go/src/reflect/value.go:596 (0x4fccc5)
                Value.call: call(frametype, fn, stackArgs, uint32(frametype.Size()), uint32(abid.retOffset), uint32(frameSize), &regArgs)
        /usr/local/go/src/reflect/value.go:380 (0x4fbdd8)
                Value.Call: return v.call("Call", in)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/gocron.go:122 (0x2563904)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:87 (0x2561b31)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:213 (0x2562817)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:269 (0x25632b7)
        /usr/local/go/src/runtime/asm_amd64.s:1695 (0x47b0a0)
                goexit: BYTE    $0x90   // NOP

and a lot exceptions

2024/10/15 14:04:22 ...irror/mirror_pull.go:178:parseRemoteUpdateOutput() [W] parseRemoteUpdateOutput: unexpected update line " * [new ref]         refs/pull/798/head  -> refs/pull/798/head"
2024/10/15 14:04:22 ...irror/mirror_pull.go:178:parseRemoteUpdateOutput() [W] parseRemoteUpdateOutput: unexpected update line " * [new ref]         refs/pull/798/merge -> refs/pull/798/merge"
2024/10/15 14:05:22 ...ns/schedule_tasks.go:87:startTasks() [E] CreateScheduleTask: SetJob: yaml: line 15: did not find expected key
        /source/services/actions/schedule_tasks.go:87 (0x1ec5678)
        /source/services/actions/schedule_tasks.go:24 (0x25858bc)
        /source/services/cron/tasks_actions.go:63 (0x25858bd)
        /source/services/cron/tasks.go:111 (0x25824c7)
        /source/modules/graceful/manager.go:92 (0xaa9d26)
        /source/services/cron/tasks.go:88 (0x258223a)
        /source/services/cron/tasks.go:67 (0x2586d93)
        /usr/local/go/src/reflect/value.go:596 (0x4fccc5)
                Value.call: call(frametype, fn, stackArgs, uint32(frametype.Size()), uint32(abid.retOffset), uint32(frameSize), &regArgs)
        /usr/local/go/src/reflect/value.go:380 (0x4fbdd8)
                Value.Call: return v.call("Call", in)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/gocron.go:122 (0x2563904)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:87 (0x2561b31)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:213 (0x2562817)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:269 (0x25632b7)
        /usr/local/go/src/runtime/asm_amd64.s:1695 (0x47b0a0)
                goexit: BYTE    $0x90   // NOP


2024/10/15 14:06:22 ...ns/schedule_tasks.go:87:startTasks() [E] CreateScheduleTask: SetJob: yaml: line 15: did not find expected key
        /source/services/actions/schedule_tasks.go:87 (0x1ec5678)
        /source/services/actions/schedule_tasks.go:24 (0x25858bc)
        /source/services/cron/tasks_actions.go:63 (0x25858bd)
        /source/services/cron/tasks.go:111 (0x25824c7)
        /source/modules/graceful/manager.go:92 (0xaa9d26)
        /source/services/cron/tasks.go:88 (0x258223a)
        /source/services/cron/tasks.go:67 (0x2586d93)
        /usr/local/go/src/reflect/value.go:596 (0x4fccc5)
                Value.call: call(frametype, fn, stackArgs, uint32(frametype.Size()), uint32(abid.retOffset), uint32(frameSize), &regArgs)
        /usr/local/go/src/reflect/value.go:380 (0x4fbdd8)
                Value.Call: return v.call("Call", in)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/gocron.go:122 (0x2563904)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:87 (0x2561b31)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:213 (0x2562817)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:269 (0x25632b7)
        /usr/local/go/src/runtime/asm_amd64.s:1695 (0x47b0a0)
                goexit: BYTE    $0x90   // NOP


2024/10/15 14:07:22 ...ns/schedule_tasks.go:87:startTasks() [E] CreateScheduleTask: SetJob: yaml: line 15: did not find expected key
        /source/services/actions/schedule_tasks.go:87 (0x1ec5678)
        /source/services/actions/schedule_tasks.go:24 (0x25858bc)
        /source/services/cron/tasks_actions.go:63 (0x25858bd)
        /source/services/cron/tasks.go:111 (0x25824c7)
        /source/modules/graceful/manager.go:92 (0xaa9d26)
        /source/services/cron/tasks.go:88 (0x258223a)
        /source/services/cron/tasks.go:67 (0x2586d93)
        /usr/local/go/src/reflect/value.go:596 (0x4fccc5)
                Value.call: call(frametype, fn, stackArgs, uint32(frametype.Size()), uint32(abid.retOffset), uint32(frameSize), &regArgs)
        /usr/local/go/src/reflect/value.go:380 (0x4fbdd8)
                Value.Call: return v.call("Call", in)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/gocron.go:122 (0x2563904)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:87 (0x2561b31)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:213 (0x2562817)
        /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:269 (0x25632b7)
        /usr/local/go/src/runtime/asm_amd64.s:1695 (0x47b0a0)
                goexit: BYTE    $0x90   // NOP

@somera commented on GitHub (Oct 15, 2024): And today I see first system messages  I missing here info to the project. ``` 2024/10/15 19:50:18 ...eb/routing/logger.go:102:func1() [I] router: completed GET /repo/search?sort=updated&order=desc&uid=1&team_id=undefined&q=&page=1&limit=15&mode=&archived=false for 192.168.178.21:0, 200 OK in 95.1ms @ repo/repo.go:556(repo.SearchRepo) 2024/10/15 19:50:22 ...ns/schedule_tasks.go:87:startTasks() [E] CreateScheduleTask: SetJob: yaml: line 15: did not find expected key /source/services/actions/schedule_tasks.go:87 (0x1ec5678) /source/services/actions/schedule_tasks.go:24 (0x25858bc) /source/services/cron/tasks_actions.go:63 (0x25858bd) /source/services/cron/tasks.go:111 (0x25824c7) /source/modules/graceful/manager.go:92 (0xaa9d26) /source/services/cron/tasks.go:88 (0x258223a) /source/services/cron/tasks.go:67 (0x2586d93) /usr/local/go/src/reflect/value.go:596 (0x4fccc5) Value.call: call(frametype, fn, stackArgs, uint32(frametype.Size()), uint32(abid.retOffset), uint32(frameSize), &regArgs) /usr/local/go/src/reflect/value.go:380 (0x4fbdd8) Value.Call: return v.call("Call", in) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/gocron.go:122 (0x2563904) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:87 (0x2561b31) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:213 (0x2562817) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:269 (0x25632b7) /usr/local/go/src/runtime/asm_amd64.s:1695 (0x47b0a0) goexit: BYTE $0x90 // NOP ``` and a lot exceptions ``` 2024/10/15 14:04:22 ...irror/mirror_pull.go:178:parseRemoteUpdateOutput() [W] parseRemoteUpdateOutput: unexpected update line " * [new ref] refs/pull/798/head -> refs/pull/798/head" 2024/10/15 14:04:22 ...irror/mirror_pull.go:178:parseRemoteUpdateOutput() [W] parseRemoteUpdateOutput: unexpected update line " * [new ref] refs/pull/798/merge -> refs/pull/798/merge" 2024/10/15 14:05:22 ...ns/schedule_tasks.go:87:startTasks() [E] CreateScheduleTask: SetJob: yaml: line 15: did not find expected key /source/services/actions/schedule_tasks.go:87 (0x1ec5678) /source/services/actions/schedule_tasks.go:24 (0x25858bc) /source/services/cron/tasks_actions.go:63 (0x25858bd) /source/services/cron/tasks.go:111 (0x25824c7) /source/modules/graceful/manager.go:92 (0xaa9d26) /source/services/cron/tasks.go:88 (0x258223a) /source/services/cron/tasks.go:67 (0x2586d93) /usr/local/go/src/reflect/value.go:596 (0x4fccc5) Value.call: call(frametype, fn, stackArgs, uint32(frametype.Size()), uint32(abid.retOffset), uint32(frameSize), &regArgs) /usr/local/go/src/reflect/value.go:380 (0x4fbdd8) Value.Call: return v.call("Call", in) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/gocron.go:122 (0x2563904) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:87 (0x2561b31) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:213 (0x2562817) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:269 (0x25632b7) /usr/local/go/src/runtime/asm_amd64.s:1695 (0x47b0a0) goexit: BYTE $0x90 // NOP 2024/10/15 14:06:22 ...ns/schedule_tasks.go:87:startTasks() [E] CreateScheduleTask: SetJob: yaml: line 15: did not find expected key /source/services/actions/schedule_tasks.go:87 (0x1ec5678) /source/services/actions/schedule_tasks.go:24 (0x25858bc) /source/services/cron/tasks_actions.go:63 (0x25858bd) /source/services/cron/tasks.go:111 (0x25824c7) /source/modules/graceful/manager.go:92 (0xaa9d26) /source/services/cron/tasks.go:88 (0x258223a) /source/services/cron/tasks.go:67 (0x2586d93) /usr/local/go/src/reflect/value.go:596 (0x4fccc5) Value.call: call(frametype, fn, stackArgs, uint32(frametype.Size()), uint32(abid.retOffset), uint32(frameSize), &regArgs) /usr/local/go/src/reflect/value.go:380 (0x4fbdd8) Value.Call: return v.call("Call", in) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/gocron.go:122 (0x2563904) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:87 (0x2561b31) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:213 (0x2562817) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:269 (0x25632b7) /usr/local/go/src/runtime/asm_amd64.s:1695 (0x47b0a0) goexit: BYTE $0x90 // NOP 2024/10/15 14:07:22 ...ns/schedule_tasks.go:87:startTasks() [E] CreateScheduleTask: SetJob: yaml: line 15: did not find expected key /source/services/actions/schedule_tasks.go:87 (0x1ec5678) /source/services/actions/schedule_tasks.go:24 (0x25858bc) /source/services/cron/tasks_actions.go:63 (0x25858bd) /source/services/cron/tasks.go:111 (0x25824c7) /source/modules/graceful/manager.go:92 (0xaa9d26) /source/services/cron/tasks.go:88 (0x258223a) /source/services/cron/tasks.go:67 (0x2586d93) /usr/local/go/src/reflect/value.go:596 (0x4fccc5) Value.call: call(frametype, fn, stackArgs, uint32(frametype.Size()), uint32(abid.retOffset), uint32(frameSize), &regArgs) /usr/local/go/src/reflect/value.go:380 (0x4fbdd8) Value.Call: return v.call("Call", in) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/gocron.go:122 (0x2563904) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:87 (0x2561b31) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:213 (0x2562817) /go/pkg/mod/github.com/go-co-op/gocron@v1.37.0/executor.go:269 (0x25632b7) /usr/local/go/src/runtime/asm_amd64.s:1695 (0x47b0a0) goexit: BYTE $0x90 // NOP ```

GiteaMirror commented 2025-11-02 10:47:07 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 15, 2024):

Same #30244

@somera commented on GitHub (Oct 15, 2024): Same #30244

GiteaMirror commented 2025-11-02 10:47:07 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 15, 2024):

Can I use this

; [actions]
;; Enable/Disable actions capabilities
;ENABLED = false

to disable action temporary?

And this

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Cleanup expired actions assets
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;[cron.cleanup_actions]
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;ENABLED = true
;RUN_AT_START = true
;SCHEDULE = @midnight

to cleanup all the action jobs?

@somera commented on GitHub (Oct 15, 2024): Can I use this ``` ; [actions] ;; Enable/Disable actions capabilities ;ENABLED = false ``` to disable action temporary? And this ``` ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; Cleanup expired actions assets ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;[cron.cleanup_actions] ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;ENABLED = true ;RUN_AT_START = true ;SCHEDULE = @midnight ``` to cleanup all the action jobs?

GiteaMirror commented 2025-11-02 10:47:07 -06:00

Author

Owner

Copy Link

@yp05327 commented on GitHub (Oct 16, 2024):

It is a global setting for all repos, if you do not need to use actions in this instance, you can disable it globally.

Clean up only remove action job log, related data and artififacts, it will not delete those action jobs.

@yp05327 commented on GitHub (Oct 16, 2024): It is a global setting for all repos, if you do not need to use actions in this instance, you can disable it globally. Clean up only remove action job log, related data and artififacts, it will not delete those action jobs.

GiteaMirror commented 2025-11-02 10:47:07 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 17, 2024):

It is a global setting for all repos, if you do not need to use actions in this instance, you can disable it globally.

Thx,

Clean up only remove action job log, related data and artififacts, it will not delete those action jobs.

hm.

Are you working on a solution to this problem?

The failed action jobs are flooding my system messages view.

@somera commented on GitHub (Oct 17, 2024): > It is a global setting for all repos, if you do not need to use actions in this instance, you can disable it globally. Thx, > Clean up only remove action job log, related data and artififacts, it will not delete those action jobs. hm. Are you working on a solution to this problem? The failed action jobs are flooding my system messages view.

GiteaMirror commented 2025-11-02 10:47:08 -06:00

Author

Owner

Copy Link

@yp05327 commented on GitHub (Oct 17, 2024):

For existing mirrors, no good solution from me.

As it is related to repo_unit table in DB.
If there's a record with unit type 10 (action), and it is not globally disabled, then it means action unit is enabled.
We can not simply remove these records in migration, as users may need it.
So we can only do it by ourselves (cli or sql) or add a new maintenance operations, but it is not a usually used feature I think, so maybe there's no worth to implement it.

↑ It is for the action jobs

And the commit status (x in dashboard repo list) is recorded in another table, and if you don't want to see them, maybe you also need to clean it.

So, as a summary, I have no good idea now for completely solving it for these existing mirrors.

@yp05327 commented on GitHub (Oct 17, 2024): For existing mirrors, no good solution from me. As it is related to `repo_unit` table in DB. If there's a record with unit type 10 (action), and it is not globally disabled, then it means action unit is enabled. We can not simply remove these records in migration, as users may need it. So we can only do it by ourselves (cli or sql) or add a new maintenance operations, but it is not a usually used feature I think, so maybe there's no worth to implement it. ↑ It is for the action jobs And the commit status (`x` in dashboard repo list) is recorded in another table, and if you don't want to see them, maybe you also need to clean it. So, as a summary, I have no good idea now for completely solving it for these **existing mirrors**.

GiteaMirror commented 2025-11-02 10:47:08 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 17, 2024):

Understand. Means I have fix it for ~20.000 mirrors by myself. Or I do

To batch disable the "Actions" unit of existing mirrors, users can use the API PATCH /repos/{owner}/{repo} to update repos.

this with an script for all the mirrors?

I this case I should send only has_actions = false as an json? Right?

This will disable the action. And how can I than fix this

?

@somera commented on GitHub (Oct 17, 2024): Understand. Means I have fix it for ~20.000 mirrors by myself. Or I do > To batch disable the "Actions" unit of existing mirrors, users can use the API [PATCH /repos/{owner}/{repo}](https://gitea.com/api/swagger#/repository/repoEdit) to update repos. this with an script for all the mirrors? I this case I should send **only** has_actions = false as an json? Right? This will disable the action. And how can I than fix this  ?

GiteaMirror commented 2025-11-02 10:47:08 -06:00

Author

Owner

Copy Link

@Zettat123 commented on GitHub (Oct 18, 2024):

I this case I should send only has_actions = false as an json? Right?

Yes. You only need to set the fields that need to be changed.

9116665e9c/routers/api/v1/repo/repo.go (L1018-L1027)

@Zettat123 commented on GitHub (Oct 18, 2024): > I this case I should send only has_actions = false as an json? Right? Yes. You only need to set the fields that need to be changed. https://github.com/go-gitea/gitea/blob/9116665e9c1c01d882c919fb3058f7fdb695350e/routers/api/v1/repo/repo.go#L1018-L1027

GiteaMirror commented 2025-11-02 10:47:08 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 18, 2024):

@Zettat123 I did this for ~3500 mirrors. Looks good.

And what should be removed in th database to remove this

?

This is visible after I set has_actions = false. And click on the x or o show 404.

@somera commented on GitHub (Oct 18, 2024): @Zettat123 I did this for ~3500 mirrors. Looks good. And what should be removed in th database to remove this  ? This is visible after I set has_actions = false. And click on the x or o show 404.

GiteaMirror commented 2025-11-02 10:47:08 -06:00

Author

Owner

Copy Link

@lunny commented on GitHub (Oct 20, 2024):

I think these commit status can be removed manually from the database with

delete from commit_status where repo_id = (select id from repository where is_mirror = true)
delete from commit_status_summary where repo_id = (select id from repository where is_mirror = true)

@lunny commented on GitHub (Oct 20, 2024): I think these commit status can be removed manually from the database with ``` delete from commit_status where repo_id = (select id from repository where is_mirror = true) delete from commit_status_summary where repo_id = (select id from repository where is_mirror = true) ```

GiteaMirror commented 2025-11-02 10:47:09 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 21, 2024):

I this case I should send only has_actions = false as an json? Right?

Yes. You only need to set the fields that need to be changed.

I have now a script which I run after I added some new mirrors.

But for the next release there will be a fix in gitea? Means, when I import new mirror "Actions" will be deactivated by default?

I think these commit status can be removed manually from the database with

delete from commit_status where repo_id = (select id from repository where is_mirror = true)
delete from commit_status_summary where repo_id = (select id from repository where is_mirror = true)

Thx. I try this next weekend with an Gitea-DB backup.

@somera commented on GitHub (Oct 21, 2024): > > I this case I should send only has_actions = false as an json? Right? > > Yes. You only need to set the fields that need to be changed. I have now a script which I run after I added some new mirrors. But for the next release there will be a fix in gitea? Means, when I import new mirror "Actions" will be deactivated by default? > I think these commit status can be removed manually from the database with > > ``` > delete from commit_status where repo_id = (select id from repository where is_mirror = true) > delete from commit_status_summary where repo_id = (select id from repository where is_mirror = true) > ``` Thx. I try this next weekend with an Gitea-DB backup.

GiteaMirror commented 2025-11-02 10:47:09 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Oct 24, 2024):

@lunny is there a fix in the next release that for new mirrors "Actions" will be not activated?

@somera commented on GitHub (Oct 24, 2024): @lunny is there a fix in the next release that for new mirrors "Actions" will be not activated?

GiteaMirror commented 2025-11-02 10:47:09 -06:00

Author

Owner

Copy Link

@lunny commented on GitHub (Oct 25, 2024):

Yes, I think there should be a PR to fix that but there is no ETA

@lunny commented on GitHub (Oct 25, 2024): Yes, I think there should be a PR to fix that but there is no ETA

GiteaMirror commented 2025-11-02 10:47:09 -06:00

Author

Owner

Copy Link

@somera commented on GitHub (Jan 11, 2025):

@lunny looks good for me after update to 1.23.1. Thx.

@somera commented on GitHub (Jan 11, 2025): @lunny looks good for me after update to 1.23.1. Thx.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

release/v1.25

release/v1.24

release/v1.23

release/v1.22

release/v1.21

release/v1.20

release/v1.19

release/v1.18

release/v1.17

release/v1.16

release/v1.15

release/v1.14

release/v1.13

release/v1.12

release/v1.11

release/v1.10

release/v1.9

release/v1.8

v1.25.3

v1.25.2

v1.25.1

v1.25.0

v1.24.7

v1.25.0-rc0

v1.26.0-dev

v1.24.6

v1.24.5

v1.24.4

v1.24.3

v1.24.2

v1.24.1

v1.24.0

v1.23.8

v1.24.0-rc0

v1.25.0-dev

v1.23.7

v1.23.6

v1.23.5

v1.23.4

v1.23.3

v1.23.2

v1.23.1

v1.23.0

v1.23.0-rc0

v1.24.0-dev

v1.22.6

v1.22.5

v1.22.4

v1.22.3

v1.22.2

v1.22.1

v1.22.0

v1.23.0-dev

v1.22.0-rc1

v1.21.11

v1.22.0-rc0

v1.21.10

v1.21.9

v1.21.8

v1.21.7

v1.21.6

v1.21.5

v1.21.4

v1.21.3

v1.21.2

v1.20.6

v1.21.1

v1.21.0

v1.21.0-rc2

v1.21.0-rc1

v1.20.5

v1.22.0-dev

v1.21.0-rc0

v1.20.4

v1.20.3

v1.20.2

v1.20.1

v1.20.0

v1.19.4

v1.21.0-dev

v1.20.0-rc2

v1.20.0-rc1

v1.20.0-rc0

v1.19.3

v1.19.2

v1.19.1

v1.19.0

v1.19.0-rc1

v1.20.0-dev

v1.19.0-rc0

v1.18.5

v1.18.4

v1.18.3

v1.18.2

v1.18.1

v1.18.0

v1.17.4

v1.18.0-rc1

v1.19.0-dev

v1.18.0-rc0

v1.17.3

v1.17.2

v1.17.1

v1.17.0

v1.17.0-rc2

v1.16.9

v1.17.0-rc1

v1.18.0-dev

v1.16.8

v1.16.7

v1.16.6

v1.16.5

v1.16.4

v1.16.3

v1.16.2

v1.16.1

v1.16.0

v1.15.11

v1.17.0-dev

v1.16.0-rc1

v1.15.10

v1.15.9

v1.15.8

v1.15.7

v1.15.6

v1.15.5

v1.15.4

v1.15.3

v1.15.2

v1.15.1

v1.14.7

v1.15.0

v1.15.0-rc3

v1.14.6

v1.15.0-rc2

v1.14.5

v1.16.0-dev

v1.15.0-rc1

v1.14.4

v1.14.3

v1.14.2

v1.14.1

v1.14.0

v1.13.7

v1.14.0-rc2

v1.13.6

v1.13.5

v1.14.0-rc1

v1.15.0-dev

v1.13.4

v1.13.3

v1.13.2

v1.13.1

v1.13.0

v1.12.6

v1.13.0-rc2

v1.14.0-dev

v1.13.0-rc1

v1.12.5

v1.12.4

v1.12.3

v1.12.2

v1.12.1

v1.11.8

v1.12.0

v1.11.7

v1.12.0-rc2

v1.11.6

v1.12.0-rc1

v1.13.0-dev

v1.11.5

v1.11.4

v1.11.3

v1.10.6

v1.12.0-dev

v1.11.2

v1.10.5

v1.11.1

v1.10.4

v1.11.0

v1.11.0-rc2

v1.10.3

v1.11.0-rc1

v1.10.2

v1.10.1

v1.10.0

v1.9.6

v1.9.5

v1.10.0-rc2

v1.11.0-dev

v1.10.0-rc1

v1.9.4

v1.9.3

v1.9.2

v1.9.1

v1.9.0

v1.9.0-rc2

v1.10.0-dev

v1.9.0-rc1

v1.8.3

v1.8.2

v1.8.1

v1.8.0

v1.8.0-rc3

v1.7.6

v1.8.0-rc2

v1.7.5

v1.8.0-rc1

v1.9.0-dev

v1.7.4

v1.7.3

v1.7.2

v1.7.1

v1.7.0

v1.7.0-rc3

v1.6.4

v1.7.0-rc2

v1.6.3

v1.7.0-rc1

v1.7.0-dev

v1.6.2

v1.6.1

v1.6.0

v1.6.0-rc2

v1.5.3

v1.6.0-rc1

v1.6.0-dev

v1.5.2

v1.5.1

v1.5.0

v1.5.0-rc2

v1.5.0-rc1

v1.5.0-dev

v1.4.3

v1.4.2

v1.4.1

v1.4.0

v1.4.0-rc3

v1.4.0-rc2

v1.3.3

v1.4.0-rc1

v1.3.2

v1.3.1

v1.3.0

v1.3.0-rc2

v1.3.0-rc1

v1.2.3

v1.2.2

v1.2.1

v1.2.0

v1.2.0-rc3

v1.2.0-rc2

v1.1.4

v1.2.0-rc1

v1.1.3

v1.1.2

v1.1.1

v1.1.0

v1.0.2

v1.0.1

v1.0.0

v0.9.99

Labels

Clear labels

$20

$250

$50

$500

backport/done

💎 Bounty

docs-update-needed

good first issue

hacktoberfest

issue/bounty

issue/confirmed

issue/critical

issue/duplicate

issue/needs-feedback

issue/not-a-bug

issue/regression

issue/stale

issue/workaround

lgtm/need 2

modifies/api

modifies/translation

outdated/backport/v1.18

outdated/theme/markdown

outdated/theme/timetracker

performance/bigrepo

performance/cpu

performance/memory

performance/speed

pr/breaking

proposal/accepted

proposal/rejected

pr/wip

pull-request

Mirrored from GitHub Pull Request

reviewed/wontfix

💰 Rewarded

skip-changelog

status/blocked

topic/accessibility

topic/api

topic/authentication

topic/build

topic/code-linting

topic/commit-signing

topic/content-rendering

topic/deployment

topic/distribution

topic/federation

topic/gitea-actions

topic/issues

topic/lfs

topic/mobile

topic/moderation

topic/packages

topic/pr

topic/projects

topic/repo

topic/repo-migration

topic/security

topic/theme

topic/ui

topic/ui-interaction

topic/ux

topic/webhooks

topic/wiki

type/bug

type/deprecation

type/docs

type/enhancement

type/feature

type/miscellaneous

type/proposal

type/question

type/refactoring

type/summary

type/testing

type/upstream

No Label issue/workaround topic/gitea-actions type/bug

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

GiteaMirror ninjasurge

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#13585