Skip to content
CodeQL

chore: define AST tree for the query model INTELLIJ-18 #134

Sign in to view logs

chore: define AST tree for the query model INTELLIJ-18

chore: define AST tree for the query model INTELLIJ-18 #134

Triggered via pull request July 1, 2024 17:30
@kmruizkmruiz
synchronize #13
chore/intellij-18
Status Success
Total duration 9m 44s
Artifacts –

codeql.yml

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

Annotations

6 errors
NewConnectionActivatedProbeTestForAtlasCliEnvironment.should get proper build information of the server(Application, Project, MongoDbServerUrl): NewConnectionActivatedProbeTestForAtlasCliEnvironment#L1
Argument(s) are different! Wanted: telemetryService.sendEvent( <custom argument matcher> ); -> at com.mongodb.jbplugin.observability.TelemetryService.sendEvent(TelemetryService.kt:38) Actual invocations have different arguments: telemetryService.sendEvent( com.mongodb.jbplugin.observability.TelemetryEvent$NewConnection@74b97416 ); -> at com.mongodb.jbplugin.observability.probe.NewConnectionActivatedProbe.connected(NewConnectionActivatedProbe.kt:64)
NewConnectionActivatedProbeTestForLocalEnvironment.should get proper build information of the server(Application, Project, MongoDbServerUrl): NewConnectionActivatedProbeTestForLocalEnvironment#L1
Argument(s) are different! Wanted: telemetryService.sendEvent( <custom argument matcher> ); -> at com.mongodb.jbplugin.observability.TelemetryService.sendEvent(TelemetryService.kt:38) Actual invocations have different arguments: telemetryService.sendEvent( com.mongodb.jbplugin.observability.TelemetryEvent$NewConnection@63553e9f ); -> at com.mongodb.jbplugin.observability.probe.NewConnectionActivatedProbe.connected(NewConnectionActivatedProbe.kt:64)
NewConnectionActivatedProbeTestForAtlasCliEnvironment.should get proper build information of the server(Application, Project, MongoDbServerUrl): NewConnectionActivatedProbeTestForAtlasCliEnvironment#L1
Argument(s) are different! Wanted: telemetryService.sendEvent( <custom argument matcher> ); -> at com.mongodb.jbplugin.observability.TelemetryService.sendEvent(TelemetryService.kt:38) Actual invocations have different arguments: telemetryService.sendEvent( com.mongodb.jbplugin.observability.TelemetryEvent$NewConnection@30c7be6f ); -> at com.mongodb.jbplugin.observability.probe.NewConnectionActivatedProbe.connected(NewConnectionActivatedProbe.kt:64)
NewConnectionActivatedProbeTestForLocalEnvironment.should get proper build information of the server(Application, Project, MongoDbServerUrl): NewConnectionActivatedProbeTestForLocalEnvironment#L1
Argument(s) are different! Wanted: telemetryService.sendEvent( <custom argument matcher> ); -> at com.mongodb.jbplugin.observability.TelemetryService.sendEvent(TelemetryService.kt:38) Actual invocations have different arguments: telemetryService.sendEvent( com.mongodb.jbplugin.observability.TelemetryEvent$NewConnection@14485747 ); -> at com.mongodb.jbplugin.observability.probe.NewConnectionActivatedProbe.connected(NewConnectionActivatedProbe.kt:64)
NewConnectionActivatedProbeTestForAtlasCliEnvironment.should get proper build information of the server(Application, Project, MongoDbServerUrl): NewConnectionActivatedProbeTestForAtlasCliEnvironment#L1
Argument(s) are different! Wanted: telemetryService.sendEvent( <custom argument matcher> ); -> at com.mongodb.jbplugin.observability.TelemetryService.sendEvent(TelemetryService.kt:38) Actual invocations have different arguments: telemetryService.sendEvent( com.mongodb.jbplugin.observability.TelemetryEvent$NewConnection@46702c26 ); -> at com.mongodb.jbplugin.observability.probe.NewConnectionActivatedProbe.connected(NewConnectionActivatedProbe.kt:64)
NewConnectionActivatedProbeTestForLocalEnvironment.should get proper build information of the server(Application, Project, MongoDbServerUrl): NewConnectionActivatedProbeTestForLocalEnvironment#L1
Argument(s) are different! Wanted: telemetryService.sendEvent( <custom argument matcher> ); -> at com.mongodb.jbplugin.observability.TelemetryService.sendEvent(TelemetryService.kt:38) Actual invocations have different arguments: telemetryService.sendEvent( com.mongodb.jbplugin.observability.TelemetryEvent$NewConnection@38022758 ); -> at com.mongodb.jbplugin.observability.probe.NewConnectionActivatedProbe.connected(NewConnectionActivatedProbe.kt:64)