Skip to content

Encalve Spec

Encalve Spec #14

Triggered via pull request June 4, 2024 10:45
@cristovaothcristovaoth
synchronize #1
draft-spec
Status Failure
Total duration 33s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 12 warnings
ci
Line length must be no more than 120 but current length is 263
ci
Line length must be no more than 120 but current length is 121
ci
Line length must be no more than 120 but current length is 143
ci
Line length must be no more than 120 but current length is 148
ci
Line length must be no more than 120 but current length is 174
ci
Line length must be no more than 120 but current length is 205
ci
Line length must be no more than 120 but current length is 126
ci
Line length must be no more than 120 but current length is 138
ci
Line length must be no more than 120 but current length is 139
ci
Line length must be no more than 120 but current length is 151
ci
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
ci
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-node@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
ci
Main key parameter in mapping computationModules is not named
ci
Main key parameter in mapping executionModules is not named
ci
Value parameter in mapping e3s is not named
ci
GC: Use Custom Errors instead of require statements
ci
GC: Use Custom Errors instead of require statements
ci
GC: Use Custom Errors instead of require statements
ci
GC: Use Custom Errors instead of require statements
ci
GC: Use Custom Errors instead of require statements
ci
GC: Use Custom Errors instead of require statements
ci
GC: Use Custom Errors instead of require statements