answerAsk in ui/src/chat/state.ts:171-177 clears the pending question before it calls api.chatAnswer, and has no catch. Callers are ChatAskCard.vue:18-51 and ChatQuestionnaire.vue:136.
If the request fails, the question card disappears, the operator's answer is lost, and the turn keeps waiting with no message.
Done when: the question stays until the answer is accepted, a failure restores it with the answer still filled in, and the error shows on the card.
`answerAsk` in `ui/src/chat/state.ts:171-177` clears the pending question before it calls `api.chatAnswer`, and has no catch. Callers are `ChatAskCard.vue:18-51` and `ChatQuestionnaire.vue:136`.
If the request fails, the question card disappears, the operator's answer is lost, and the turn keeps waiting with no message.
Done when: the question stays until the answer is accepted, a failure restores it with the answer still filled in, and the error shows on the card.
Fixed in e9937ded and pushed. answerAsk now awaits api.chatAnswer first and clears streamingTurn.ask only on success, resolving true/false; on failure it sets the new askError ref and returns false, so the question card stays and the turn keeps waiting with the error visible. ChatAskCard shows askError as a ReadError with a Retry that resends the last answer (lastAnswer), keeps the typed reply filled in until the answer is accepted, and routes Deny/Always/Approve/choice buttons through the same answer() wrapper; ChatQuestionnaire submits through the card's send so questionnaire answers retry too. askError resets at turn start, on each new ask frame, and in selectSession. Verified: task check exited 0 on the committed tree.
Fixed in e9937ded and pushed. answerAsk now awaits api.chatAnswer first and clears streamingTurn.ask only on success, resolving true/false; on failure it sets the new askError ref and returns false, so the question card stays and the turn keeps waiting with the error visible. ChatAskCard shows askError as a ReadError with a Retry that resends the last answer (lastAnswer), keeps the typed reply filled in until the answer is accepted, and routes Deny/Always/Approve/choice buttons through the same answer() wrapper; ChatQuestionnaire submits through the card's send so questionnaire answers retry too. askError resets at turn start, on each new ask frame, and in selectSession. Verified: task check exited 0 on the committed tree.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
answerAskinui/src/chat/state.ts:171-177clears the pending question before it callsapi.chatAnswer, and has no catch. Callers areChatAskCard.vue:18-51andChatQuestionnaire.vue:136.If the request fails, the question card disappears, the operator's answer is lost, and the turn keeps waiting with no message.
Done when: the question stays until the answer is accepted, a failure restores it with the answer still filled in, and the error shows on the card.
Fixed in
e9937dedand pushed. answerAsk now awaits api.chatAnswer first and clears streamingTurn.ask only on success, resolving true/false; on failure it sets the new askError ref and returns false, so the question card stays and the turn keeps waiting with the error visible. ChatAskCard shows askError as a ReadError with a Retry that resends the last answer (lastAnswer), keeps the typed reply filled in until the answer is accepted, and routes Deny/Always/Approve/choice buttons through the same answer() wrapper; ChatQuestionnaire submits through the card's send so questionnaire answers retry too. askError resets at turn start, on each new ask frame, and in selectSession. Verified: task check exited 0 on the committed tree.Fixed in
e9937dedand pushed to main. Gate: task check exited 0 on the committed tree.