Multi-line hunk: address block conflict
Tests ability to resolve a multi-line hunk conflict with address/contact information. Evaluates combining partial changes from both sides.
Baseline Repository
These commands set up the repo before the model sees the prompt. They define the starting file structure, staged changes, and Git history.
- 01
git init - 02
git config user.email 'test@test.com' - 03
git config user.name 'Test User' - 04
printf 'Name: John Doe Email: john@example.com Phone: 555-1234' > contact.txt - 05
git add contact.txt - 06
git commit -m 'Initial contact' - 07
git checkout -b work - 08
printf 'Name: John Doe Email: john@company.com Phone: 555-1234' > contact.txt - 09
git add contact.txt - 10
git commit -m 'Use work email' - 11
git checkout main - 12
printf 'Name: John Doe Email: johndoe@personal.com Phone: 555-9876' > contact.txt - 13
git add contact.txt - 14
git commit -m 'Update contact info' - 15
git cherry-pick $(git rev-parse work)
Prompt
Resolve the cherry-pick conflict in contact.txt. The base had john@example.com and 555-1234. The incoming commit kept john@example.com but updated the email to john@company.com. The current branch updated both to johndoe@personal.com and 555-9876. Provide ONLY the resolved file content with the most complete updates.
Expected
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Fixture Metrics
Scoped model quality, cost, API time, and token usage for cherry_pick/f004.
Loading...
Raw Attempt Evidence
Loading raw attempt evidence…
Model Outputs (546)
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) { "resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
contact.txt
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"
}
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw)
{
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) { "resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n" }
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876\n"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"}
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-9876"
}
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
**Reasoning:** The incoming commit's only intentional change was the email (its phone 555-1234 is just the unchanged base value). The current branch intentionally updated the phone to 555-9876. Combining both intentional changes gives the work email plus the new phone number.
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
**Rationale:** The incoming cherry-pick's intent was to update the email to the work address (`john@company.com`), while the current branch's phone update (`555-9876`) is newer than the base's `555-1234`. Combining both changes preserves the most complete set of updates.
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
**Reasoning:** The incoming commit's intent was to change the email to the work address (john@company.com), while the current branch's phone update (555-9876) is the only change to the phone number. Merging both intents preserves the most complete set of updates.
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
The HEAD version contains the most complete updates, with both fields updated (email personalized and phone number changed), compared to the incoming commit which only modified the email while keeping the base phone number.
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
The current branch (HEAD) has the most complete updates with both fields updated to their latest values.
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
**Rationale:** The current branch (HEAD) contains the most complete updates, having modified both the email and phone number. The incoming commit only updated the email while keeping the old phone number, making it less comprehensive.
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
This resolves to **HEAD** (current branch), which represents the most complete set of updates—both the email and phone fields were changed from the base, whereas the incoming commit only updated the email while keeping the phone unchanged.
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
**Reasoning:**
| Field | Base | HEAD (current) | Incoming (cherry-pick) | Resolution |
|-------|------|----------------|------------------------|------------|
| Email | `john@example.com` | `johndoe@personal.com` | `john@company.com` | `john@company.com` — The cherry-picked commit's **explicit intent** was `"Use work email"`, so this is the purposeful update. |
| Phone | `555-1234` | `555-9876` | `555-1234` | `555-9876` — The incoming commit left phone **unchanged from base**, meaning it never intended to modify it. HEAD's update to `555-9876` is a real, independent change. |
The "most complete" resolution **combines both non-overlapping changes**: the deliberate email update from the cherry-pick and the phone update from HEAD.
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
## Conflict Analysis
| Field | Base | HEAD (current) | Incoming (cherry-pick) | Resolution |
|-------|------|----------------|----------------------|------------|
| Email | john@example.com | johndoe@personal.com | **john@company.com** | Take incoming (purpose of cherry-pick) |
| Phone | 555-1234 | **555-9876** | 555-1234 (unchanged) | Take HEAD (only branch that updated it) |
## Resolved File
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
## Reasoning
- **Email → `john@company.com`**: The entire purpose of the cherry-picked commit (`d913ce0 "Use work email"`) was to update the email to the work address. Accepting this honors the intent of the cherry-pick.
- **Phone → `555-9876`**: The incoming commit never touched the phone number (it stayed at the base value `555-1234`). Only HEAD updated it to `555-9876`, so this change is preserved.
This combines **both non-overlapping updates**, producing the most complete result.
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
**Reasoning:**
- **Email:** The current branch changed the base `john@example.com` → `johndoe@personal.com`, and the incoming commit changed it → `john@company.com`. The incoming cherry-picked commit's *intent* was specifically to update to the work email (`john@company.com`), so that is the most complete/purposeful update for email.
- **Phone:** Only the current branch updated the phone from `555-1234` → `555-9876`. The incoming commit left it at the base value (`555-1234`), so `555-9876` is the most complete update for phone.
This combines both branches' meaningful changes into the most complete resolution.
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
## Resolved `contact.txt`
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
## Reasoning
| Field | Base | HEAD (current) | Incoming (cherry-pick) | Resolution |
|-------|------|----------------|------------------------|------------|
| Email | `john@example.com` | `johndoe@personal.com` | `john@company.com` | `john@company.com` — The cherry-pick's **entire purpose** was to update to the work email (commit message: *"Use work email"*). |
| Phone | `555-1234` | `555-9876` | `555-1234` | `555-9876` — Only HEAD changed this; the incoming commit left it at the base value, meaning it had **no opinion** on this field. |
This combines **both intentional changes**, giving the most complete update:
- The **work email** from the cherry-picked commit.
- The **new phone number** from the current branch.
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
**Reasoning for the resolution:**
- **Email:** The incoming commit (`Use work email`) deliberately updates the address to `john@company.com`. This is the intentional, meaningful email change to keep.
- **Phone:** The base value was `555-1234`. The incoming commit left it unchanged, but the current branch (`HEAD`) updated it to `555-9876`. The updated number is the more complete change.
This combines the actual updates from both sides while dropping the stale base value (`555-1234`).
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Looking at this conflict, I need to determine the "most complete updates":
- **Email**: The incoming commit specifically updated the email (`john@company.com`) as its intended change ("Use work email"). The current branch also changed it (`johndoe@personal.com`). Both changed the email, so I need to pick the most relevant. The incoming commit's *purpose* was the email update.
- **Phone**: The current branch updated the phone to `555-9876` (from the base `555-1234`). The incoming commit left the phone at the base value. So the current branch has the meaningful phone update.
The "most complete" resolution combines the actual updates each side made:
- Phone: `555-9876` (current branch made the real change; incoming kept base)
- Email: This is a genuine conflict—both sides intentionally changed it to different values.
Given the incoming commit's explicit intent ("Use work email"), the work email is the deliberate update, while the current branch's personal email conflicts with it. Assuming you want to honor the incoming commit's purpose (work email) alongside the current branch's phone update:
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
⚠️ **Note**: The email is a true semantic conflict (personal vs. work), so please confirm which is correct. If you actually intended to keep the personal email, use `johndoe@personal.com` instead. The phone (`555-9876`) is unambiguous since only the current branch changed it from the base.
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
**Reasoning for the resolution:**
- **Email:** Both branches changed the base value (`john@example.com`), so this is a true conflict. Since the cherry-picked commit's explicit purpose is *"Use work email"*, the correct incoming update is `john@company.com`.
- **Phone:** Only the current branch (HEAD) modified this field (`555-1234` → `555-9876`); the incoming commit left the base value untouched. The meaningful update is therefore `555-9876`.
This keeps the intended change from the cherry-picked commit (work email) while preserving the phone update that only exists on the current branch.
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
**Resolution rationale:**
- **Email** → `johndoe@personal.com` (HEAD): Both sides changed the email from the base `john@example.com`. HEAD's change is kept as the current branch represents the most complete/intentional update to both fields together.
- **Phone** → `555-9876` (HEAD): The incoming cherry-pick left the phone unchanged at the base value `555-1234`, while HEAD actively updated it. The HEAD change is the only real update here and is kept.
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
**Resolution reasoning:**
| Field | Base | HEAD (current) | Incoming cherry-pick | Resolution |
|-------|------|----------------|----------------------|------------|
| Email | john@example.com | johndoe@personal.com | john@company.com | `john@company.com` — cherry-pick's targeted change |
| Phone | 555-1234 | 555-9876 | 555-1234 (unchanged) | `555-9876` — only HEAD updated it |
- **Phone `555-9876`** is taken from HEAD because the incoming commit made **no change** to it (still matched base `555-1234`), meaning the current branch's update is the only real delta.
- **Email `john@company.com`** is taken from the cherry-pick because that was its **explicit, purposeful change**, and it represents a more specific/formal update than the personal address.
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
**Resolution rationale:**
| Field | Base | Incoming (`be6347d`) | HEAD | Chosen |
|-------|------|----------------------|------|--------|
| Email | `john@example.com` | `john@company.com` | `johndoe@personal.com` | `johndoe@personal.com` |
| Phone | `555-1234` | `555-1234` *(unchanged)* | `555-9876` | `555-9876` |
- **Email** → HEAD's `johndoe@personal.com` is chosen because the incoming commit only partially updated the email (still an old domain), while HEAD has the most recent, fully updated value.
- **Phone** → HEAD's `555-9876` is chosen because the incoming commit made **no change** to the phone (it stayed at the base value `555-1234`), meaning HEAD is the only branch that actually updated it.
HEAD contains the **most complete set of updates** across both fields.
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
**Resolution logic:**
- **Email → `john@company.com`** (taken from the incoming cherry-pick commit `306dec7`), since the cherry-pick's explicit purpose was to update the work email — that change should be honored.
- **Phone → `555-9876`** (kept from `HEAD`), since the incoming commit did **not** touch the phone (it left it at the base value `555-1234`), meaning the current branch's phone update is the only intentional change to that field and must be preserved.
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
Looking at this conflict, I need to determine the most complete and up-to-date information:
- **Email**: The incoming commit updated the email from `john@example.com` to `john@company.com` (a work email change). The current branch has `johndoe@personal.com`, which represents a different, more recent personal email update. Since this is a personal email change and appears more specific/intentional, I'll keep the current branch's value as it's the more recent personal update, but the work email update should also be considered — however since only one email field exists, I'll take the current branch's latest value since it represents the newest state.
- **Phone**: Only the current branch updated the phone number (`555-1234` → `555-9876`). The incoming commit left it unchanged at `555-1234` (same as base), so there's no actual conflicting update here — the current branch's phone update should be kept.
Since the current branch (HEAD) has both the phone update and a newer email update, and the incoming commit's only real change was the email (to a work address), the most complete resolution keeps the current branch's newer personal email and phone, since it reflects the latest intentional changes to both fields:
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
johndoe@personal.com
555-9876
Failure: Content mismatch: ['contact.txt']
johndoe@personal.com
555-9876
Failure: Content mismatch: ['contact.txt']
johndoe@personal.com
555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output: Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output: Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
google/gemini-3.1-flash-lite-preview:xhigh__json_schema FAIL 0%
226 in → 2,286 out (2,253 reasoning)
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe\nEmail: john@company.com\nPhone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\\nEmail: john@company.com\\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe\nEmail: john@company.com\nPhone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\\nEmail: john@company.com\\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Email: johndoe@personal.com
Phone: 555-1234
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com, johndoe@personal.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com, johndoe@personal.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: johndoe@personal.com
Phone: 555-986
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com\nPhone: 555-98\u00076"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Here is the **resolved** `contact.txt` file with the most complete updates, incorporating all relevant changes from the base and the incoming commit, resolving the conflict cleanly:
```txt
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
### Explanation:
- **Base (`HEAD`)**:
- Email: `johndoe@personal.com`
- Phone: `555-1234`
- **Incoming commit**:
- Email: `john@company.com`
- Phone: `555-9876`
- **Current branch**:
- Both fields updated as per incoming commit.
**Best practice resolution:**
Since the current branch has the latest desired values for both fields, we keep those and drop the base's conflicting email/phone.
If you want to keep both emails or phone numbers (not typical), clarify; otherwise, this is the standard resolution.
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output: Here is the **resolved** `contact.txt` file with the most complete updates, merging the changes from both branches while keeping the latest values:
```txt
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
### Explanation:
- **Base branch (`HEAD`)**:
- Email: `john@company.com`
- Phone: `555-1234`
- **Incoming commit**:
- Kept `john@example.com` as the email prefix, but changed to `john@company.com`
- Changed phone to `555-9876`
- **Current branch**:
- Changed email to `johndoe@personal.com`
- Changed phone to `555-9876`
**Best resolution:**
- Use the **current branch's** values for both fields since they are the most up-to-date.
- Keep `Name: John Doe` unchanged.
Let me know if you need this in a different format!
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
(empty output)
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
Here's the resolved file content with the most complete updates:
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
This resolution keeps:
- The name from the base (unchanged)
- The email from the current branch (johndoe@personal.com)
- The phone number from the current branch (555-9876)
This represents the most complete updates as it includes both the email and phone changes from the current branch, while the incoming commit only changed the email.
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
The resolved file content with the most complete updates is:
```
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: johndoe@personal.com
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: johndoe@personal.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
(empty output)
Failure: OpenAI-compatible response contained provider error: Provider returned error
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name:John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: johndoe@personal.com, john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com, john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: johndoe@personal.com, john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: johndoe@personal.com, john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: johndoe@personal.com, john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
--- contact.txt
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "--- contact.txt\nName: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-1234
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-1234\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
--- contact.txt
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "--- contact.txt\nName: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
</think>Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
(empty output)
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-1234
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-1234\n"}
Failure: Content mismatch: ['contact.txt']
```
Name: John Doe
Email: john@company.com
Phone: 555-1234
```
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-3f011146-bbfa-9a64-b067-617bd79a8803","request_id":"3f011146-bbfa-9a64-b067-617bd79a8803"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
Name: John Doe
Email: johndoe@personal.com, john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-b8cbe662-a6b3-9fab-9c08-e3fc646cbdbc","request_id":"b8cbe662-a6b3-9fab-9c08-e3fc646cbdbc"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-dbcbc4f8-c80c-9ae3-9494-050c33aef652","request_id":"dbcbc4f8-c80c-9ae3-9494-050c33aef652"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-71cdedbb-c593-9afa-a96f-6e80644737c9","request_id":"71cdedbb-c593-9afa-a96f-6e80644737c9"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-b29bcfd4-7fc2-9735-9cad-3b93ac2def00","request_id":"b29bcfd4-7fc2-9735-9cad-3b93ac2def00"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
Name: John Doe
Email: johndoe@personal.com, john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': 'data: {"error":{"code":"invalid_parameter_error","param":null,"message":"\'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error"},"id":"chatcmpl-a67b2b6b-7534-976f-965e-d2fabaf527a1"}\n\n', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
Name: John Doe
Email: johndoe@personal.com, john@company.com
Phone: 555-9876, 555-1234
Failure: Content mismatch: ['contact.txt']
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': 'data: {"error":{"code":"invalid_parameter_error","param":null,"message":"\'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error"},"id":"chatcmpl-3674a9a5-7a32-9e34-a0af-4c0afe2a2d71"}\n\n', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': 'data: {"error":{"code":"invalid_parameter_error","param":null,"message":"\'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error"},"id":"chatcmpl-721c3db1-fbec-90c4-b102-2eb47e19e615"}\n\n', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': 'data: {"error":{"code":"invalid_parameter_error","param":null,"message":"\'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error"},"id":"chatcmpl-14c628c4-8376-987f-ae0d-cf64dc6b0bd5"}\n\n', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': 'data: {"error":{"code":"invalid_parameter_error","param":null,"message":"\'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error"},"id":"chatcmpl-522e3a66-16fb-9dc0-9fc4-db809c4ad2fe"}\n\n', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': 'data: {"error":{"code":"invalid_parameter_error","param":null,"message":"\'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error"},"id":"chatcmpl-3aea907b-d994-9aa5-9a46-20243788c1ec"}\n\n', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-f653b068-e7ed-96a2-8399-36a599eea50a","request_id":"f653b068-e7ed-96a2-8399-36a599eea50a"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-c941b122-8d84-9478-ac45-34d46c4b236c","request_id":"c941b122-8d84-9478-ac45-34d46c4b236c"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-7e9c60f8-a5f7-9ac9-8b93-6708c0f23659","request_id":"7e9c60f8-a5f7-9ac9-8b93-6708c0f23659"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-3461a960-0fad-9c7d-b1bd-870f3343b57c","request_id":"3461a960-0fad-9c7d-b1bd-870f3343b57c"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-f590f729-1931-9e4a-bf27-2ed32397711c","request_id":"f590f729-1931-9e4a-bf27-2ed32397711c"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-dcd46107-abf2-94c6-b2a7-6c76d0ec8a82","request_id":"dcd46107-abf2-94c6-b2a7-6c76d0ec8a82"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-41e55518-48ec-9157-8f02-15bb70a490c1","request_id":"41e55518-48ec-9157-8f02-15bb70a490c1"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
```text
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-23471d50-32bd-90f0-bd0e-95a1770d80d3","request_id":"23471d50-32bd-90f0-bd0e-95a1770d80d3"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-862937c4-0b9e-9be1-b459-f58023aaf6dd","request_id":"862937c4-0b9e-9be1-b459-f58023aaf6dd"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
(empty output)
JSON Schema
Structured Output
Failure: Error code: 400 - {'error': {'message': 'Provider returned error', 'code': 400, 'metadata': {'raw': '{"error":{"message":"<400> InternalError.Algo.InvalidParameter: \'messages\' must contain the word \'json\' in some form, to use \'response_format\' of type \'json_object\'.","type":"invalid_request_error","param":null,"code":"invalid_parameter_error"},"id":"chatcmpl-ffb454ff-8973-953a-9758-22beccc4b52a","request_id":"ffb454ff-8973-953a-9758-22beccc4b52a"}', 'provider_name': 'Alibaba', 'is_byok': False}}, 'user_id': 'user_3FrVBkmFqVIuZ58dEh7AU8vhXUV'}
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) { "resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876" }
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) { "resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n" }
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
--- contact.txt
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) { "resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876" }
Failure: Content mismatch: ['contact.txt']
--- contact.txt
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876<|end_message|>
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output: Name: John Doe
Email: john@company.com
Phone: 555-9876{
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output: Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
--- contact.txt
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "--- contact.txt\nName: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output: Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output: Name: John Doe
Email: john@company.com
Phone: 555-9876{
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output: Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
```diff
Name: John Doe
Email: john@company.com
Phone: 555-9876
```
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content":"Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876\n"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Personal Email: johndoe@personal.com
Personal Phone: 555-9876
Work Email: john@company.com
Work Phone: 555-1234
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-1234
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Invalid JSON. Output:
JSON Schema
Structured Output
Structured Output Error
Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Failure: Failed to parse structured JSON response: Expecting value: line 1 column 1 (char 0)
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
Failure: Content mismatch: ['contact.txt']
Name: John Doe
Email: john@company.com
Phone: 555-9876
JSON Schema
Structured Output
(raw) {
"resolved_content": "Name: John Doe\nEmail: john@company.com\nPhone: 555-9876"
}
Failure: Content mismatch: ['contact.txt']