Skip to content
CodeQL

Add parent trace context information when scheduling an orchestration #136

Sign in to view logs

Add parent trace context information when scheduling an orchestration

Add parent trace context information when scheduling an orchestration #136

Triggered via pull request January 30, 2025 20:26
@bachuvbachuv
synchronize #358
vabachu/add-trace-context
Status Failure
Total duration 10m 32s
Artifacts –

codeQL.yml

on: pull_request
Matrix: Analyze
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 1 warning
Analyze (csharp): src/Client/Grpc/GrpcDurableTaskClient.cs#L87
'CreateInstanceRequest' does not contain a definition for 'ParentTraceContext'
Analyze (csharp): src/Client/Grpc/GrpcDurableTaskClient.cs#L87
'CreateInstanceRequest' does not contain a definition for 'ParentTraceContext'
Analyze (csharp): src/Client/Grpc/GrpcDurableTaskClient.cs#L87
'CreateInstanceRequest' does not contain a definition for 'ParentTraceContext'
Analyze (csharp): src/Client/Grpc/GrpcDurableTaskClient.cs#L87
'CreateInstanceRequest' does not contain a definition for 'ParentTraceContext'
Analyze (csharp)
Process completed with exit code 1.
Analyze (csharp)
Unable to validate code scanning workflow: error: getWorkflow() failed: Error: Expected to find a code scanning workflow file at D:\a\durabletask-dotnet\durabletask-dotnet\.github\workflows\codeQL.yml, but no such file existed. This can happen if the currently running workflow checks out a branch that doesn't contain the corresponding workflow file.