Skip to content

fix by using Oak knowledge and altering the config for the dotlambda … #245

fix by using Oak knowledge and altering the config for the dotlambda …

fix by using Oak knowledge and altering the config for the dotlambda … #245

Triggered via push May 25, 2024 10:28
Status Success
Total duration 7m 2s
Artifacts

main.yml

on: push
build-devcontainer
3m 22s
build-devcontainer
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 7 warnings
build-devcontainer
imageName is required to push images
build (windows-latest)
Process completed with exit code 1.
build (macOS-latest): src/Fantomas.Core/ASTTransformer.fs#L384
Failed to inline the value 'getLambdaBodyExpr' marked 'inline', perhaps because a recursive value was marked 'inline'
build (macOS-latest): src/Fantomas.Core/ASTTransformer.fs#L384
Failed to inline the value 'getLambdaBodyExpr' marked 'inline', perhaps because a recursive value was marked 'inline'
build (ubuntu-latest)
Uploading multiple SARIF runs with the same category is deprecated and will be removed on June 4, 2025. Please update your workflow to upload a single run per category. For more information, see https://github.blog/changelog/2024-05-06-code-scanning-will-stop-combining-runs-from-a-single-upload
build (ubuntu-latest): src/Fantomas.Core/ASTTransformer.fs#L384
Failed to inline the value 'getLambdaBodyExpr' marked 'inline', perhaps because a recursive value was marked 'inline'
build (ubuntu-latest): src/Fantomas.Core/ASTTransformer.fs#L384
Failed to inline the value 'getLambdaBodyExpr' marked 'inline', perhaps because a recursive value was marked 'inline'
build (ubuntu-latest): src/Fantomas.Core/ASTTransformer.fs#L384
Failed to inline the value 'getLambdaBodyExpr' marked 'inline', perhaps because a recursive value was marked 'inline'
build (ubuntu-latest): src/Fantomas.Core/ASTTransformer.fs#L384
Failed to inline the value 'getLambdaBodyExpr' marked 'inline', perhaps because a recursive value was marked 'inline'