Repository navigation
fix(yemot): in-memory call mode + log unsaved absences on hangup - #248
Merged
Merged
Conversation
…ngup - static stateless = false: calls are held in memory between Yemot requests again (single server node); the flow stays replay-safe so it can be turned back on later. - When a seminar caller hangs up before finishing, warn with the klass, teacher and the absent students already confirmed (nothing is saved), so a lost report can be traced. - Bump server/shared to buzz-code/nra-server#85 (per-request Yemot request/response log). Part of buzz-code/ops#36 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012GTictQRZtiJDmxx6EP9jx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by הדסה · project thread
Fixes buzz-code/ops#36
Changes
static stateless = falseinyemot-handler.service.ts. The Yemot handler keeps calls in memory between requests again, as before the replay mode. It's a temporary step: production runs a single server node, and the flow stays replay-safe (callStartedAt, writes after the last prompt), so it can be switched back on.server/sharedto feat(yemot): log each request's answers and the exact response sent nra-server#85 (cc6d2bf): one log line per Yemot request (answers + hangup flag) and per response (exact text sent).Tests
HangupError.server: 127 suites / 1250 tests pass,tsc --noEmitclean.Merge order
Merge buzz-code/nra-server#85 first, then re-pin
server/sharedto nra-servermainif that PR is squashed (the pinned commit is on its branch).Generated by Claude Code