Skip to content
Back to pull request #32680

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

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 #24581

Triggered via pull request November 30, 2024 04:39
@lunnylunny
synchronize #32680
lunny:lunny/pull_requests_api
Status Success
Total duration 7m 16s
Artifacts –

pull-compliance.yml

on: pull_request
files-changed  /  detect
5s
files-changed / detect
lint-backend
6m 11s
lint-backend
lint-templates
0s
lint-templates
lint-yaml
0s
lint-yaml
lint-swagger
0s
lint-swagger
lint-spell
20s
lint-spell
lint-go-windows
6m 11s
lint-go-windows
lint-go-gogit
5m 35s
lint-go-gogit
checks-backend
3m 4s
checks-backend
frontend
0s
frontend
backend
6m 53s
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-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
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