Conversation
🦋 Changeset detectedLatest commit: cf3d912 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAdded an empty Changeset markdown file and modified Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@packages/react/runtime/src/lifecycle/render.ts`:
- Around line 18-20: The duplicate profiling span should be removed and the
existing ReactLynx::renderMainThread trace (created via profileStart/profileEnd)
should be expanded to cover the entire renderMainThread function; move the
single profileStart to the outermost entry of renderMainThread and wrap the
function body in a try/finally that always calls profileEnd, removing the inner
profileStart/profileEnd pair that currently encloses renderOpcodesInto() and the
test-only opcode remap so the trace is not nested or left unbalanced if remap or
renderOpcodesInto() throws.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 53087848-02b1-40a7-be07-67e2acc6b84e
📒 Files selected for processing (2)
.changeset/itchy-dogs-search.mdpackages/react/runtime/src/lifecycle/render.ts
| if (typeof __PROFILE__ !== 'undefined' && __PROFILE__) { | ||
| profileStart('ReactLynx::renderMainThread'); | ||
| } |
There was a problem hiding this comment.
Expand the existing renderMainThread trace instead of adding a second one.
Lines 23-33 already manage a ReactLynx::renderMainThread span. Adding another start here and another end on Line 58 nests the same trace name, and the new outer end is skipped if the test-only opcode remap or renderOpcodesInto() throws. Since profileEnd just forwards to the native profiler, that can leave profiling state unbalanced and pollute later measurements. If the intent is to cover the whole function, widen the current trace to a single outer try/finally and drop the inner duplicate.
Also applies to: 57-59
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/react/runtime/src/lifecycle/render.ts` around lines 18 - 20, The
duplicate profiling span should be removed and the existing
ReactLynx::renderMainThread trace (created via profileStart/profileEnd) should
be expanded to cover the entire renderMainThread function; move the single
profileStart to the outermost entry of renderMainThread and wrap the function
body in a try/finally that always calls profileEnd, removing the inner
profileStart/profileEnd pair that currently encloses renderOpcodesInto() and the
test-only opcode remap so the trace is not nested or left unbalanced if remap or
renderOpcodesInto() throws.
Merging this PR will degrade performance by 66.25%
Performance Changes
Comparing Footnotes
|
React MTF Example#89 Bundle Size — 207.47KiB (0%).cf3d912(current) vs 78493b4 main#76(baseline) Bundle metrics
|
| Current #89 |
Baseline #76 |
|
|---|---|---|
0B |
0B |
|
0B |
0B |
|
0% |
0% |
|
0 |
0 |
|
3 |
3 |
|
174 |
174 |
|
68 |
68 |
|
46.09% |
46.09% |
|
2 |
2 |
|
0 |
0 |
Bundle size by type no changes
| Current #89 |
Baseline #76 |
|
|---|---|---|
111.23KiB |
111.23KiB |
|
96.24KiB |
96.24KiB |
Bundle analysis report Branch p/perf-trace Project dashboard
Generated by RelativeCI Documentation Report issue
React Example#6955 Bundle Size — 237.89KiB (0%).cf3d912(current) vs 78493b4 main#6942(baseline) Bundle metrics
|
| Current #6955 |
Baseline #6942 |
|
|---|---|---|
0B |
0B |
|
0B |
0B |
|
0% |
0% |
|
0 |
0 |
|
4 |
4 |
|
180 |
180 |
|
71 |
71 |
|
46.4% |
46.4% |
|
2 |
2 |
|
0 |
0 |
Bundle size by type no changes
| Current #6955 |
Baseline #6942 |
|
|---|---|---|
145.76KiB |
145.76KiB |
|
92.13KiB |
92.13KiB |
Bundle analysis report Branch p/perf-trace Project dashboard
Generated by RelativeCI Documentation Report issue
Web Explorer#8533 Bundle Size — 728.6KiB (0%).cf3d912(current) vs 78493b4 main#8520(baseline) Bundle metrics
Bundle size by type
|
| Current #8533 |
Baseline #8520 |
|
|---|---|---|
384.4KiB |
384.4KiB |
|
342.04KiB |
342.04KiB |
|
2.16KiB |
2.16KiB |
Bundle analysis report Branch p/perf-trace Project dashboard
Generated by RelativeCI Documentation Report issue
Summary by CodeRabbit
Checklist