Skip to content

feat: 🚀 Add unity playback #49

feat: 🚀 Add unity playback

feat: 🚀 Add unity playback #49

Triggered via pull request May 11, 2024 15:19
@DragonAuraDragonAura
synchronize #365
Cyh28:dev
Status Failure
Total duration 4m 32s
Artifacts

deploy.yml

on: pull_request
deploy-to-tencent-cos
4m 20s
deploy-to-tencent-cos
Fit to window
Zoom out
Zoom in

Annotations

1 error and 23 warnings
deploy-to-tencent-cos
Process completed with exit code 1.
deploy-to-tencent-cos: logic/Preparation/Utility/Value/SafeValue/SafeMethod/InterlockedEx.cs#L73
Converting null literal or possible null value to non-nullable type.
deploy-to-tencent-cos: logic/Preparation/Utility/Value/SafeValue/SafeMethod/InterlockedEx.cs#L48
Possible null reference argument for parameter 'meth' in 'void ILGenerator.Emit(OpCode opcode, MethodInfo meth)'.
deploy-to-tencent-cos: logic/Preparation/Utility/Value/SafeValue/SafeMethod/InterlockedEx.cs#L23
Possible null reference argument for parameter 'meth' in 'void ILGenerator.Emit(OpCode opcode, MethodInfo meth)'.
deploy-to-tencent-cos: logic/Server/GameServer.cs#L18
Non-nullable field 'status' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
deploy-to-tencent-cos: logic/Server/GameServer.cs#L19
Non-nullable field 'scores' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
deploy-to-tencent-cos: logic/Server/HttpSender.cs#L62
Dereference of a possibly null reference.
deploy-to-tencent-cos: logic/Preparation/Utility/Value/SafeValue/SafeMethod/InterlockedEx.cs#L73
Converting null literal or possible null value to non-nullable type.
deploy-to-tencent-cos: logic/Preparation/Utility/Value/SafeValue/SafeMethod/InterlockedEx.cs#L48
Possible null reference argument for parameter 'meth' in 'void ILGenerator.Emit(OpCode opcode, MethodInfo meth)'.
deploy-to-tencent-cos: logic/Preparation/Utility/Value/SafeValue/SafeMethod/InterlockedEx.cs#L23
Possible null reference argument for parameter 'meth' in 'void ILGenerator.Emit(OpCode opcode, MethodInfo meth)'.
deploy-to-tencent-cos: logic/Server/GameServer.cs#L18
Non-nullable field 'status' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
deploy-to-tencent-cos: installer/Data/ConfigFileData.cs#L12
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
deploy-to-tencent-cos: installer/Data/ConfigFileData.cs#L34
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
deploy-to-tencent-cos: installer/Data/ConfigFileData.cs#L133
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
deploy-to-tencent-cos: installer/Data/ConfigFileData.cs#L134
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
deploy-to-tencent-cos: installer/Data/ConfigFileData.cs#L135
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
deploy-to-tencent-cos: installer/Data/ConfigFileData.cs#L136
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
deploy-to-tencent-cos: installer/Data/ConfigFileData.cs#L144
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
deploy-to-tencent-cos: installer/Data/ConfigFileData.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
deploy-to-tencent-cos: installer/Data/ConfigFileData.cs#L143
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
deploy-to-tencent-cos: installer/Data/ConfigFileData.cs#L351
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
deploy-to-tencent-cos: installer/Model/EEsast.cs#L195
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.
deploy-to-tencent-cos: installer/Model/Logger.cs#L343
The field 'ListLogger.time' is never used
deploy-to-tencent-cos: installer/Data/ConfigFileData.cs#L352
The event 'ConfigData.OnFileChanged' is never used