Skip to content

Changing Sentry init options. #944

Changing Sentry init options.

Changing Sentry init options. #944

Triggered via push October 20, 2024 17:20
Status Failure
Total duration 2m 42s
Artifacts
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 8 warnings
build
Process completed with exit code 1.
build
Process completed with exit code 1.
build
Error: An API error occurred: channel_not_found
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, docker/login-action@v2, voxmedia/github-action-slack-notify-build@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build: ServiceItemsPlanningPlugin/Core.cs#L150
The variable 'pattern' is assigned but its value is never used
build: ServiceItemsPlanningPlugin/Core.cs#L150
The variable 'pattern' is assigned but its value is never used
build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
build
The variable 'ex' is declared but never used
build
Field 'ServiceLogic._eventHandlers' is never assigned to, and will always have its default value null
build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
build
The variable 'pattern' is assigned but its value is never used