ehmicky
ehmicky
Note: this problem was reported [here as well](https://answers.netlify.com/t/running-netlify-dev-in-postbuild-causes-lingering-processes-warning/33866/2).
> they just don't panic At the moment, the build in Netlify is not panicking. Currently, the only impact of lingering processes is the presence of this warning message in...
@mheffner From https://github.com/netlify/buildbot/issues/984, it appears that we currently terminate lingering processes. However, this is done as part of terminating the container it seems (so terminating it inside `@netlify/build` would be...
> Yeah, we don't currently terminate them in the build. [You're right, thanks for correcting](https://app.netlify.com/sites/mick/deploys/6048f9486f4741009d139a1d) (I implied the opposite in my previous comment, but this was incorrect). I agree we...
Hi @bahmutov, We've just released some improvements to this warning message which should make it clearer. The color is now yellow and the message has been improved. Also the detection...
Hi @redmagic, Thanks for reporting this. Could you please show the log lines between the two screenshots above? Thanks!
Interesting, this is happening during Functions bundling. I am transferring this bug to `@netlify/zip-it-and-ship-it`, which is responsible for this part of the build logic. @eduardoboucas @netlify-team-account-1 What are your thoughts...
Nice idea!
Hi @bomzj, Thanks for reporting this. This appears to be the same issue described in https://github.com/netlify/zip-it-and-ship-it/issues/135. Please let us know if the information in that issue are solving your problem.
Hi @mfanuzzi, It seems like `import.meta.url` in [this line of code](https://github.com/netlify/js-client/blob/56393851edd6a205bae3a82b145ebc7a849ad9e8/src/open_api.js?_pjax=%23js-repo-pjax-container%2C%20div%5Bitemtype%3D%22http%3A%2F%2Fschema.org%2FSoftwareSourceCode%22%5D%20main%2C%20%5Bdata-pjax-container%5D#L5) is `undefined`. This seems this bug might not be due to `js-client`, but to the bundling process done on...