-
-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CICD automation fails with "node:internal/streams/readable:705" due to lack of stdin #575
Comments
Intersting i get the same error with webpack4 as well now:
What happens immediately after ℹ Bundle emulator ... |
Is there a MWE? Otherwise, we cannot look into this. (Also please make sure to use the bug template - there are crucial pieces of information missing in the OP, e.g., the OS, used versions, ...) |
[Package Version, OS, Browser, ...] DescriptionWith a shell Piral application I am able to build locally but not via CICD pipeline in the cloud, get an odd error, which looks like it may be related to something specific with the streams, perhaps stdin being piped? You can view the exact logs here: https://bitbucket.org/PvHIvz/piralmwe/pipelines/results/1 I am a little suspect of this:
causing issues Just some more research seems like others have had this issue with an unrelated package but worth digging: and check out their fix: |
Fixed with a patch: prob a better way then just commenting out since that will break other stuff i'm sure on desktop, but needs a think about how to put this into the piral-cli tooling. |
Yes, thanks for the MWE, the investigation, and the proposed fixed. Indeed, it seems that under certain circumstances The fix in the referenced repo works on this condition, e.g., they do child.stdin && child.stdin.pipe(process.stdin);
child.stdout && child.stdout.pipe(process.stdout); I think we should do the same. |
Hi I think there is a missing check stdin here, as I just upgraded our CI, and encountered it again: https://github.com/smapiot/piral/blob/develop/src/tooling/piral-cli/src/build/bundler-calls.ts#L118 |
Right - it was only changed in the dynamic part which is used, e.g., for debugging (there, actually, it is quite unlikely to occur anyway). Build is currently running - you can then check with the preview version of |
Giving
Seems like issue still prevails. |
Likely the problem is that from a CI server, there is no TTY, and so the stdin fails. I was able to workaround by:
Not sure how much user input is required in CLI outside of selecting the bundler, but most will probably configure from local and package-lock.json retains user selection for CI. Still though, IMHO a CLI shouldn't ever require TTY. |
Please make sure you indeed use the next version. If your patch worked beforehand, then the real |
@FlorianRappl I am not the OP here, but just jumping on a thread for having the same issue. From above, isn't |
@gitisz My comment is quite independent of that - it essentially states that either the next version is not correctly applied or the patch posted by the OP is not working. If you know for sure that the current version was applied then the latter must be the case (simple logic). Independent of that we still require a reproducible of the issue. There is a new preview version out, but without a reproducible it will be hard to verify the fix. |
Hi, sorry been super buys, I can confirm that using the next version solves the issue for us. @gitisz if it does not for you make sure you are pulling the latest version, also check your lock files to be sure they are not pinned. Also make sure you have one and only one bundler there, otherwise it fails back to the CLI input, which for obvious reasons will not work through automation. P |
Closing for now as the OP issue seems to be resolved - if we get a reproducible / this happens again in another environment we should have a new / separate issue for tracking purposes. |
Hi,
We are using the webpack5 plugin, and build's run fine locally, as well as locally in docker image, but when running via bitbucket cloud automation we get the below error. Ive spent a huge amount of time trying to debug this issue to no avail. It may have something to do with the std out/err or maybe file system, but its a bit of a black block.
as an aside ive tried webpack (4) as well as parcel, but i cant get either to work locally for other unrelated reasons.
ℹ [0003] Finding the version of "piral-native,piral,piral-core,piral-base" in "/app".
ℹ [0003] Finding the version of "piral-native,piral,piral-core,piral-base" in "/app".
ℹ [0003] Used versions: "0.15" and "0.15".
ℹ [0003] Removing the directory "/app/dist/emulator" ...
ℹ Bundle emulator ...
node:internal/streams/readable:705
dest.end();
^
TypeError: dest.end is not a function
at onend (node:internal/streams/readable:705:10)
at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
Node.js v18.12.1
error Command failed with exit code 1.
The text was updated successfully, but these errors were encountered: