mirror of
https://github.com/jehna/humanify.git
synced 2026-04-27 01:26:00 +03:00
[GH-ISSUE #550] Breaks on long files (missing retry logic) #90
Labels
No labels
bug
enhancement
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/humanify#90
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @txkbir on GitHub (Jul 28, 2025).
Original GitHub issue: https://github.com/jehna/humanify/issues/550
i'm trying to process a 180k line file using my own OAI api key, but i consistently crash after 6-7% of the file has been processed (which takes me approximately 1.5h). i'm curious if someone can share insights on the most complex / largest projects that this tool has successfully handled?
@0xdevalias commented on GitHub (Jul 29, 2025):
@txkbir Are you able to provide details/specifics about what is crashing / what the error is?
And also what platform you're running on, node version, etc.
@txkbir commented on GitHub (Jul 29, 2025):
i get an
InternalServerError: 503 upstream connect error or disconnect/reset before headers. reset reason: connection termination at APIError.generate (file:///Users/takbir/.nvm/versions/node/v21.2.0/lib/node_modules/humanifyjs/node_modules/openai/error.mjs:62:20) at OpenAI.makeStatusError, which seems to mean it has nothing to do with the code but rather the api server. regardless, i'm still curious if my performance metrics sound reasonable based on what has been tested by this tool to handle.im running node v21.2.0 with npm v10.2.3 on macOS sequoia 15.5
@brianjenkins94 commented on GitHub (Jul 29, 2025):
My guess would be that's related to
humanify's dependency ofopenaibeing a major version behind what's current.@jehna commented on GitHub (Jan 25, 2026):
The underlying issue here is that there's no proper error handling logic on the 3rd party API clients. I'm thinking we'll probably need to add some kind of queue with retry logic to fix this.