yume-runner/runtime
Zettat123 1596e4b1fd Fix potential log panic (#82)
If a job uses a [reusable workflow](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-of-jobsjob_iduses), the job's steps sequence will be empty.

But in log reporter, we don't check the length of `r.state.Steps`, which may cause panic.

``` go
if v, ok := entry.Data["stepNumber"]; ok {
	if v, ok := v.(int); ok {
		step = r.state.Steps[v]
	}
}
```

Reviewed-on: https://gitea.com/gitea/act_runner/pulls/82
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: Zettat123 <zettat123@gmail.com>
Co-committed-by: Zettat123 <zettat123@gmail.com>
2023-03-28 11:49:09 +08:00
..
label.go Clarify labels (#69) 2023-03-23 20:48:33 +08:00
label_test.go Vet code (#73) 2023-03-24 15:10:39 +08:00
reporter.go Fix potential log panic (#82) 2023-03-28 11:49:09 +08:00
runtime.go Get outbound IP in multiple ways or disable cache server if failed to init (#74) 2023-03-24 17:55:13 +08:00
task.go Fix failed to create container if the runner works in root dir (#67) 2023-03-23 09:41:22 +08:00