[SDK-3770] Fix logging issue across multiple rest/realtime/push instances #133
sacOO7Annotations
10 errors and 11 warnings
|
check
'ConnectionInitializedState' does not contain a constructor that takes 2 arguments
|
|
check
'ConnectionConnectedState' does not contain a constructor that takes 4 arguments
|
|
check
'ConnectionInitializedState' does not contain a constructor that takes 2 arguments
|
|
check
'ConnectionFailedState' does not contain a constructor that takes 3 arguments
|
|
check
'ConnectionClosedState' does not contain a constructor that takes 3 arguments
|
|
check
'ConnectionInitializedState' does not contain a constructor that takes 2 arguments
|
|
check
'ConnectionConnectedState' does not contain a constructor that takes 4 arguments
|
|
check
'ConnectionInitializedState' does not contain a constructor that takes 2 arguments
|
|
check
'ConnectionFailedState' does not contain a constructor that takes 3 arguments
|
|
check
'ConnectionClosedState' does not contain a constructor that takes 3 arguments
|
|
check
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
check
Expected 'disable' or 'restore'
|
|
check
Expected 'disable' or 'restore'
|
|
check
'ClientOptions.CaptureCurrentSynchronizationContext' is obsolete: 'Use CustomContext property instead, CaptureCurrentSynchronizationContext property will be removed in future versions'
|
|
check
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
check
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
check
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
check
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
check
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
check
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
check
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|