search

go-gitea / gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
https://gitea.com
MIT License
45.08k stars 5.49k forks source link

[Actions] - Empty Workflow or deleted workflow would stay in open status on the UI. #24773

Closed saraiva82 closed 6 months ago

saraiva82 commented 1 year ago

Description

If an empty workflow file is created and actions are triggered by another workflow, that empty action will show as open and running forever in the web ui. I checked if it was running in docker and it was not. I tried hitting stop on the UI and it does not work. I tried deleting the empty workflow and when my other workflow was triggered with a push, the deleted empty action triggered again and remains open. Again no docker action running in the backend. I then created the file again and populated with some job/steps and even though it ran properly, it did not remove these ghost action in the UI. Restarting gitea did not do the trick either.

I honestly did not try the demo site as there is a 3 hour wait time to activate my registration. I'll try later and update this

Gitea Version

1.19.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

image

Git Version

No response

Operating System

Running on Docker

How are you running Gitea?

Docker-compose with AWS RDS Postgres instance for the database

Database

PostgreSQL

wolfogre commented 1 year ago

If an empty workflow file is created and actions are triggered by another workflow,

Could you please show us your workflow file? It's just a empty file?

And please take a screenshot of the task detail page.

saraiva82 commented 1 year ago

Yes the workflow file was empty like build.yml but no contents inside.

saraiva82 commented 1 year ago

image What you see on the ever-running action are the workflows that had content inside them. but when this was committed that was another workflow file added to the directory which led to this ever-running state. I then added content to that file to see if it would clear and it did not. it just runs the workflow normally. My last attempt was to delete the file altogether and that lead to a second-ever running open action. This seems to only affect the Actions UI and not the actual backend of it.

Zettat123 commented 1 year ago

Hi @saraiva82 , I can't reproduce this issue. Could you please provide detailed steps to help us reproduce it?

yp05327 commented 7 months ago

If I understand clearly, the root reason is that an empty workflow file should not be triggered, but it was? Then you can not stop it or delete it. If it is, empty workflow will not be triggered in the latest version, so I think this issue has been fixed. Can you upgrade to the latest version, and check it again?

GiteaBot commented 6 months ago

We close issues that need feedback from the author if there were no new comments for a month. :tea: