fix: feishu reply context truncation + task events NULL data crash - #508
Merged
viettranx merged 2 commits intoMar 27, 2026
Conversation
500 bytes is too short for CJK/Unicode text (each accented char = 2-3 bytes, so ~250 real characters). Increase to 2000 so reply context is not aggressively truncated.
ListTaskEvents and ListTeamEvents crash with "unsupported Scan,
storing driver.Value type <nil> into type *json.RawMessage" when the
data column is NULL. Use COALESCE(data, '{}') to return an empty JSON
object instead.
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
replyContextMaxLenfrom 500 → 2000. The old limit was too aggressive for CJK/Unicode text (500 bytes ≈ ~250 Vietnamese/Chinese characters), causing reply context to be truncated with...ListTaskEventsandListTeamEventscrash withsql: Scan error on column index 5, name "data": unsupported Scan, storing driver.Value type <nil> into type *json.RawMessagewhen thedatacolumn is NULL. Fix withCOALESCE(data, '{}')Test plan
datacolumn — should load without error