-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Labels
Description
What happened?
[streamText] Skipping unknown chunk type: response.created {
type: 'response.created',
sequence_number: 0,
response: {
id: 'resp_687526f40da08196a60673de49d44c27015db9a6d0e58461',
object: 'response',
created_at: 1752508149,
status: 'in_progress',
background: false,
error: null,
incomplete_details: null,
instructions: 'You are a helpful AI assistant that communicates using properly formatted markdown. Follow these strict formatting rules:\n' +
'\n' +
'MARKDOWN FORMATTING REQUIREMENTS:\n' +
'1. **Lists**: Always keep list items on the same line as the marker\n' +
' - ✅ CORRECT: "1. Lorem ipsum dolor sit amet..."\n' +
' - ❌ WRONG: "1. \\nLorem ipsum dolor sit amet..."\n' +
'\n' +
'2. **No line breaks after list markers**: Never put a line break immediately after numbered lists (1. 2. 3.) or bullet lists (- * +)\n' +
'\n' +
'3. **Proper list syntax**:\n' +
' - Numbered lists: "1. Content here"\n' +
' - Bullet lists: "- Content here" or "* Content here"\n' +
' - No extra spaces or line breaks between marker and content\n' +
'\n' +
'4. **Other markdown**: Use standard markdown for headers, emphasis, links, tables, and code blocks\n' +
'\n' +
'5. **Consistency**: Maintain consistent formatting throughout your response\n' +
'\n' +
'Remember: Keep list content on the same line as the list marker to ensure proper rendering.\n' +
'\n' +
'CHART CREATION INSTRUCTIONS (for chart requests only):\n' +
'\n' +
"ACCESSIBLE COLORS: ['#1E40AF', '#047857', '#D97706', '#DC2626', '#7C3AED', '#0E7490', '#C2410C', '#4D7C0F']\n" +
'ENSURE WCAG AA COMPLIANCE (4.5:1 contrast). USE PROPER LABELING.\n' +
'For 8+ items: cycle colors with patterns\n' +
'\n' +
'IMPORTANT: Follow these instructions when creating charts, but DO NOT mention accessibility features, color guidelines, or technical requirements in your response unless specifically asked. Just create the chart following these standards silently.',
max_output_tokens: null,
max_tool_calls: null,
model: 'o4-mini-2025-04-16',
output: [],
parallel_tool_calls: true,
previous_response_id: null,
reasoning: { effort: 'medium', summary: 'detailed' },
service_tier: 'auto',
store: true,
temperature: 1,
text: { format: [Object] },
tool_choice: 'auto',
tools: [ [Object] ],
top_logprobs: 0,
top_p: 1,
truncation: 'disabled',
usage: null,
user: 'jb61KhsbMXPjOQCgOFhPCTIhPAE3',
metadata: {}
}
}
[streamText] Skipping unknown chunk type: response.in_progress {
type: 'response.in_progress',
sequence_number: 1,
response: {
id: 'resp_687526f40da08196a60673de49d44c27015db9a6d0e58461',
object: 'response',
created_at: 1752508149,
status: 'in_progress',
background: false,
error: null,
incomplete_details: null,
instructions: 'You are a helpful AI assistant that communicates using properly formatted markdown. Follow these strict formatting rules:\n' +
'\n' +
'MARKDOWN FORMATTING REQUIREMENTS:\n' +
'1. **Lists**: Always keep list items on the same line as the marker\n' +
' - ✅ CORRECT: "1. Lorem ipsum dolor sit amet..."\n' +
' - ❌ WRONG: "1. \\nLorem ipsum dolor sit amet..."\n' +
'\n' +
'2. **No line breaks after list markers**: Never put a line break immediately after numbered lists (1. 2. 3.) or bullet lists (- * +)\n' +
'\n' +
'3. **Proper list syntax**:\n' +
' - Numbered lists: "1. Content here"\n' +
' - Bullet lists: "- Content here" or "* Content here"\n' +
' - No extra spaces or line breaks between marker and content\n' +
'\n' +
'4. **Other markdown**: Use standard markdown for headers, emphasis, links, tables, and code blocks\n' +
'\n' +
'5. **Consistency**: Maintain consistent formatting throughout your response\n' +
'\n' +
'Remember: Keep list content on the same line as the list marker to ensure proper rendering.\n' +
'\n' +
'CHART CREATION INSTRUCTIONS (for chart requests only):\n' +
'\n' +
"ACCESSIBLE COLORS: ['#1E40AF', '#047857', '#D97706', '#DC2626', '#7C3AED', '#0E7490', '#C2410C', '#4D7C0F']\n" +
'ENSURE WCAG AA COMPLIANCE (4.5:1 contrast). USE PROPER LABELING.\n' +
'For 8+ items: cycle colors with patterns\n' +
'\n' +
'IMPORTANT: Follow these instructions when creating charts, but DO NOT mention accessibility features, color guidelines, or technical requirements in your response unless specifically asked. Just create the chart following these standards silently.',
max_output_tokens: null,
max_tool_calls: null,
model: 'o4-mini-2025-04-16',
output: [],
parallel_tool_calls: true,
previous_response_id: null,
reasoning: { effort: 'medium', summary: 'detailed' },
service_tier: 'auto',
store: true,
temperature: 1,
text: { format: [Object] },
tool_choice: 'auto',
tools: [ [Object] ],
top_logprobs: 0,
top_p: 1,
truncation: 'disabled',
usage: null,
user: 'jb61KhsbMXPjOQCgOFhPCTIhPAE3',
metadata: {}
}
}
also
[streamText] Skipping unknown chunk type: response.reasoning_summary_part.added {
type: 'response.reasoning_summary_part.added',
sequence_number: 110,
item_id: 'rs_687526f7c6d08196ab58e98b29ede4d4015db9a6d0e58461',
output_index: 1,
summary_index: 1,
part: { type: 'summary_text', text: '' }
}
[streamText] Skipping unknown chunk type: response.reasoning_summary_part.done {
type: 'response.reasoning_summary_part.done',
sequence_number: 214,
item_id: 'rs_687526f7c6d08196ab58e98b29ede4d4015db9a6d0e58461',
output_index: 1,
summary_index: 1,
part: {
type: 'summary_text',
text: '**Providing SQL for distribution analysis**\n' +
'\n' +
"I’m outlining steps to run an aggregation for distribution analysis using SQL code snippets. First, I’ll include a preview of the IP data and geo tables to get an idea of the structure. Next, I’ll show how to join the IP data with geo information to count visits by country and region. Finally, I’ll guide on interpreting the results, like identifying the top five countries. Since we can't run queries directly, I'll ensure the code is ready for the user to execute themselves."
}
}
[streamText] Skipping unknown chunk type: response.content_part.added {
type: 'response.content_part.added',
sequence_number: 217,
item_id: 'msg_687527c3768481968a28bf242f4e1a8d015db9a6d0e58461',
output_index: 2,
content_index: 0,
part: { type: 'output_text', annotations: [], logprobs: [], text: '' }
}
What did you expect to happen?
should they be handled / visualized on the ui ?
How did it happen?
used o4-mini