Skip to content

feat: method waiting for long running operation #669

feat: method waiting for long running operation

feat: method waiting for long running operation #669

Triggered via pull request April 11, 2024 18:36
Status Success
Total duration 8m 52s
Artifacts

main.yml

on: pull_request
Find vulnerabilities
8s
Find vulnerabilities
Matrix: build
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

40 warnings
Build, lint, and test on Node 20 and ubuntu-latest: examples/integration-scripts/challenge.test.ts#L66
'rpyResult1' is never reassigned. Use 'const' instead
Build, lint, and test on Node 20 and ubuntu-latest: examples/integration-scripts/challenge.test.ts#L84
'rpyResult2' is never reassigned. Use 'const' instead
Build, lint, and test on Node 18 and ubuntu-latest: examples/integration-scripts/challenge.test.ts#L66
'rpyResult1' is never reassigned. Use 'const' instead
Build, lint, and test on Node 18 and ubuntu-latest: examples/integration-scripts/challenge.test.ts#L84
'rpyResult2' is never reassigned. Use 'const' instead
Build, lint, and test on Node 18 and macOS-latest: examples/integration-scripts/challenge.test.ts#L66
'rpyResult1' is never reassigned. Use 'const' instead
Build, lint, and test on Node 18 and macOS-latest: examples/integration-scripts/challenge.test.ts#L84
'rpyResult2' is never reassigned. Use 'const' instead
Build, lint, and test on Node 20 and macOS-latest: examples/integration-scripts/challenge.test.ts#L66
'rpyResult1' is never reassigned. Use 'const' instead
Build, lint, and test on Node 20 and macOS-latest: examples/integration-scripts/challenge.test.ts#L84
'rpyResult2' is never reassigned. Use 'const' instead