You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Sentry: APP-JDP] Web SearchReport max update depth exceeded during file validation #97102
⚠️Medium confidence — the regression source and the offending code are identified with a concrete mechanism, but the exact loop hasn't been reproduced (1 user / 8 events, no repro steps). Treat as a strong starting point.
What is the root cause of that problem?
The crash is a React state-update loop inside useFilesValidation, which is what runs when you drop/paste a receipt onto a transaction in a report opened from Search (the report-view consumer is MoneyRequestReceiptView.tsx:257-274).
The likely trigger is PR #93234 ("Prevent OOM tab reload when attaching multiple files on mWeb", merged 2026-07-16). That PR rewrote PDF validation from "mount all thumbnails at once" to "mount one at a time" and added a validatedPDFCount counter that is incremented via setState inside every thumbnail settle callback. 9.4.43-1 (first-seen 2026-07-27) is the first release that contains it, which lines up with the crash appearing.
The mechanism: checkIfAllValidatedAndProceed compares a ref (validatedPDFs.current.length, mutated synchronously) against a state value read from a stale render closure (pdfFilesToRender.length). Each setValidatedPDFCount increment re-renders and remounts the next PDFThumbnail, which re-creates that closure. Because the callbacks call setValidatedPDFCount(...) and checkIfAllValidatedAndProceed() synchronously in the same tick, the completion branch can re-satisfy and re-fire — driving handleNext() → hideLoaderAndHandleNext() (setIsLoaderVisible(false)) → reset() (~10 synchronous setStates) in a remount loop until React throws Maximum update depth exceeded. The hideLoaderAndHandleNext frame in the Sentry stack is this terminal cascade.
This is made worse by a weak re-entry guard: validateFiles guards with if (isValidatingFiles) return; on a state value (not a ref), and reset() flips it back to false in the same synchronous batch as onFilesValidated, so it offers almost no protection against a completion-triggered re-entry.
This is distinct from #96411 (workspace-selection loop during report creation) — same symptom, different route and code path.
What changes do you think we should make in order to solve the problem?
In checkIfAllValidatedAndProceed, stop gating completion on the pdfFilesToRenderstate value. Compare validatedPDFs.current.length against a stable ref count of PDFs to validate (set when pdfFilesToRender is populated), so a stale closure can't cause the counts to disagree and re-fire.
Make the isValidatingFiles re-entry guard a ref so it can't be bypassed by a stale closure, and don't clear it in the same synchronous batch that calls onFilesValidated.
Guard checkIfAllValidatedAndProceed so its completion branch (onFilesValidated + reset()) can only run once per validation batch (e.g. an isFinalizing ref latch).
What alternative solutions did you explore? (Optional)
Confirming via logs before/while fixing: check the frequency of the Log.warn('Files are already being validated...') message (useFilesValidation.tsx:341) around the crash window, and whether crashing sessions involved PDFs vs plain images — this distinguishes the PDF-thumbnail loop from a pure non-PDF terminal cascade.
Not fully proven: that a PDFThumbnail callback can fire more than once (would make the loop deterministic — lives in react-pdf internals), and whether a single non-PDF image drop alone can trigger the loop without a PDF. Both need runtime confirmation.
MoneyRequestReceiptView is the report-view consumer that renders {PDFValidationComponent}, consistent with the /search/view/:reportID route.
Next Steps for Contributor+ team: To accept:@MelvinBot implement [this](https://github.com/Expensify/App/issues/97102) to create a draft PR. To refine:@MelvinBot <your feedback> To reject: Explain why you are rejecting Melvin's proposal.
Fair question — here's exactly how I got there, and why your FullStory finding matters.
What the RCA was actually based on (not a session replay):
The Sentry stack frames in the issue body — hideLoaderAndHandleNext and sortFilesByOriginalOrder. Both symbols are defined in exactly one file, src/hooks/useFilesValidation.tsx (grep for const hideLoaderAndHandleNext / sortFilesByOriginalOrder = returns only that file), so if those frames are real, the crash is in the file-validation hook.
The version timeline — first seen on 9.4.43-1, which is the first build containing PR Prevent OOM tab reload when attaching multiple files on mWeb #93234 (bf7ea9f), which added the setValidatedPDFCount state updates that turn a redundant PDF re-render into an infinite loop.
That's code + release correlation. I did not have session or log evidence that a file was being attached — I flagged the attachment trigger as unverified and rated the whole thing Medium confidence for that reason.
Your FullStory observation is the missing runtime check, and it's a real challenge to the premise. If the crashing session had no attachment at all, the "drop/paste a receipt" trigger is wrong. Two ways to reconcile it — both need the crashing Sentry event, which I can't open from here:
Is that FullStory session actually one of the 8 crash events? (match user + timestamp). If it's a different session, it doesn't disprove anything.
On the crashing event specifically, two things to read:
The un-minified stack — do useFilesValidation frames genuinely appear, or is hideLoaderAndHandleNext a symbolication artifact from the minified prod bundle? Minified stacks mis-map frames fairly often, and if that's the case the whole useFilesValidation line of reasoning (mine and both contributor proposals) collapses.
The breadcrumbs for the entire session, not just the final click. The two proposals below describe a latent render loop seeded by a PDF attach — the attach could have happened earlier and the loop only tipped over React's limit on a later render (e.g. the link click you saw). So the decisive question isn't "did the click have an attachment" but "did this session attach any file (especially a PDF) at any point?" If the answer is a hard no, the RCA is wrong.
So: the RCA is a code-and-version inference from the reported stack frames, not a confirmed reproduction. If you can confirm from the crashing event that no file (PDF or otherwise) was attached anywhere in that session, I'd treat the useFilesValidation attribution as a likely minification artifact and we should re-open the root cause rather than accept any of the three proposals.
Suspected regression commit:bf7ea9ff8f6 — "Cap concurrent PDF.js parses: focused-only carousel mount + serialized PDF validation"
Summary
An infinite React update loop (Error: Maximum update depth exceeded, React production error #185) is thrown while a user repeatedly uploads receipts on expense report views (/search/view/*, view name SearchReport). It surfaces as an unhandled promise rejection (mechanism: auto.browser.global_handlers.onunhandledrejection), so the user sees an "Unhandled Promise Rejection" alert rather than a clean recovery.
Impact / scope
Field
Value
First seen
2026-07-27 11:41 UTC
Last seen
2026-07-27 11:43 UTC
Release
new.expensify@9.4.43-1 (standalone / web)
Occurrences
8 (within ~2 min)
Users impacted
1 — kym.mcgain@plenti.com.au (admin)
Account size
61–300 personal details, 301–1000 reports, 2–10 policies
Fullstory confirms the trigger behaviorally. From ~79 min into the session the user runs a tight, repetitive bulk-upload loop:
Click an expense row in Search results (mostly "Software Subscription", also "IT & misc computing", "Employee Entertainment", "Meals").
Navigate to /search/view/{reportID}.
Click "Add a receipt or drag and drop" (34× total across the session).
Navigate back to /search?q=type:expense… and repeat, ~10s apart.
Every one of the 4 captured React #185 crashes fires ~0.7–1.0s after an "Add a receipt" click:
Crash timestamp
Preceding "Add a receipt" click
Report view
87m28.9s
87m28.2s
/search/view/5851350659843724
88m10.8s
88m10.0s
/search/view/626007684385171
88m52.8s
88m51.5s
/search/view/5495105168360751
89m36.8s
89m35.8s
/search/view/2319127091036807
The report in the Sentry culprit (/search/view/3157155020102124) was opened immediately after the 4th crash. No other console errors/warnings appear in the session — only React #185 — directly tying the loop to the receipt-validation flow. It is intermittent: ~4 crashes across ~34 uploads.
Analysis / likely root cause
React's max-update-depth guard is global to the React root, so the setIsLoaderVisible(false) in the stack is the straw, not necessarily the loop origin — the tree is already in a runaway render/commit cycle when the upload settles.
The completion path in validateAndResizeFiles fires a synchronous cascade of setState calls (setIsLoaderVisible(false), setValidFilesToUpload, onFilesValidated, reset) once validation finishes.
Prime suspect for the loop: commit bf7ea9ff8f6 (shipped in the 9.4.43 window), which rewrote PDF validation to render one thumbnail at a time via new validatedPDFCount state + checkIfAllValidatedAndProceed(), which reads pdfFilesToRender (state) through render-time closures and re-enters the setState-heavy completion path. This hook also has prior render-loop/flicker history (c4f623ac802 "App blinks when Attachment error modal shows up", 99a74c899e8 stale isValidatingMultipleFiles), so it's a fragile area.
Confidence: the error, trigger, code path, and regression window are firmly established. The exact looping line could not be isolated from the minified production bundle alone (Sentry Seer autofix is unavailable — "No budget for Seer Autofix"); pinpointing it needs a local repro.
Steps to reproduce
Log in on new.expensify.com (web) as an admin on an account with many reports (the repro account has 301–1000).
Go to Search → type:expense and open an expense report view (/search/view/{reportID}).
Click "Add a receipt or drag and drop" and pick a receipt file.
Navigate back to the search results, open a different expense, and upload again.
Repeat rapidly, back-to-back across many expenses (~1 upload every ~10s, dozens in a row), as in the Fullstory session.
After several uploads the app enters an update loop and throws Maximum update depth exceeded (unhandled promise rejection alert).
⚠️ Repro is intermittent (~4 crashes / ~34 uploads in the reported session) — may take many iterations.
Expected result
Repeatedly uploading receipts should never trigger an infinite render loop or an unhandled promise rejection; each upload should validate and attach (or show an error modal) independently.
Actual result
After rapid repeated uploads, React throws error #185 and the failure escapes as an uncaught promise rejection.
Suggested next steps
Defensive (safe regardless of exact loop): guard the validateAndResizeFiles(...) call at useFilesValidation.tsx:362 with a .catch and reset isValidatingFiles on failure, so a render loop can't escape as an unhandled rejection.
Reproduce & bisect against bf7ea9ff8f6 to confirm the validatedPDFCount / checkIfAllValidatedAndProceed path is the loop.
Fix the loop and land with Fixes APP-JDP in the commit message to auto-close the issue.
Platform
Web (standalone) · Edge 150 / Windows ≥10 · new.expensify@9.4.43-1
Thanks shubham1206agra — this writeup lines up with what I found, and the Fullstory timing (crash ~0.7–1.0s after each "Add a receipt" click) is strong evidence. Agreeing on the root-cause window, plus one verified addition and a concrete recommendation.
Addition — the crash also wedges the hook (verified, and explains the intermittency): validateFiles sets setIsValidatingFiles(true) at L345 and is only reset to false inside reset() (L98), which runs only on the success/complete paths. When #185 throws, reset() is never reached, so isValidatingFiles stays true and the guard at L340-L343 silently blocks every future upload on that mounted hook (only the Files are already being validated warning). This fits the observed pattern: each crash is followed by navigating to a different report → the hook remounts fresh (isValidatingFiles back to false), which is why the user could keep uploading despite ~4 crashes across ~34 uploads. So the defensive fix isn't just cosmetic — without it, a crash leaves the receipt uploader dead until remount.
Recommendation:
Land the defensive guard now (safe regardless of the exact loop): wrap the calls at L362/L373 so a thrown error is caught, reset() runs (clearing isValidatingFiles + the loader), and the failure is Logged instead of becoming an unhandled rejection. This kills both the alert and the wedge.
Fix the loop origin (the actual cure). Leading code-level candidate: checkIfAllValidatedAndProceed (L127-L154) gates completion on the pdfFilesToRenderstate value read through a render-time closure while progress is tracked in refs + validatedPDFCount; each increment remounts the next PDFThumbnail and re-creates that closure. Fix by comparing against a stable ref count and latching the completion branch so onFilesValidated + reset() can only fire once per batch.
Still needs a local repro (agreed) to pin the exact looping line and to confirm whether it reproduces with plain images or only when a PDF is in the mix — I couldn't isolate it from the minified bundle either. Bisecting against bf7ea9f is the right call.
Note on "straw vs origin"
Your framing is right: React's nestedUpdateCount guard is per-root, so setIsLoaderVisible(false) being in the stack just means it was the setState that tripped the 50-update limit — the tree was already in a runaway cycle. That's why fix #1 (catch/reset) stops the unhandled-rejection + wedge symptom but fix #2 (breaking the re-render cycle) is the real cure. Both are worth landing.
Next Steps for Contributor+ team: To accept:@MelvinBot implement [this](https://github.com/Expensify/App/issues/97102) to create a draft PR (I'd start with the defensive guard). To refine:@MelvinBot <your feedback> To reject: Explain why you are rejecting Melvin's proposal.
Activity
melvin-bot commentedon Jul 27, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @shubham1206agra (
External)melvin-bot commentedon Jul 27, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022081739761753094034
MelvinBot commentedon Jul 27, 2026
Proposal
What is the root cause of that problem?
The crash is a React state-update loop inside
useFilesValidation, which is what runs when you drop/paste a receipt onto a transaction in a report opened from Search (the report-view consumer isMoneyRequestReceiptView.tsx:257-274).The likely trigger is PR #93234 ("Prevent OOM tab reload when attaching multiple files on mWeb", merged 2026-07-16). That PR rewrote PDF validation from "mount all thumbnails at once" to "mount one at a time" and added a
validatedPDFCountcounter that is incremented viasetStateinside every thumbnail settle callback. 9.4.43-1 (first-seen 2026-07-27) is the first release that contains it, which lines up with the crash appearing.The mechanism:
checkIfAllValidatedAndProceedcompares a ref (validatedPDFs.current.length, mutated synchronously) against a state value read from a stale render closure (pdfFilesToRender.length). EachsetValidatedPDFCountincrement re-renders and remounts the nextPDFThumbnail, which re-creates that closure. Because the callbacks callsetValidatedPDFCount(...)andcheckIfAllValidatedAndProceed()synchronously in the same tick, the completion branch can re-satisfy and re-fire — drivinghandleNext()→hideLoaderAndHandleNext()(setIsLoaderVisible(false)) →reset()(~10 synchronoussetStates) in a remount loop until React throws Maximum update depth exceeded. ThehideLoaderAndHandleNextframe in the Sentry stack is this terminal cascade.This is made worse by a weak re-entry guard:
validateFilesguards withif (isValidatingFiles) return;on a state value (not a ref), andreset()flips it back tofalsein the same synchronous batch asonFilesValidated, so it offers almost no protection against a completion-triggered re-entry.This is distinct from #96411 (workspace-selection loop during report creation) — same symptom, different route and code path.
What changes do you think we should make in order to solve the problem?
checkIfAllValidatedAndProceed, stop gating completion on thepdfFilesToRenderstate value. ComparevalidatedPDFs.current.lengthagainst a stable ref count of PDFs to validate (set whenpdfFilesToRenderis populated), so a stale closure can't cause the counts to disagree and re-fire.isValidatingFilesre-entry guard a ref so it can't be bypassed by a stale closure, and don't clear it in the same synchronous batch that callsonFilesValidated.checkIfAllValidatedAndProceedso its completion branch (onFilesValidated+reset()) can only run once per validation batch (e.g. anisFinalizingref latch).What alternative solutions did you explore? (Optional)
Confirming via logs before/while fixing: check the frequency of the
Log.warn('Files are already being validated...')message (useFilesValidation.tsx:341) around the crash window, and whether crashing sessions involved PDFs vs plain images — this distinguishes the PDF-thumbnail loop from a pure non-PDF terminal cascade.Investigation details & what's unverified
bf7ea9f, merged 2026-07-16) introducedvalidatedPDFCount, the one-at-a-timepdfFilesToRender.at(validatedPDFCount)render, andsetValidatedPDFCount((c) => c + 1)in each callback.sortFilesByOriginalOrder/hideLoaderAndHandleNext/ the loader logic predate it. This hook has a documented history of stale-state bugs (e.g. Fix stale isValidatingMultipleFiles state in file validation error modal #88753).PDFThumbnailcallback can fire more than once (would make the loop deterministic — lives inreact-pdfinternals), and whether a single non-PDF image drop alone can trigger the loop without a PDF. Both need runtime confirmation.MoneyRequestReceiptViewis the report-view consumer that renders{PDFValidationComponent}, consistent with the/search/view/:reportIDroute.Next Steps for Contributor+ team:
To accept:
@MelvinBot implement [this](https://github.com/Expensify/App/issues/97102)to create a draft PR.To refine:
@MelvinBot <your feedback>To reject: Explain why you are rejecting Melvin's proposal.
shubham1206agra commentedon Jul 27, 2026
@MelvinBot I have watched https://app.fullstory.com/ui/o-1WN56P-na1/session/4692981788963911322:4786187663065064339!8401347299423219620/devtools/console and the link the user clicks on does not have any attachment. How did you arrive at the RCA?
MelvinBot commentedon Jul 27, 2026
Fair question — here's exactly how I got there, and why your FullStory finding matters.
What the RCA was actually based on (not a session replay):
hideLoaderAndHandleNextandsortFilesByOriginalOrder. Both symbols are defined in exactly one file,src/hooks/useFilesValidation.tsx(grep forconst hideLoaderAndHandleNext/sortFilesByOriginalOrder =returns only that file), so if those frames are real, the crash is in the file-validation hook.9.4.43-1, which is the first build containing PR Prevent OOM tab reload when attaching multiple files on mWeb #93234 (bf7ea9f), which added thesetValidatedPDFCountstate updates that turn a redundant PDF re-render into an infinite loop.That's code + release correlation. I did not have session or log evidence that a file was being attached — I flagged the attachment trigger as unverified and rated the whole thing Medium confidence for that reason.
Your FullStory observation is the missing runtime check, and it's a real challenge to the premise. If the crashing session had no attachment at all, the "drop/paste a receipt" trigger is wrong. Two ways to reconcile it — both need the crashing Sentry event, which I can't open from here:
useFilesValidationframes genuinely appear, or ishideLoaderAndHandleNexta symbolication artifact from the minified prod bundle? Minified stacks mis-map frames fairly often, and if that's the case the wholeuseFilesValidationline of reasoning (mine and both contributor proposals) collapses.So: the RCA is a code-and-version inference from the reported stack frames, not a confirmed reproduction. If you can confirm from the crashing event that no file (PDF or otherwise) was attached anywhere in that session, I'd treat the
useFilesValidationattribution as a likely minification artifact and we should re-open the root cause rather than accept any of the three proposals.shubham1206agra commentedon Jul 27, 2026
@MelvinBot Read the comment below
🐛
Maximum update depth exceeded(React #185) during rapid receipt uploads on Search report viewLinks
src/hooks/useFilesValidation.tsxbf7ea9ff8f6— "Cap concurrent PDF.js parses: focused-only carousel mount + serialized PDF validation"Summary
An infinite React update loop (
Error: Maximum update depth exceeded, React production error #185) is thrown while a user repeatedly uploads receipts on expense report views (/search/view/*, view nameSearchReport). It surfaces as an unhandled promise rejection (mechanism: auto.browser.global_handlers.onunhandledrejection), so the user sees an "Unhandled Promise Rejection" alert rather than a clean recovery.Impact / scope
new.expensify@9.4.43-1(standalone / web)kym.mcgain@plenti.com.au(admin)New in 9.4.43 — not present in earlier releases.
Evidence
Stacktrace (minified, from the Sentry event) resolves entirely into
useFilesValidation.tsx:Fullstory confirms the trigger behaviorally. From ~79 min into the session the user runs a tight, repetitive bulk-upload loop:
/search/view/{reportID}./search?q=type:expense…and repeat, ~10s apart.Every one of the 4 captured React #185 crashes fires ~0.7–1.0s after an "Add a receipt" click:
/search/view/5851350659843724/search/view/626007684385171/search/view/5495105168360751/search/view/2319127091036807The report in the Sentry culprit (
/search/view/3157155020102124) was opened immediately after the 4th crash. No other console errors/warnings appear in the session — only React #185 — directly tying the loop to the receipt-validation flow. It is intermittent: ~4 crashes across ~34 uploads.Analysis / likely root cause
setIsLoaderVisible(false)in the stack is the straw, not necessarily the loop origin — the tree is already in a runaway render/commit cycle when the upload settles.validateAndResizeFilesfires a synchronous cascade of setState calls (setIsLoaderVisible(false),setValidFilesToUpload,onFilesValidated,reset) once validation finishes.validateFilescallsvalidateAndResizeFiles(...)withoutawaitand without.catch(useFilesValidation.tsx:362) — so a thrown Add link styles for sidebar footer #185 has no handler and becomes an uncaught promise rejection.bf7ea9ff8f6(shipped in the 9.4.43 window), which rewrote PDF validation to render one thumbnail at a time via newvalidatedPDFCountstate +checkIfAllValidatedAndProceed(), which readspdfFilesToRender(state) through render-time closures and re-enters the setState-heavy completion path. This hook also has prior render-loop/flicker history (c4f623ac802"App blinks when Attachment error modal shows up",99a74c899e8staleisValidatingMultipleFiles), so it's a fragile area.Steps to reproduce
new.expensify.com(web) as an admin on an account with many reports (the repro account has 301–1000).type:expenseand open an expense report view (/search/view/{reportID}).Maximum update depth exceeded(unhandled promise rejection alert).Expected result
Repeatedly uploading receipts should never trigger an infinite render loop or an unhandled promise rejection; each upload should validate and attach (or show an error modal) independently.
Actual result
After rapid repeated uploads, React throws error #185 and the failure escapes as an uncaught promise rejection.
Suggested next steps
validateAndResizeFiles(...)call atuseFilesValidation.tsx:362with a.catchand resetisValidatingFileson failure, so a render loop can't escape as an unhandled rejection.bf7ea9ff8f6to confirm thevalidatedPDFCount/checkIfAllValidatedAndProceedpath is the loop.Fixes APP-JDPin the commit message to auto-close the issue.Platform
Web (standalone) · Edge 150 / Windows ≥10 ·
new.expensify@9.4.43-1MelvinBot commentedon Jul 27, 2026
Thanks
shubham1206agra— this writeup lines up with what I found, and the Fullstory timing (crash ~0.7–1.0s after each "Add a receipt" click) is strong evidence. Agreeing on the root-cause window, plus one verified addition and a concrete recommendation.What I can confirm in code (high confidence):
useFilesValidation.tsx:362callsvalidateAndResizeFiles(...)with noawaitand no.catch, so a thrown React Add link styles for sidebar footer #185 escapes as an unhandled promise rejection. (Same for the retry call at L373.)bf7ea9f= PR Prevent OOM tab reload when attaching multiple files on mWeb #93234, first shipped in 9.4.43 — it introduced thevalidatedPDFCount/ one-thumbnail-at-a-time render +checkIfAllValidatedAndProceed().Addition — the crash also wedges the hook (verified, and explains the intermittency):
validateFilessetssetIsValidatingFiles(true)at L345 and is only reset tofalseinsidereset()(L98), which runs only on the success/complete paths. When #185 throws,reset()is never reached, soisValidatingFilesstaystrueand the guard at L340-L343 silently blocks every future upload on that mounted hook (only theFiles are already being validatedwarning). This fits the observed pattern: each crash is followed by navigating to a different report → the hook remounts fresh (isValidatingFilesback tofalse), which is why the user could keep uploading despite ~4 crashes across ~34 uploads. So the defensive fix isn't just cosmetic — without it, a crash leaves the receipt uploader dead until remount.Recommendation:
reset()runs (clearingisValidatingFiles+ the loader), and the failure isLogged instead of becoming an unhandled rejection. This kills both the alert and the wedge.checkIfAllValidatedAndProceed(L127-L154) gates completion on thepdfFilesToRenderstate value read through a render-time closure while progress is tracked in refs +validatedPDFCount; each increment remounts the nextPDFThumbnailand re-creates that closure. Fix by comparing against a stable ref count and latching the completion branch soonFilesValidated+reset()can only fire once per batch.Still needs a local repro (agreed) to pin the exact looping line and to confirm whether it reproduces with plain images or only when a PDF is in the mix — I couldn't isolate it from the minified bundle either. Bisecting against
bf7ea9fis the right call.Note on "straw vs origin"
Your framing is right: React's
nestedUpdateCountguard is per-root, sosetIsLoaderVisible(false)being in the stack just means it was the setState that tripped the 50-update limit — the tree was already in a runaway cycle. That's why fix #1 (catch/reset) stops the unhandled-rejection + wedge symptom but fix #2 (breaking the re-render cycle) is the real cure. Both are worth landing.Next Steps for Contributor+ team:
To accept:
@MelvinBot implement [this](https://github.com/Expensify/App/issues/97102)to create a draft PR (I'd start with the defensive guard).To refine:
@MelvinBot <your feedback>To reject: Explain why you are rejecting Melvin's proposal.
melvin-bot commentedon Jul 30, 2026
@shubham1206agra Whoops! This issue is 2 days overdue. Let's get this updated quick!
shubham1206agra commentedon Jul 31, 2026
I will try to repro this again at night.
melvin-bot commentedon Aug 3, 2026
@shubham1206agra Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
shubham1206agra commentedon Aug 5, 2026
@mountiny Should we hold off here? Since this bug is not reported except for that session
mountiny commentedon Aug 6, 2026
Fair this only has one session so I think we can close