-
-
Notifications
You must be signed in to change notification settings - Fork 79.1k
Cron job result serialization fails on special characters in edit tool arguments #67488
Copy link
Copy link
Closed
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.ClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.ClawSweeper marked this issue as an existing queue_fix_pr work candidate.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.ClawSweeper found a high-confidence source-level issue reproduction.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.Very strong issue quality with high-confidence source-level or clear reproduction.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Bug Description
Cron job
daily-memory-reviewreportsExpected ',' or '}' after property value in JSON at position 492 (line 1 column 493)even though the agent task completes successfully.Reproduction
sessionTarget: isolatedanddelivery.mode: announceedittool on a markdown file containing:...)**...**)errorwith the JSON parse errorExpected Behavior
Job should be marked as
oksince the agent completed successfully and delivery was sent.Actual Behavior
lastRunStatus: "error"lastError: "Expected ',' or '}' after property value in JSON at position 492 (line 1 column 493)"lastDeliveryStatus: "delivered"(delivery actually succeeded)consecutiveErrors: 1Details
The error appears to occur in the cron framework's post-processing / result serialization step, not during agent execution. The JSON parse error at position 492 on line 1 suggests a single-line JSON string is being parsed and failing on special characters from the
edittool'soldText/newTextarguments.Environment
agentTurnpayload,isolatedsession,announcedelivery to TelegramCron Job State (from jobs.json)
{ "id": "621e8e50-da09-4ac1-bb47-8f1428af832a", "name": "daily-memory-review", "lastRunStatus": "error", "lastDurationMs": 120311, "lastDeliveryStatus": "delivered", "consecutiveErrors": 1, "lastError": "Expected ',' or '}' after property value in JSON at position 492 (line 1 column 493)" }