Add infraction type enum for granular punishment #138
therefAnnotations
4 errors and 11 warnings
|
linting:
contracts/contracts/coordination/InfractionCollector.sol#L44
Replace !infractions[ritualId][stakingProviders[i]][InfractionType.MISSING_TRANSCRIPT],·"Infraction·already·reported" with ⏎················!infractions[ritualId][stakingProviders[i]][InfractionType.MISSING_TRANSCRIPT],⏎················"Infraction·already·reported"⏎············
|
|
linting:
contracts/contracts/coordination/InfractionCollector.sol#L49
Insert ⏎··············
|
|
linting:
contracts/contracts/coordination/InfractionCollector.sol#L52
Replace InfractionType.MISSING_TRANSCRIPT with ⏎····················InfractionType.MISSING_TRANSCRIPT⏎················
|
|
linting
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
Use Custom Errors instead of require statements
|
|
linting:
contracts/contracts/Adjudicator.sol#L90
Use Custom Errors instead of require statements
|
|
linting:
contracts/contracts/Adjudicator.sol#L102
Use Custom Errors instead of require statements
|
|
linting:
contracts/contracts/Adjudicator.sol#L106
Use Custom Errors instead of require statements
|
|
linting:
contracts/contracts/Adjudicator.sol#L114
Use Custom Errors instead of require statements
|
|
tests
The following actions uses Node.js version which is deprecated 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/
|