Skip to content

[$250] Web-Chat- Edit comment input is not focused #104360

Open

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: v9.5.13-3
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/79209900/folder/13176686/44007893/1871926840?sort=%2Bidentifier
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Windows 11 Chrome
App Component: Chat Report View

Action Performed:

Preconditions:

  • Create 2 workspaces
  • Delete 1 workspace
  1. Open https://staging.new.expensify.com/
  2. Navigate to Spend > Reports
  3. Click FAB
  4. Click 'Create reports'
  5. Comment on the empty report
  6. Right lick on the comment
  7. Click on 'Edit comment'

Expected Result:

Verify that the input of the message whose element you have selected is in focus

Actual Result:

The input compose is not focused

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7289481_1792305520541.bandicam_2026-10-18_13-29-40-872.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7289481

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @wildan-m

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 19, 2026
  2. applause-bot commented on Oct 19, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/d8325cff8e01e345bb4135539346d6690f60b2b78e100510d034efea4654e9e8

  3. MelvinBot commented on Oct 19, 2026

    @MelvinBot
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    After you delete a workspace, the "Edit comment" input does not get focus on a report opened from Spend > Reports.

    What is the root cause of that problem?

    Deleting a workspace leaves behind a "ready to focus" promise that never resolves. Every delayed composer focus then waits on it forever.

    1. The delete-workspace confirm modal stays open with a loading state. Then closeModal() removes it from the global modal stack while it is still visible. This unmounts the modal instead of hiding it.
    2. On unmount, BaseModal calls hideModal, but never ComposerFocusManager.setReadyToFocus(id). Only the visible→hidden path resolves the promise. So the modal's entry stays in promiseMap, unresolved.
    3. focusComposerWithDelay waits on ComposerFocusManager.isReadyToFocus() with no id. With no id, it reads the last key in promiseMap. Later modals add and remove their own keys, so the leaked entry ends up last again.
    4. In the RHP, ReportActionItemMessageEdit sets autoFocus={!shouldUseNarrowLayout}, which is false there. Its only focus path is the delayed focus on mount, which never runs.

    Inbox chats on wide web still work because autoFocus is true there. The empty report doesn't matter. The deleted workspace is the trigger.

    Code references

    What changes do you think we should make in order to solve the problem?

    In BaseModal, when the modal unmounts while still visible, also call ComposerFocusManager.setReadyToFocus(uniqueModalId) in the unmount cleanup. This fixes every global modal that closes while visible, not only delete-workspace.

    What alternative solutions did you explore? (Optional)

    • Have ConfirmModalWrapper hide itself first (isVisible=false), then pop the stack in onModalHide, instead of unmounting while visible.
    • Add a timeout to the isReadyToFocus() wait in focusComposerWithDelay, so one leaked promise can't block focus for the whole session.
    Confidence and verification

    Confidence: Medium. The code path is confirmed. I could not reproduce it at runtime: on web, the test tool can't right-click, so it never reached "Edit comment". The empty report was created and the comment posted fine.

    To confirm, test edit-comment in a fresh session where no workspace was deleted. This theory says it should focus there. In a session where a workspace was deleted, a non-empty report from Spend > Reports should also fail.


    Next Steps for Contributor+ team:
    To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/104360) to create a draft PR.
    To refine: @MelvinBot <your feedback>
    To reject: Explain why you are rejecting Melvin's proposal.


    view run · view recording

  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Oct 19, 2026
  5. melvin-bot commented on Oct 19, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (External)

  6. changed the title [-]Web-Chat- Edit comment input is not focused[/-] [+][$175] Web-Chat- Edit comment input is not focused[/+] on Oct 19, 2026
  7. melvin-bot commented on Oct 19, 2026

    @melvin-bot
  8. camesenin commented on Oct 19, 2026

    @camesenin
  9. melvin-bot commented on Oct 19, 2026

    @melvin-bot

    ✅ Contributor details stored successfully. Thank you for contributing to Expensify!

  10. azhumide commented on Oct 19, 2026

    @azhumide

    Contributor details
    Your Expensify account email: azhumide@gmail.com
    Upwork Profile Link: https://www.upwork.com/freelancers/~01096eb540e2a8e9a5

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    On Web, after deleting a workspace (or when any modal unmounts while visible), right-clicking a message in a report opened from Spend > Reports and selecting "Edit comment" fails to focus the edit comment composer input.

    What is the root cause of that problem?

    A leaked unresolved promise in ComposerFocusManager:

    1. When a modal opens (onModalWillShow), BaseModal.tsx:359 calls saveFocusState(), which calls ComposerFocusManager.resetReadyToFocus(uniqueModalId) (BaseModal.tsx:133). This registers a pending promise in ComposerFocusManager.promiseMap (src/libs/ComposerFocusManager.ts:189-198).

    2. In normal dismiss flows, handleDismissModal() runs in useEffect when !isVisible && wasVisible (BaseModal.tsx:174-176), invoking ComposerFocusManager.setReadyToFocus(uniqueModalId) which resolves and deletes the entry from promiseMap.

    3. However, when a modal unmounts directly while still visible (such as during DeleteWorkspaceFlow when closeModal pops the modal stack while in a loading state):
      The unmount effect runs (BaseModal.tsx:197-206):

      useEffect(
          () => () => {
              if (!shouldCallHideModalOnUnmount.current) {
                  return;
              }
              hideModalCallbackRef.current?.(true);
          },
          [],
      );

      This calls hideModalCallbackRef.current?.(true), which triggers hideModal() and calls ComposerFocusManager.refocusAfterModalFullyClosed(uniqueModalId, restoreFocusType) (BaseModal.tsx:152).
      However, handleDismissModal() is never called because the !isVisible && wasVisible update effect never executes when unmounting directly.

    4. As a result:

      • uniqueModalId remains permanently in promiseMap with an unresolved promise.
      • When entering edit comment mode, ReportActionItemMessageEdit.tsx:160 calls focusComposerWithDelay(composerRef.current)(true).
      • In src/libs/focusComposerWithDelay/index.ts:57, it awaits Promise.all([ComposerFocusManager.isReadyToFocus(), isWindowReadyToFocus()]).
      • ComposerFocusManager.isReadyToFocus() (called without arguments) invokes getTopmostModalId(), which returns the leaked modal ID from promiseMap.
      • This await hangs indefinitely, completely blocking composer focus.
    5. Flaws in existing proposals:

      • MelvinBot noted the unmount path but did not address unmount effect dependencies or memory cleanup in ComposerFocusManager.
      • camesenin proposed:
        useEffect(() => () => {
            ...
            handleDismissModal();
        }, [handleDismissModal]);
        In React, putting [handleDismissModal] as a dependency on an unmount cleanup effect is a critical bug: the cleanup function fires on every render where handleDismissModal changes, resolving the focus promise prematurely while the modal is still mounted and open.

    What changes do you think we should make in order to solve the problem?

    1. In src/components/Modal/BaseModal.tsx:
      • Store uniqueModalId in a ref (or capture it cleanly) and invoke ComposerFocusManager.setReadyToFocus inside the unmount cleanup effect:
      const uniqueModalIdRef = useRef(uniqueModalId);
      useEffect(() => {
          uniqueModalIdRef.current = uniqueModalId;
      }, [uniqueModalId]);
      
      useEffect(
          () => () => {
              if (!shouldCallHideModalOnUnmount.current) {
                  return;
              }
              hideModalCallbackRef.current?.(true);
              ComposerFocusManager.setReadyToFocus(uniqueModalIdRef.current);
          },
          // Keep empty dependency array so cleanup only runs when unmounting
          [],
      );
    2. In src/libs/ComposerFocusManager.ts (Defense-in-depth):
      • In getTopmostModalId(), verify that the returned modal ID corresponds to an active modal; if the map holds dangling keys with no active modals, prune them so isReadyToFocus() never hangs indefinitely.

    What specific scenarios should we cover in automated tests?

    In tests/ui/BaseModalTest.tsx:

    • Render BaseModal with isVisible={true}.
    • Unmount the component directly while still visible.
    • Verify that ComposerFocusManager.isReadyToFocus() resolves immediately after unmount instead of hanging unresolved.
  11. melvin-bot commented on Oct 19, 2026

    @melvin-bot

    ✅ Contributor details stored successfully. Thank you for contributing to Expensify!

  12. khizzcr7 commented on Oct 19, 2026

    @khizzcr7

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    After deleting a workspace, opening a report from Spend > Reports and right-clicking a comment to "Edit comment" does not focus the comment input on web.

    What is the root cause of that problem?

    Deleting the workspace leaves a never-resolving "ready to focus" promise behind, and every delayed composer focus after that waits on it forever:

    1. The delete-workspace confirm modal is closed via closeModal() while it is still in its loading state, which unmounts the modal instead of dismissing it.
    2. BaseModal's handleDismissModal (which calls ComposerFocusManager.setReadyToFocus(uniqueModalId)) only runs on the visible-to-hidden path (isVisible && wasVisible). The unmount cleanup calls hideModal, which only calls ComposerFocusManager.refocusAfterModalFullyClosed - that waits on isReadyToFocus(id) and never resolves the promise itself. So the modal's entry leaks in promiseMap.
    3. focusComposerWithDelay calls ComposerFocusManager.isReadyToFocus() with no id, which reads the last key in promiseMap via getTopmostModalId(). The leaked entry ends up last again, so delayed focus never fires.
    4. In the RHP, ReportActionItemMessageEdit sets autoFocus={!shouldUseNarrowLayout} which is false there, so the delayed focus on mount is its only focus path - and it never runs.

    Inbox chats on wide web still work because autoFocus is true there. The empty report and the deleted workspace are just the trigger, not the cause.

    What changes do you think we should make in order to solve the problem?

    In BaseModal, when the modal unmounts while it is still visible, also call ComposerFocusManager.setReadyToFocus(uniqueModalId) in the unmount cleanup. This fixes every global modal that closes while visible, not only the delete-workspace flow.

    What alternative solutions did you explore?

    • Have ConfirmModalWrapper hide itself first (isVisible=false), then pop the modal stack in onModalHide, instead of unmounting while visible.
    • Add a timeout to the isReadyToFocus() wait in focusComposerWithDelay, so one leaked promise cannot block focus for the whole session.

    What will I verify?

    • Delete a workspace, then open a report from Spend > Reports and right-click "Edit comment" on web: the input gets focus.
    • Normal modal dismiss focus-restore behavior is unchanged.
    • Add a unit test covering the unmount-while-visible path resolving the promise.
  13. 64 remaining items

  14. RajGahoi commented on Nov 12, 2026

    @RajGahoi

    Contributor details
    Your Expensify account email: gahoiraj01@gmail.com
    Upwork Profile Link: https://www.upwork.com/freelancers/~014898525b9c53fc32

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    On Web, after deleting a workspace and subsequently opening a report in the RHP (e.g. via Spend > Reports > Create report), posting a comment, and clicking "Edit comment", the edit message composer does not receive input focus.

    What is the root cause of that problem?

    Two factors interact to trigger this bug:

    1. Unresolved readyToFocus promise leak in ComposerFocusManager upon unmounting visible modals:

      • When the workspace deletion confirm modal opens, BaseModal.tsx registers a pending promise in ComposerFocusManager.resetReadyToFocus(uniqueModalId).
      • In DeleteWorkspaceFlow.tsx, the confirm modal remains in a loading state (isConfirmLoading: true) until the deletion completes, at which point closeModal() directly removes the modal from ModalContext.
      • This directly unmounts BaseModal while isVisible is still true.
      • While BaseModal's unmount cleanup calls hideModalCallbackRef.current?.(true), it does not call ComposerFocusManager.setReadyToFocus(uniqueModalId). (Normal resolution only happens when isVisible transitions from true to false or during onDismiss).
      • Consequently, uniqueModalId is left permanently in ComposerFocusManager.promiseMap with an unresolved promise.
    2. Delayed composer focus hangs forever in RHP:

      • In ReportActionItemMessageEdit.tsx, the input specifies autoFocus={!shouldUseNarrowLayout}. In RHP, isInNarrowPaneModal is true, making shouldUseNarrowLayout true, which disables autoFocus.
      • Therefore, focusing the composer depends entirely on focusComposerWithDelay(composerRef.current)(true) on mount.
      • focusComposerWithDelay awaits ComposerFocusManager.isReadyToFocus(). Without a modal ID passed, isReadyToFocus() defaults to getTopmostModalId(), which returns the leaked promise from the unmounted delete-workspace modal.
      • Because this promise never resolves, focusComposerWithDelay awaits indefinitely, and composerRef.current.focus() is never executed.

    What changes do you think we should make in order to solve the problem?

    1. In src/components/Modal/BaseModal.tsx:

      • In the unmount cleanup effect (useEffect(() => () => { ... }, [])), ensure that if shouldCallHideModalOnUnmount.current is true (i.e. the modal unmounted while visible), ComposerFocusManager.setReadyToFocus(uniqueModalId) is called before or alongside hideModalCallbackRef.current?.(true).
      • This guarantees that any modal unmounted directly from the modal stack cleans up and resolves its entry in promiseMap, preventing leaked promises from locking future delayed composer focuses.
    2. In src/libs/ComposerFocusManager.ts (Defensive guard):

      • In isReadyToFocus, if all active modals are closed or no matching modal is currently active, ensure it does not hang on orphaned promises.

    What alternative solutions did you explore? (Optional)

    • Adding a fallback timeout to focusComposerWithDelay: This only masks the leak by introducing an artificial delay before focus occurs. Resolving setReadyToFocus in BaseModal's unmount cleanup handles the leak at its origin.
    • Forcing autoFocus={true} in ReportActionItemMessageEdit: Does not fix the underlying leak in ComposerFocusManager, which would continue to affect any other delayed focus consumer in the app after an unmounted modal.

    What specific scenarios should we cover in automated tests?

    • Add a unit test in tests/ui/BaseModalTest.tsx (or ComposerFocusManagerTest.ts):
      1. Mount BaseModal with isVisible={true}.
      2. Unmount BaseModal directly while isVisible is still true.
      3. Assert that ComposerFocusManager.isReadyToFocus() resolves immediately and does not leave an unresolved entry in promiseMap.
  15. melvin-bot commented on Nov 12, 2026

    @melvin-bot

    ✅ Contributor details stored successfully. Thank you for contributing to Expensify!

  16. robertjchen commented on Nov 12, 2026

    @robertjchen
    Contributor

    Thanks @parasharrajat. Let's keep this issue scoped and go with @wildan-m's proposal.

    @neerajbachani the Concierge close case looks valid, but it's a separate focus path (closeSidePanel and the focus trap). Changing those here adds regression risk to a fix that's otherwise small 🤔 Please report it in #expensify-bugs as its own issue and link it here 👍

  17. aion-citadel-forge commented on Nov 12, 2026

    @aion-citadel-forge

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    On Web, after deleting a workspace (or closing any modal that unmounts while isVisible is true), navigating to Spend > Reports, creating or opening a report, commenting on the empty report, right-clicking on the comment, and clicking Edit comment, the edit comment composer input does not receive focus.

    What is the root cause of that problem?

    In src/components/Modal/BaseModal.tsx:

    1. When a modal opens, saveFocusState calls:
      ComposerFocusManager.resetReadyToFocus(uniqueModalId);
      In src/libs/ComposerFocusManager.ts, resetReadyToFocus creates an unresolved promise in promiseMap keyed to that uniqueModalId.
    2. When a modal is dismissed normally, handleDismissModal() is invoked when !isVisible && wasVisible inside the useEffect on line 176:
      if (!isVisible && wasVisible) {
          handleDismissModal();
      }
      handleDismissModal() calls ComposerFocusManager.setReadyToFocus(uniqueModalId), which resolves and deletes the entry in promiseMap.
    3. However, when an action causes immediate navigation that unmounts the modal screen while isVisible is still true (such as confirming workspace deletion in Workspace Settings), the modal unmounts directly while isVisible remains true.
    4. As a result, the !isVisible && wasVisible transition never fires. BaseModal's unmount cleanup effect runs:
      useEffect(
          () => () => {
              if (!shouldCallHideModalOnUnmount.current) {
                  return;
              }
              hideModalCallbackRef.current?.(true);
          },
          [],
      );
      hideModal() executes ComposerFocusManager.refocusAfterModalFullyClosed(uniqueModalId, restoreFocusType), but it never calls handleDismissModal() or ComposerFocusManager.setReadyToFocus(uniqueModalId).
    5. Consequently, promiseMap retains an unresolved promise keyed to that unmounted modal indefinitely.
    6. When the user later right-clicks a comment and selects Edit comment, focusComposerWithDelay (src/libs/focusComposerWithDelay/index.ts:59) executes:
      await Promise.all([ComposerFocusManager.isReadyToFocus(), isWindowReadyToFocus()]);
      Because ComposerFocusManager.isReadyToFocus() awaits the dangling promise in promiseMap, it blocks indefinitely and the composer input is never focused.

    What changes do you think we should make in order to solve the problem?

    1. In src/components/Modal/BaseModal.tsx:
      Ensure handleDismissModal() is called during unmount cleanup when shouldCallHideModalOnUnmount.current is true:
      useEffect(
          () => () => {
              if (!shouldCallHideModalOnUnmount.current) {
                  return;
              }
              handleDismissModal();
              hideModalCallbackRef.current?.(true);
          },
          [],
      );
    2. In src/libs/ComposerFocusManager.ts:
      In restoreFocusState(id) or when cleaning up modals, call setReadyToFocus(id) to resolve and remove any dangling promise associated with that id:
      function restoreFocusState(id: ModalId, shouldIgnoreFocused = false, restoreFocusType: RestoreFocusType = CONST.MODAL.RESTORE_FOCUS_TYPE.DEFAULT, isInUploadingContext = false) {
          if (!id) {
              return;
          }
          setReadyToFocus(id);
          if (!activeModals.length) {
              return;
          }
      This guarantees that no modal unmount or navigation transition leaves an unresolved promise in ComposerFocusManager.

    What alternative solutions did you explore? (Optional)

    Adding arbitrary setTimeout delays in ReportActionCompose or focusComposerWithDelay. This was rejected because it does not resolve the root lifecycle issue in BaseModal / ComposerFocusManager and introduces timing flakes across platforms.

    Tests

    1. Open Expensify Web on Chrome.
    2. Navigate to Workspaces and ensure 2 workspaces exist.
    3. Delete 1 workspace (Workspace Settings > More features / Delete workspace > Confirm).
    4. Navigate to Spend > Reports.
    5. Click FAB > Create report.
    6. Type a message and submit comment.
    7. Right-click on the comment and click Edit comment.
    8. Verify the edit comment input is immediately in focus with the cursor placed at the end.
  18. aion-citadel-forge commented on Nov 12, 2026

    @aion-citadel-forge

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    On Web, after deleting a workspace (or closing any modal that unmounts while isVisible is true), navigating to Spend > Reports, creating or opening a report, commenting on the empty report, right-clicking on the comment, and clicking Edit comment, the edit comment composer input does not receive focus.

    What is the root cause of that problem?

    In src/components/Modal/BaseModal.tsx:

    1. When a modal opens, saveFocusState calls:
      ComposerFocusManager.resetReadyToFocus(uniqueModalId);
      In src/libs/ComposerFocusManager.ts, resetReadyToFocus creates an unresolved promise in promiseMap keyed to that uniqueModalId.
    2. When a modal is dismissed normally, handleDismissModal() is invoked when !isVisible && wasVisible inside the useEffect on line 176:
      if (!isVisible && wasVisible) {
          handleDismissModal();
      }
      handleDismissModal() calls ComposerFocusManager.setReadyToFocus(uniqueModalId), which resolves and deletes the entry in promiseMap.
    3. However, when an action causes immediate navigation that unmounts the modal screen while isVisible is still true (such as confirming workspace deletion in Workspace Settings), the modal unmounts directly while isVisible remains true.
    4. As a result, the !isVisible && wasVisible transition never fires. BaseModal's unmount cleanup effect runs:
      useEffect(
          () => () => {
              if (!shouldCallHideModalOnUnmount.current) {
                  return;
              }
              hideModalCallbackRef.current?.(true);
          },
          [],
      );
      hideModal() executes ComposerFocusManager.refocusAfterModalFullyClosed(uniqueModalId, restoreFocusType), but it never calls handleDismissModal() or ComposerFocusManager.setReadyToFocus(uniqueModalId).
    5. Consequently, promiseMap retains an unresolved promise keyed to that unmounted modal indefinitely.
    6. When the user later right-clicks a comment and selects Edit comment, focusComposerWithDelay (src/libs/focusComposerWithDelay/index.ts:59) executes:
      await Promise.all([ComposerFocusManager.isReadyToFocus(), isWindowReadyToFocus()]);
      Because ComposerFocusManager.isReadyToFocus() awaits the dangling promise in promiseMap, it blocks indefinitely and the composer input is never focused.

    What changes do you think we should make in order to solve the problem?

    1. In src/components/Modal/BaseModal.tsx:
      Ensure handleDismissModal() is called during unmount cleanup when shouldCallHideModalOnUnmount.current is true:
      useEffect(
          () => () => {
              if (!shouldCallHideModalOnUnmount.current) {
                  return;
              }
              handleDismissModal();
              hideModalCallbackRef.current?.(true);
          },
          [],
      );
    2. In src/libs/ComposerFocusManager.ts:
      In restoreFocusState(id) or when cleaning up modals, call setReadyToFocus(id) to resolve and remove any dangling promise associated with that id:
      function restoreFocusState(id: ModalId, shouldIgnoreFocused = false, restoreFocusType: RestoreFocusType = CONST.MODAL.RESTORE_FOCUS_TYPE.DEFAULT, isInUploadingContext = false) {
          if (!id) {
              return;
          }
          setReadyToFocus(id);
          if (!activeModals.length) {
              return;
          }
      This guarantees that no modal unmount or navigation transition leaves an unresolved promise in ComposerFocusManager.

    What alternative solutions did you explore? (Optional)

    Adding arbitrary setTimeout delays in ReportActionCompose or focusComposerWithDelay. This was rejected because it does not resolve the root lifecycle issue in BaseModal / ComposerFocusManager and introduces timing flakes across platforms.

    Tests

    1. Open Expensify Web on Chrome.
    2. Navigate to Workspaces and ensure 2 workspaces exist.
    3. Delete 1 workspace (Workspace Settings > More features / Delete workspace > Confirm).
    4. Navigate to Spend > Reports.
    5. Click FAB > Create report.
    6. Type a message and submit comment.
    7. Right-click on the comment and click Edit comment.
    8. Verify the edit comment input is immediately in focus with the cursor placed at the end.
  19. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Nov 14, 2026
  20. melvin-bot commented on Nov 14, 2026

    @melvin-bot

    📣 @wildan-m 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

    Offer link
    Upwork job
    Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
    Keep in mind: Code of Conduct | Contributing 📖

  21. parasharrajat commented on Nov 14, 2026

    @parasharrajat
    Member

    Assigned Wildman based on this #104360 (comment)

  22. wildan-m commented on Nov 15, 2026

    @wildan-m
    Contributor

    on it

  23. wildan-m commented on Nov 15, 2026

    @wildan-m
    Contributor

    @parasharrajat the PR is ready for review: #106944

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions