fix: Context::Global() need Context::Scope #1416
david-clangcode_linter.yml
on: push
Cppcheck
1m 17s
Find merge conflicts
12s
reformat-bridge
34s
Annotations
2 errors and 5 warnings
|
Find merge conflicts:
bridge/third_party/v8/lib/macos/arm64/libv8.dylib#L1
Merge conflict found in ./bridge/third_party/v8/lib/macos/arm64/libv8.dylib
|
|
Cppcheck
Process completed with exit code 1.
|
|
Find merge conflicts
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
reformat-bridge
The following actions uses node12 which is deprecated and will be forced to run on node16: EndBug/add-and-commit@v4. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
reformat-bridge
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, EndBug/add-and-commit@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Cppcheck
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Cppcheck
You are using macOS 12.
We (and Apple) do not provide support for this old version.
It is expected behaviour that some formulae will fail to build in this old version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.
|