Skip to content

Conversation

@lakchote
Copy link
Contributor

@lakchote lakchote commented Oct 8, 2025

Reverts #71162

Fixes

#72058
#72064

@lakchote lakchote marked this pull request as ready for review October 8, 2025 12:00
@lakchote lakchote requested a review from a team as a code owner October 8, 2025 12:00
@melvin-bot melvin-bot bot requested a review from Gonals October 8, 2025 12:01
@mountiny mountiny changed the title Revert "fix: Reports - More menu on expense RHP blocks primary and secondary button." [CP Staging] Revert "fix: Reports - More menu on expense RHP blocks primary and secondary button." Oct 8, 2025
@melvin-bot
Copy link

melvin-bot bot commented Oct 8, 2025

@Gonals Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot bot removed the request for review from a team October 8, 2025 12:01
Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Straight revert

@mountiny
Copy link
Contributor

mountiny commented Oct 8, 2025

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory

Flaky test failure - straight revert

@mountiny mountiny merged commit 9037835 into main Oct 8, 2025
21 of 26 checks passed
export default PopoverMenu;
export default React.memo(
PopoverMenu,
(prevProps, nextProps) =>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ PERF-5 (docs)

Using deepEqual for React.memo comparisons creates performance overhead that often exceeds the re-render cost they aim to prevent. Deep equality checks recursively compare all nested properties.

Consider using shallow comparisons of specific relevant properties instead:

export default React.memo(
    PopoverMenu,
    (prevProps, nextProps) =>
        prevProps.menuItems === nextProps.menuItems &&
        prevProps.isVisible === nextProps.isVisible &&
        prevProps.anchorPosition === nextProps.anchorPosition &&
        // ... other primitive comparisons
);

@mountiny mountiny deleted the revert-71162-krishna2323/issue/70364 branch October 8, 2025 12:02
@melvin-bot melvin-bot bot added the Emergency label Oct 8, 2025
@melvin-bot
Copy link

melvin-bot bot commented Oct 8, 2025

@mountiny looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

export default React.memo(
PopoverMenu,
(prevProps, nextProps) =>
deepEqual(prevProps.menuItems, nextProps.menuItems) &&
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❌ PERF-5 (docs)

Using deepEqual for comparing menuItems creates unnecessary performance overhead. Since menuItems is likely to be a new array reference on each render, this deep comparison will run on every update.

Consider using a reference equality check or memoizing the menuItems in the parent component:

prevProps.menuItems === nextProps.menuItems

@mountiny mountiny removed the Emergency label Oct 8, 2025
@lakchote lakchote removed the request for review from Gonals October 8, 2025 12:05
OSBotify pushed a commit that referenced this pull request Oct 8, 2025
…ue/70364

[CP Staging] Revert "fix: Reports - More menu on expense RHP blocks primary and secondary button."

(cherry picked from commit 9037835)

(cherry-picked to staging by lakchote)
@OSBotify OSBotify added the CP Staging marks PRs that have been CP'd to staging label Oct 8, 2025
@OSBotify
Copy link
Contributor

OSBotify commented Oct 8, 2025

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify
Copy link
Contributor

OSBotify commented Oct 8, 2025

🚀 Cherry-picked to staging by https://github.com/lakchote in version: 9.2.27-2 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@OSBotify
Copy link
Contributor

OSBotify commented Oct 8, 2025

🚀 Deployed to production by https://github.com/lakchote in version: 9.2.27-6 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@OSBotify
Copy link
Contributor

OSBotify commented Oct 8, 2025

🚀 Cherry-picked to staging by https://github.com/lakchote in version: 9.2.28-0 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.2.28-5 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CP Staging marks PRs that have been CP'd to staging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants