这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@Boshen
Copy link
Member

@Boshen Boshen commented Nov 16, 2025

No description provided.

Copy link
Member Author

Boshen commented Nov 16, 2025


How to use the Graphite Merge Queue

Add the label merge to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@codecov
Copy link

codecov bot commented Nov 16, 2025

Codecov Report

❌ Patch coverage is 28.57143% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 93.97%. Comparing base (06c2c45) to head (31ed0e0).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
src/file_system.rs 0.00% 6 Missing ⚠️
src/cache/cache_impl.rs 50.00% 4 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #835      +/-   ##
==========================================
- Coverage   94.21%   93.97%   -0.24%     
==========================================
  Files          17       17              
  Lines        3078     3089      +11     
==========================================
+ Hits         2900     2903       +3     
- Misses        178      186       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@codspeed-hq
Copy link

codspeed-hq bot commented Nov 16, 2025

CodSpeed Performance Report

Merging #835 will improve performances by 4.64%

Comparing 11-16-fix_use_std_fs_canonicalize_as_a_fallback_when_canonicalize_fails (31ed0e0) with main (e9c472c)1

Summary

⚡ 1 improvement
✅ 10 untouched
⏩ 5 skipped2

Benchmarks breakdown

Benchmark BASE HEAD Change
complex_real 23.4 µs 22.4 µs +4.64%

Footnotes

  1. No successful run was found on main (31ed0e0) during the generation of this report, so e9c472c was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

  2. 5 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@Boshen Boshen added the merge label Nov 16, 2025
Copy link
Member Author

Boshen commented Nov 16, 2025

Merge activity

@graphite-app graphite-app bot force-pushed the 11-16-refactor_remove_cachedpathimpl_canonicaling branch from 5c6f234 to 06c2c45 Compare November 16, 2025 09:27
@graphite-app graphite-app bot force-pushed the 11-16-fix_use_std_fs_canonicalize_as_a_fallback_when_canonicalize_fails branch from 283600f to 31ed0e0 Compare November 16, 2025 09:28
Base automatically changed from 11-16-refactor_remove_cachedpathimpl_canonicaling to main November 16, 2025 09:31
@graphite-app graphite-app bot removed the merge label Nov 16, 2025
@graphite-app graphite-app bot merged commit 31ed0e0 into main Nov 16, 2025
17 checks passed
@graphite-app graphite-app bot deleted the 11-16-fix_use_std_fs_canonicalize_as_a_fallback_when_canonicalize_fails branch November 16, 2025 09:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants