Skip to content

InfractionCollector Contract #1186

InfractionCollector Contract

InfractionCollector Contract #1186

Triggered via pull request August 20, 2024 12:43
Status Failure
Total duration 7m 20s
Artifacts

main.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 11 warnings
linting: contracts/contracts/coordination/InfractionCollector.sol#L27
Replace ⏎············address(_coordinator)·!=·address(0),⏎············"Contracts·must·be·specified"⏎········ with address(_coordinator)·!=·address(0),·"Contracts·must·be·specified"
linting: contracts/contracts/coordination/InfractionCollector.sol#L53
Replace InfractionType.MISSING_TRANSCRIPT with ⏎····················InfractionType.MISSING_TRANSCRIPT⏎················
linting
Process completed with exit code 1.
tests
Process completed with exit code 1.
linting: contracts/contracts/Adjudicator.sol#L31
Function order is incorrect, state variable declaration can not go after event definition (line 25)
linting: contracts/contracts/Adjudicator.sol#L37
Main key parameter in mapping penaltyHistory is not named
linting: contracts/contracts/Adjudicator.sol#L37
Value parameter in mapping penaltyHistory is not named
linting: contracts/contracts/Adjudicator.sol#L38
Main key parameter in mapping evaluatedCFrags is not named
linting: contracts/contracts/Adjudicator.sol#L38
Value parameter in mapping evaluatedCFrags is not named
linting: contracts/contracts/Adjudicator.sol#L53
GC: Use Custom Errors instead of require statements
linting: contracts/contracts/Adjudicator.sol#L90
GC: Use Custom Errors instead of require statements
linting: contracts/contracts/Adjudicator.sol#L102
GC: Use Custom Errors instead of require statements
linting: contracts/contracts/Adjudicator.sol#L106
GC: Use Custom Errors instead of require statements
linting: contracts/contracts/Adjudicator.sol#L114
GC: Use Custom Errors instead of require statements
tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/