Fix: Incorrect user joining room logic #5
dotnet.yml
on: push
build-linux
19s
build-windows
58s
Annotations
25 warnings
build-linux
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
build-linux:
ConnectionMessage.cs#L165
'ConnectionMessage.Client.NewRoom.action' hides inherited member 'ConnectionMessage.Message.action'. Use the new keyword if hiding was intended.
|
build-linux:
ConnectionMessage.cs#L197
Cannot convert null literal to non-nullable reference type.
|
build-linux:
ConnectionMessage.cs#L223
'ConnectionMessage.Client.JoinRoom.action' hides inherited member 'ConnectionMessage.Message.action'. Use the new keyword if hiding was intended.
|
build-linux:
ConnectionMessage.cs#L241
'ConnectionMessage.Client.LeaveRoom.action' hides inherited member 'ConnectionMessage.Message.action'. Use the new keyword if hiding was intended.
|
build-linux:
ConnectionMessage.cs#L175
Non-nullable field '_roomID' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
build-linux:
ConnectionMessage.cs#L143
Cannot convert null literal to non-nullable reference type.
|
build-linux:
ConnectionMessage.cs#L144
Cannot convert null literal to non-nullable reference type.
|
build-linux:
Program.cs#L235
The result of the expression is always 'false' since a value of type 'bool' is never equal to 'null' of type 'bool?'
|
build-linux:
Program.cs#L234
The result of the expression is always 'false' since a value of type 'bool' is never equal to 'null' of type 'bool?'
|
build-linux:
Program.cs#L369
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.
|
build-linux
No files were found with the provided path: test-results. No artifacts will be uploaded.
|
build-windows
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
build-windows:
ConnectionMessage.cs#L165
'ConnectionMessage.Client.NewRoom.action' hides inherited member 'ConnectionMessage.Message.action'. Use the new keyword if hiding was intended.
|
build-windows:
ConnectionMessage.cs#L197
Cannot convert null literal to non-nullable reference type.
|
build-windows:
ConnectionMessage.cs#L223
'ConnectionMessage.Client.JoinRoom.action' hides inherited member 'ConnectionMessage.Message.action'. Use the new keyword if hiding was intended.
|
build-windows:
ConnectionMessage.cs#L241
'ConnectionMessage.Client.LeaveRoom.action' hides inherited member 'ConnectionMessage.Message.action'. Use the new keyword if hiding was intended.
|
build-windows:
ConnectionMessage.cs#L175
Non-nullable field '_roomID' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
build-windows:
ConnectionMessage.cs#L143
Cannot convert null literal to non-nullable reference type.
|
build-windows:
ConnectionMessage.cs#L144
Cannot convert null literal to non-nullable reference type.
|
build-windows:
Program.cs#L235
The result of the expression is always 'false' since a value of type 'bool' is never equal to 'null' of type 'bool?'
|
build-windows:
Program.cs#L234
The result of the expression is always 'false' since a value of type 'bool' is never equal to 'null' of type 'bool?'
|
build-windows:
Program.cs#L369
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.
|
build-windows
No files were found with the provided path: test-results. No artifacts will be uploaded.
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "build-artifacts-linux", "build-artifacts-windows".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
build-artifacts-linux
|
863 KB |
|
build-artifacts-windows
|
928 KB |
|