Skip to content

Fix if statement sequence points and SequencePointInserter #3179

Fix if statement sequence points and SequencePointInserter

Fix if statement sequence points and SequencePointInserter #3179

Triggered via pull request February 22, 2024 19:25
Status Success
Total duration 3m 0s
Artifacts

main.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

21 warnings
Test
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: coverallsapp/github-action@master. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Test: neo/src/Neo/ProtocolSettings.cs#L121
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Test: neo/src/Neo/NeoSystem.cs#L118
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Test: neo/src/Neo/NeoSystem.cs#L118
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Test: tests/Neo.SmartContract.Framework.TestContracts/Contract_ExtraAttribute.cs#L9
'Contract_ExtraAttribute.Main(string, object[])' has the wrong signature to be an entry point
Test: tests/Neo.SmartContract.Framework.TestContracts/Contract_SupportedStandard17Enum.cs#L16
Non-nullable property 'Symbol' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Test: tests/Neo.SmartContract.Framework.TestContracts/Contract_SupportedStandard11Enum.cs#L13
Non-nullable property 'Symbol' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
Test: neo/src/Neo/NeoSystem.cs#L118
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Test: neo/src/Neo/NeoSystem.cs#L118
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Test: neo/src/Neo/ProtocolSettings.cs#L121
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Test: src/Neo.SmartContract.Testing/Coverage/AbiMethod.cs#L94
Nullability of reference types in type of parameter 'other' doesn't match implemented member 'bool IEquatable<AbiMethod>.Equals(AbiMethod? other)' (possibly because of nullability attributes).
Test: src/Neo.SmartContract.Testing/Coverage/AbiMethod.cs#L87
Nullability of type of parameter 'obj' doesn't match overridden member (possibly because of nullability attributes).
Test: src/Neo.SmartContract.Testing/Coverage/NeoDebugInfo.cs#L58
Possible null reference argument for parameter 'path1' in 'string Path.Combine(string path1, string path2)'.
Test: src/Neo.SmartContract.Testing/Extensions/TestExtensions.cs#L195
Possible null reference return.
Test: src/Neo.SmartContract.Testing/Coverage/CoverageHit.cs#L179
Possible null reference argument for parameter 'input' in 'bool Regex.IsMatch(string input, string pattern)'.
Test: src/Neo.SmartContract.Testing/Native/ContractManagement.cs#L22
The event 'ContractManagement.OnUpdate' is never used
Test: src/Neo.SmartContract.Testing/Native/NeoToken.cs#L30
The event 'NeoToken.OnCandidateStateChanged' is never used