Fix SSE streaming responses contain duplicate 'data:' prefix breaking OpenAI compatibility

[Michael-A-Kuykendall]

Bug Description

Streaming responses contain data: data: which breaks OpenAI compatibility as described in #26.

Technical Details

The issue is in src/openai_compat.rs where SSE responses are being formatted with an extra data: prefix and newlines:

• Initial chunk: data: {json}\n\n should be just {json}
• Token chunks: data: {json}\n\n should be just {json}
• Final chunk: data: [DONE]\n\n should be just [DONE]

Expected Behavior

SSE streaming should send clean JSON objects without the duplicate data: prefix to maintain OpenAI API compatibility.

Reported by

@qlyoung in PR #49 (declined due to governance requirements but bug report is valid)

Priority

High - affects OpenAI API compatibility

[Michael-A-Kuykendall]

@qlyoung Thank you for the detailed bug report. I've created this issue to track the SSE formatting fix. Working on the solution now following our internal development process.

[qlyoung]

I didn't report this bug, it's a pure duplicate of #26. In that issue you said you committed a fix for it. Where's the fix?

[Michael-A-Kuykendall]

I am working it now, thanks for your continued patience.

[qlyoung]

To clarify - I'm trying to figure out which commit this statement is referencing:

Do you have the SHA?

[Michael-A-Kuykendall]

I am taking the time to make the corrections you suggested, I'll have it up shortly.

Thanks again for your help.

[qlyoung]

Just to be very clear, you are saying that the comment I quoted is incorrect, and no fix was ever committed. Right?

[Michael-A-Kuykendall]

Notably, I started to fix the tests and issues you rightfully noted were contrary to policies I am defining as the project matures, and then stumbled into a next of warnings which I cannot abide, warnings = sloppy code.

[Michael-A-Kuykendall]

The commit hash is 09744c2. You were right that no fix was previously committed despite my earlier claim.

The SSE bug is now actually fixed along with all the other issues you pointed out.

Thanks!
Mike

[Michael-A-Kuykendall]

Resolved in commit 09744c2. This was a duplicate of issue #26 which is also now fixed.

[Michael-A-Kuykendall]

Just to be very clear, you are saying that the comment I quoted is incorrect, and no fix was ever committed. Right?

Sunds right, and I believe the matter is settled.

Feel free to pull the hash now while I am bundling this and other changes for a new release to see for yourself. and I encourage you to continue to call me on my bullshit, running something with this much attention is 100% brand new to me, I appreciate your continued patience and understanding as I grow!