6543 a63135363b Step status update dont set to running again once it got stoped (#3151) ... Because of the check `if step.Stopped == 0` without the check there are edgecases where could be the case a stoped steped can be markt as running again, witch is wrong. I do remember we have "running" steps indefinetly in cancled pipelines. This could be the fix, i just did not test that specific. Anyway the func hat a good testcoverage ... so just look at the tests _Source: https://github.com/woodpecker-ci/woodpecker/pull/3143#discussion_r1446138088_		2024-01-09 18:34:55 +01:00
..
auth_server.go	Update go module path for major version 2 (#2905)	2023-12-08 08:15:08 +01:00
authorizer.go	Replace interface{} with any (#2807)	2023-11-12 18:23:48 +01:00
filter.go	Update go module path for major version 2 (#2905)	2023-12-08 08:15:08 +01:00
filter_test.go	Update go module path for major version 2 (#2905)	2023-12-08 08:15:08 +01:00
jwt_manager.go	Replace interface{} with any (#2807)	2023-11-12 18:23:48 +01:00
rpc.go	Step status update dont set to running again once it got stoped (#3151)	2024-01-09 18:34:55 +01:00
rpc_test.go	Register Agent with hostname (#2936)	2023-12-19 14:17:36 +01:00
server.go	Use step uuid instead of name in GRPC status calls (#3143)	2024-01-09 15:39:09 +01:00