feat(esp32_p4_function_ev_board): add example of wifi connection #1643
igrrAnnotations
3 warnings
|
pre-commit
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, pre-commit/action@v2.0.3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
pre-commit
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, pre-commit/action@v2.0.3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
pre-commit
There was an error saving the pre-commit environments to cache:
reserveCache failed: Cache already exists. Scope: refs/pull/407/merge, Key: pre-commit-2-1da095071aaf155159d1b0a5139bdcc8310a68b20ed5247792adc76821771c4a-1d6bcb82bbdce7dfb9ee51697912f9f4c381440b7ab8bf198d084fc9c0229ada, Version: 25d34710bdd63bed70a22b8204c3e1d0942dc237e098600e3896b4334c6d784f
This only has performance implications and won't change the result of your pre-commit tests.
If this problem persists on your default branch, you can try to fix it by editing your '.pre-commit-config.yaml'.
For example try to run 'pre-commit autoupdate' or simply add a blank line.
This will result in a different hash value and thus a different cache target.
|