Skip to content
compliance

Use batch database operations instead of one by one to optimze api pulls #24580

Sign in to view logs

Use batch database operations instead of one by one to optimze api pulls

Use batch database operations instead of one by one to optimze api pulls #24580

Triggered via pull request November 30, 2024 03:13
@lunnylunny
opened #32680
lunny:lunny/pull_requests_api
Status Success
Total duration 7m 25s
Artifacts –

pull-compliance.yml

on: pull_request
files-changed  /  detect
7s
files-changed / detect
lint-backend
6m 7s
lint-backend
lint-templates
0s
lint-templates
lint-yaml
0s
lint-yaml
lint-swagger
0s
lint-swagger
lint-spell
21s
lint-spell
lint-go-windows
6m 10s
lint-go-windows
lint-go-gogit
6m 0s
lint-go-gogit
checks-backend
3m 13s
checks-backend
frontend
0s
frontend
backend
6m 56s
backend
docs
0s
docs
actions
0s
actions
Fit to window
Zoom out
Zoom in

Annotations

4 errors
checks-backend
cannot use debug.SetCrashOutput (value of type func(f *os.File, opts debug.CrashOptions) error) as func(*os.File) error value in assignment
lint-go-gogit
cannot use debug.SetCrashOutput (value of type func(f *os.File, opts debug.CrashOptions) error) as func(*os.File) error value in assignment
lint-backend
cannot use debug.SetCrashOutput (value of type func(f *os.File, opts debug.CrashOptions) error) as func(*os.File) error value in assignment
lint-go-windows
cannot use debug.SetCrashOutput (value of type func(f *os.File, opts debug.CrashOptions) error) as func(*os.File) error value in assignment