fix: 修复grok输出json解析时，字符串切片下标错误

[Alkacid]

grok输出经常出错，排查之后是JSON解析有问题：

grok有时出现**{"key": "value"}**"这样的输出，即前后有**; 当前解析后的字符串切片下标有误，导致解析失败

验证：

test_str = """abc{"key": "value"}def"""

index = test_str.find("{")
parsed, end_index = json.JSONDecoder().raw_decode(test_str, index)

print(parsed)
print(test_str[index : end_index]) #修正后
print(test_str[index : index+end_index]) #修正前

输出：

{'key': 'value'}
{"key": "value"}
{"key": "value"}def

Summary by CodeRabbit

• Bug Fixes
  • Fixed search result parsing to correctly handle API responses with mixed content formats, preventing corrupted search results.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 57c19421-9eb7-452f-b0a2-e1d3949ffaf0

📥 Commits

Reviewing files that changed from the base of the PR and between 49eadcb and 69053f3.

📒 Files selected for processing (1)

• search-layer/scripts/search.py

---

📝 Walkthrough

Walkthrough

Fixed Grok result JSON extraction when responses contain non-JSON text prefix. The code now correctly uses the absolute end index from json.JSONDecoder.raw_decode() instead of incorrectly summing the start and end indices, preventing truncated or malformed JSON.

Changes

Grok JSON Parsing

Layer / File(s)	Summary
Core JSON Extraction Fix search-layer/scripts/search.py	Corrected substring slicing to use absolute end index from decoder instead of start_idx + end_idx, fixing JSON truncation when Grok response contains non-JSON prefix text.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A slice was wrong, indices did collide,
Addition of offsets made JSON subside,
Now raw_decode's true end shall guide,
JSON extracts pure—no more truncified! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title clearly describes the main fix: correcting index slicing errors in Grok JSON output parsing, which matches the changeset that fixes JSONDecoder result handling.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}