fix: is_early_exit 항상 true로 찍히는 버그 수정#121
Merged
Conversation
startTime이 Blocking 전환 시 덮어씌워져 elapsed가 항상 0에 가까워 is_early_exit가 항상 true로 찍히던 버그 수정 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
2 participants
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.
Summary
end_brake_session이벤트의is_early_exit가 항상true로 기록되던 버그 수정stopBlocking()에서startTime(Blocking 시작 시간)으로 elapsed를 계산 → 항상 ≈0 → 항상 early exit 판정sessionStartTime(실제 세션 시작 시간)을 사용하도록 변경Test plan
is_early_exit = false확인is_early_exit = true확인end_brake_session이벤트 값 검증🤖 Generated with Claude Code