Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps, cpp): update matepek.vscode-catch2-test-adapter, ms-vscode.cpptools #610

Merged
merged 1 commit into from
Oct 20, 2024
Merged

chore(deps, cpp): update matepek.vscode-catch2-test-adapter, ms-vscode.cpptools #610

merged 1 commit into from
Oct 20, 2024

Conversation

philips-software-forest-releaser[bot]
Copy link
Contributor

Note

Before merging this PR, please conduct a manual test checking basic functionality of the updated plug-ins. There are limited automated tests for the VS Code Extension updates.

Updates ms-vscode.cpptools from 1.21.6 to 1.22.9

Release notes

Instructions

The extension can be obtained by one of the methods below:

  • Install the "C/C++" or "C/C++ Extension Pack" extension published by Microsoft from the Extensions view in VS Code.
  • Download a vsix that matches your OS from the "Download" dropdown in the "Version History" tab section on the Marketplace website, and then use the Extensions: Install from VSIX... command in VS Code (don't double-click the vsix or another app like VS might try to open it incorrectly).
  • Download a vsix that matches your OS from the Assets section below (and install it via the method mentioned above). The previous download methods have the vsix signatures verified by the Marketplace, but for this method, you can do the verification by downloading the matching manifest and signature.p7s file and running npx @vscode/vsce@latest verify-signature -i <.vsix> -m <.signature.manifest> -s <.signature.p7s> vscode-vsce#1044.

Requirements

  • VS Code 1.67.0 or later (April 2022).
  • Windows 7+ (x64, arm64), macOS 10.12+, Linux (Ubuntu 16+, etc.).

Changes

Performance Improvements

  • Initialization performance improvements. #12030
    • Some processing is parallelized and started earlier (populating the filename cache, discovering files). #11954, #12169
    • Some compiler configuration queries are cached in the database, and processing of compile_commands.json was improved. #10029, #12078
  • Performance improvements related to how custom configurations are processed. #9003, #12632
  • Improve the implementation of file buffers to reduce memory usage.
  • Performance improvements related to LSP request processing.

Enhancements

  • Add modified C_Cpp settings to the C/C++: Log Diagnostics output. #11700
  • Add better validation for settings. #12371
  • Change the default C/C++ "editor.stickyScroll.defaultModel" to "foldingProviderModel". #12483
  • Remove the C_Cpp.intelliSenseEngineFallback setting. #12596
  • Enable C/C++: Log Diagnostics without a C/C++ file being active. #12634
  • Add "Additional Tracked Settings" to the C/C++: Log Diagnostics output. PR #12635
  • Add support for providing additional context information to Copilot Chat. PR #12685
    • Currently, it requires "C_Cpp.experimentalFeatures": "enabled" and typing #cpp in the chat.
  • The .vsix and .js files are now signed. #12725, #12744
  • Add the database path to the C/C++: Log Diagnostics output.
  • Various IntelliSense parsing updates/fixes.

Bug Fixes

  • Fix the compiler selection control not keeping the list in sync with the contents of the textbox. #7427
  • Fix a string localization issue. #7824
  • Fix an issue with the 'Add #include' code action incorrectly using a relative path for a system include. #12010
  • Fix an issue with lingering IntelliSense squiggles after an edit. #12175
  • Fix hover over static constexpr variables sometimes not working. #12284
  • Fix completion not giving results in several scenarios. #12412
  • Stop logging duplicate compiler path messages. #12445
  • Fix an issue where a file is incorrectly processed as C instead of C++. #12466
  • Fix an issue with missing database symbols after a Rename operation. #12480
  • Fix include path ordering being incorrect if there is a duplicate. #12525
  • Fix a WebAssembly "Out of Memory" error. #12529
  • Fix an error message not being shown if the connection failed with remote attach debugging. #12547
  • Fix -I not being used if -iquote is also used for the same path. #12551
  • Fix issues with relative paths on nvcc (CUDA) command lines not being handled correctly. #12553
  • Fix a crash on shutdown on macOS with a verbose logging level. #12567
  • Fix a random crash when a child process is created. #12585
  • Work around IntelliSense issues with clang 18 due to size_t not being defined. #12618
  • Fix the /FU flag not working for C++/CLI. #12641
  • Fix a crash in find_existing_intellisense_client. #12666
  • Fix a rare crash on macOS related to get_memory_usage. #12667
  • Fix an issue with 'Extract to Function' formatting. #12677
  • Fix an issue with duplicate tag parsing occurring after a Rename operation. #12728
  • Fix an issue preventing use of a full command line in compilerPath. PR #12774
  • Fix an issue with clang-format/tidy version checks for some builds. #12806
  • Fix an issue causing unnecessary TU updates for files opened during a Rename operation, when "files.refactoring.autoSave": false is used.
  • Fix some issues with recursive includes handling of symbolic links, multi-root, exclusion changes, and file/folder deletion.
  • Fix unnecessary IntelliSense resetting when a new file or folder was created.
  • Fix an infinite loop on shutdown after changing the selected settings.
  • Fix accumulation of stale signature help and completion requests.
  • Fix handling of the compiler-binddir compiler argument.
  • Fix a random crash during IntelliSense creation.
  • Fix some bugs with include completion.

Updates matepek.vscode-catch2-test-adapter from 4.12.0 to 4.12.1

Release notes

See CHANGELOG.md for details.

@philips-software-forest-releaser philips-software-forest-releaser bot added dependencies Pull requests that update a dependency file vscode-extensions labels Oct 20, 2024
@sonarcloud SonarCloud
Copy link

sonarcloud bot commented Oct 20, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

@github-actions GitHub Actions
Copy link
Contributor

Compressed layer size comparison

Comparing ghcr.io/philips-software/amp-devcontainer-rust:latest to ghcr.io/philips-software/amp-devcontainer-rust@sha256:5e3bffa895defe491628257293d08fba4701565cf3cfca22638ba374422f54f2

OS/Platform Previous Size Current Size Delta
linux/amd64 425.13M 433.00M 7.87M (+1.85%)
linux/arm64 564.77M 572.52M 7.75M (+1.37%)

@github-actions GitHub Actions
Copy link
Contributor

Compressed layer size comparison

Comparing ghcr.io/philips-software/amp-devcontainer-cpp:latest to ghcr.io/philips-software/amp-devcontainer-cpp@sha256:027e8147cf89f7164d7b2ac765f4b09c2869afade45aef36598548936341c34f

OS/Platform Previous Size Current Size Delta
linux/amd64 645.35M 645.35M 0.00 (+0.00%)
linux/arm64 638.06M 638.06M 0.00 (+0.00%)

@github-actions GitHub Actions
Copy link
Contributor

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 16 0 0.08s
✅ DOCKERFILE hadolint 2 0 0.34s
✅ GHERKIN gherkin-lint 2 0 0.5s
✅ JSON npm-package-json-lint yes no 0.42s
✅ JSON prettier 15 2 0 0.67s
✅ JSON v8r 14 0 17.55s
✅ MARKDOWN markdownlint 8 0 0 0.9s
✅ MARKDOWN markdown-table-formatter 8 0 0 0.21s
✅ REPOSITORY checkov yes no 16.15s
✅ REPOSITORY gitleaks yes no 0.29s
✅ REPOSITORY git_diff yes no 0.01s
✅ REPOSITORY grype yes no 14.22s
✅ REPOSITORY secretlint yes no 1.38s
✅ REPOSITORY syft yes no 0.38s
✅ REPOSITORY trivy yes no 5.9s
✅ REPOSITORY trivy-sbom yes no 0.13s
✅ REPOSITORY trufflehog yes no 2.2s
✅ SPELL lychee 54 0 3.99s
✅ YAML prettier 21 0 0 0.97s
✅ YAML v8r 21 0 12.93s
✅ YAML yamllint 21 0 0.41s

See detailed report in MegaLinter reports

You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:

MegaLinter is graciously provided by OX Security

@github-actions GitHub Actions
Copy link
Contributor

Test Results

 2 files  ±0   2 suites  ±0   51s ⏱️ -2s
26 tests ±0  26 ✅ ±0  0 💤 ±0  0 ❌ ±0 
28 runs  ±0  28 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 24fb2b0. ± Comparison against base commit 94025e9.

@rjaegers rjaegers added this pull request to the merge queue Oct 20, 2024
Merged via the queue into main with commit 27c6b57 Oct 20, 2024
21 checks passed
@rjaegers rjaegers deleted the feature/amp-devcontainer-cpp/update-vscode-extensions branch October 20, 2024 08:08
@github-actions GitHub Actions
Copy link
Contributor

Pull Request Report (#610)

Static measures

Description Value
Number of added lines 2
Number of deleted lines 2
Number of changed files 1
Number of commits 1
Number of reviews 1
Number of comments (w/o review comments) 5
Number of reviews that contains a comment to resolve 0
Number of reviews that requested a change from the author 0
Number of reviews that approved the Pull Request 1
Get the total number of participants of a Pull Request 4

Time related measures

Description Value
PR lead time (from creation to close of PR) 5.3 Hours
Time that was spend on the branch before the PR was created 3 Sec
Time that was spend on the branch before the PR was merged 5.3 Hours
Time to merge after last review 3.7 Min

Status check related measures

Description Value
Total runtime for last status check run (Workflow for PR) 21.6 Min
Total time spend in last status check run on PR 10.8 Min

@philips-software-forest-releaser philips-software-forest-releaser bot mentioned this pull request Oct 20, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rjaegers rjaegers rjaegers approved these changes

Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file vscode-extensions
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@rjaegers