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
[Due for payment 2025-11-07] [Due for payment 2025-11-06] Expense - App opens different report when submitting expense offline and returning online #73715
👋 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.
🔄 I ran Vector1 on this deploy blocker issue and here are the top 3 possible offending PRs based on semantic similarity2 and reranking3:
#65776: Fix: Infinite Loading When Member Is Removed from Workspace Chat
#72832: fix: Invoice report opens in wide RHP
#72756: Category field when creating an expense in the selfDM
Note
PR # and name added as text only to avoid triggering regression automation on the issues which the above PRs are addressing in case the finding is incorrect.
Footnotes
Vector is currently a local-only prototype stage app that uses AI embeddings to find offending PRs for a given deploy blocker issue. Because of the early stage of the app, results must be taken with with a grain of🧂. How it works: grab deploy blocker issue's OP data (title, steps, expected / actual result) and embed -> grab all deploy checklist issue PRs data (title, explanation of change, tests, changed files, AI diff summary) and embed -> calculate cosine similarity of issue embedding to each PRs embedding -> get results -> perform reranking -> get final results. ↩
Semantic similarity, when applied to embeddings, measures the similarity in meaning between different pieces of text by comparing their vector representations in a high-dimensional "semantic space". Texts with similar meanings are mapped to vectors that are close together, and this "closeness" is quantified using metrics like cosine similarity. This technology enables search engines and chatbots to find relevant information even without exact keyword matches, providing more accurate and contextualized results. ↩
Reranking is using a machine learning model that refines the order of search results from an initial retrieval system to improve relevance. It is used as a second, more computationally intensive stage in a search pipeline to ensure that the most accurate and contextually relevant documents are shown first. ↩
changed the title [-]Expense - App opens different report when submitting expense offline and returning online[/-][+][Due for payment 2025-11-06] Expense - App opens different report when submitting expense offline and returning online[/+]on Oct 30, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.40-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@amyevans The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
changed the title [-][Due for payment 2025-11-06] Expense - App opens different report when submitting expense offline and returning online[/-][+][Due for payment 2025-11-07] [Due for payment 2025-11-06] Expense - App opens different report when submitting expense offline and returning online[/+]on Oct 31, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.41-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@amyevans The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
Activity
melvin-bot commentedon Oct 29, 2025
Triggered auto assignment to @isabelastisser (
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 Oct 29, 2025
Triggered auto assignment to @roryabraham (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 29, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 29, 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:
ikevin127 commentedon Oct 29, 2025
🔄 I ran Vector1 on this deploy blocker issue and here are the top 3 possible offending PRs based on semantic similarity2 and reranking3:
Note
PR # and name added as text only to avoid triggering regression automation on the issues which the above PRs are addressing in case the finding is incorrect.
Footnotes
Vector is currently a local-only prototype stage app that uses AI embeddings to find offending PRs for a given deploy blocker issue. Because of the early stage of the app, results must be taken with with a grain of🧂. How it works: grab deploy blocker issue's OP data (title, steps, expected / actual result) and embed -> grab all deploy checklist issue PRs data (title, explanation of change, tests, changed files, AI diff summary) and embed -> calculate cosine similarity of issue embedding to each PRs embedding -> get results -> perform reranking -> get final results. ↩
Semantic similarity, when applied to embeddings, measures the similarity in meaning between different pieces of text by comparing their vector representations in a high-dimensional "semantic space". Texts with similar meanings are mapped to vectors that are close together, and this "closeness" is quantified using metrics like cosine similarity. This technology enables search engines and chatbots to find relevant information even without exact keyword matches, providing more accurate and contextualized results. ↩
Reranking is using a machine learning model that refines the order of search results from an initial retrieval system to improve relevance. It is used as a second, more computationally intensive stage in a search pipeline to ensure that the most accurate and contextually relevant documents are shown first. ↩
9 remaining items
amyevans commentedon Oct 29, 2025
Great, closing!
[-]Expense - App opens different report when submitting expense offline and returning online[/-][+][Due for payment 2025-11-06] Expense - App opens different report when submitting expense offline and returning online[/+]melvin-bot commentedon Oct 30, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Oct 30, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.40-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-11-06. 🎊
melvin-bot commentedon Oct 30, 2025
@amyevans The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
[-][Due for payment 2025-11-06] Expense - App opens different report when submitting expense offline and returning online[/-][+][Due for payment 2025-11-07] [Due for payment 2025-11-06] Expense - App opens different report when submitting expense offline and returning online[/+]melvin-bot commentedon Oct 31, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.41-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-11-07. 🎊
melvin-bot commentedon Oct 31, 2025
@amyevans The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]