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
Distance - Duplicate waypoints error is shown while creating distance expense offline #75773
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
Just tried reverting #75116 locally and that seems to fix the issue. I don't think a revert is necessary here since it's so minor but @bernhardoj please address a fix in a followup thanks!
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
Activity
melvin-bot commentedon Nov 21, 2025
Triggered auto assignment to @strepanier03 (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Nov 21, 2025
Triggered auto assignment to @jasperhuangg (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Nov 21, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 21, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
jasperhuangg commentedon Nov 21, 2025
This one seems suspicious: #75116, although I'm not sure that this needs to block deploy since it's such an edge case.
jasperhuangg commentedon Nov 21, 2025
Just tried reverting #75116 locally and that seems to fix the issue. I don't think a revert is necessary here since it's so minor but @bernhardoj please address a fix in a followup thanks!
bernhardoj commentedon Nov 23, 2025
Raised a follow up PR!
melvin-bot commentedon Dec 17, 2025
This issue has not been updated in over 15 days. @strepanier03, @jasperhuangg eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
jasperhuangg commentedon Dec 17, 2025
@DylanDylann are we good to close this out too based on #76331 (comment)?
DylanDylann commentedon Dec 17, 2025
Yesss