Closed noahseger closed 1 year ago
Hey @noahseger, thanks for reporting. What version of twirpscript are you running?
I think I may have found a lead here: https://github.com/nodejs/help/issues/2663. I'll put out a release switching to process.stdin
usage. Once I release that, if you could let me know if the issue stops or if you continue to see it, I'd really appreciate it.
Hi @tatethurston , thanks for checking it out! We're running 0.0.61
, and can definitely let you know whether or not it stops after that lands. This framework is the best 🤘
Awesome thanks Noah, I’ll let you know when I publish
This is fixed in 0.0.66. LMK if you run into any issues!
Thanks @tatethurston! This passed our CI so we'll land it and watch for the error over the next week 🎉
Thanks @noahseger!
@noahseger how has the incidence of this error looked after 0.0.66?
Hey Tate, seems super solid since we upgraded. Thanks again 🙌
On Mon, Dec 5, 2022, 11:25 PM Tate Thurston @.***> wrote:
@noahseger https://github.com/noahseger how has the incidence of this error looked after 0.0.66?
— Reply to this email directly, view it on GitHub https://github.com/tatethurston/TwirpScript/issues/208#issuecomment-1338782712, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK5MYCDDJ6OKONV562R5A33WL3E6PANCNFSM6AAAAAASCV2VNE . You are receiving this because you were mentioned.Message ID: @.***>
Awesome, thanks Noah
Similar to #7, we've seen
stdin
fail as the number of protobufs we're processing has increased:Running under Node 16 in GitHub Actions:
All I've found so far is https://stackoverflow.com/questions/40362369/stdin-read-fails-on-some-input, and I don't know if you have the flexibility to read synchronously from
/dev/stdin
for portability.