[API_PARSER][REACHFIVE] Store access token & avoid too many request or too large … · VultureProject/vulture-gui@33b8231

Triggered via pull request September 26, 2024 09:23

nlancon

synchronize #449

fix_reachfive

Status Failure

Total duration 25s

Artifacts –

ruff.yml

on: pull_request

6 errors and 1 warning

Ruff (E741): vulture_os/services/frontend/models.py#L1372

vulture_os/services/frontend/models.py:1372:21: E741 Ambiguous variable name: `l`

Ruff (E711): vulture_os/services/frontend/models.py#L1416

vulture_os/services/frontend/models.py:1416:59: E711 Comparison to `None` should be `cond is None`

Ruff (E741): vulture_os/services/frontend/models.py#L1438

vulture_os/services/frontend/models.py:1438:42: E741 Ambiguous variable name: `l`

Ruff (E741): vulture_os/services/frontend/models.py#L1440

vulture_os/services/frontend/models.py:1440:38: E741 Ambiguous variable name: `l`

Ruff (E722): vulture_os/services/frontend/models.py#L2155

vulture_os/services/frontend/models.py:2155:13: E722 Do not use bare `except`

Ruff (E741): vulture_os/toolkit/api_parser/reachfive/reachfive.py#L180

vulture_os/toolkit/api_parser/reachfive/reachfive.py:180:51: E741 Ambiguous variable name: `l`

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/