fix(js): support Uint8Array and Buffer JSONL sources in OpenAI batch instrumentation - #2479
Open
Mohd Quamar Tyagi (Tyagiquamar) wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When \jsonlRecords\ receives a resolved file source as a \Uint8Array, \ArrayBuffer, or Node \Buffer\ (for instance, when files are read via \ s.promises.readFile\ or fetched as array buffers), the previous type check \ ypeof resolvedFile === 'string'\ evaluated to false. As a result, the source reached the fallback check where it logged an invalid JSONL source error.
This PR updates \jsonlRecords\ to check for \Uint8Array, \ArrayBuffer, and \Buffer\ instances and decodes byte buffers using \TextDecoder\ so binary-backed JSONL file sources are parsed correctly.
Testing