You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been investigating an issue where Execa does not return control to the parent process after launching a PostgreSQL setup script. The child process starts PostgreSQL successfully, and logs confirm that the database is running, but Execa remains blocked instead of completing execution.
To reproduce the issue, we created a minimal Docker setup where this happens consistently. The setup consists of a Node.js script (parent process) that spawns a Bash script (child process) responsible for initializing and starting PostgreSQL. The expectation is that Execa should return after PostgreSQL starts, but instead, it never does.
The text was updated successfully, but these errors were encountered:
We've been investigating an issue where Execa does not return control to the parent process after launching a PostgreSQL setup script. The child process starts PostgreSQL successfully, and logs confirm that the database is running, but Execa remains blocked instead of completing execution.
To reproduce the issue, we created a minimal Docker setup where this happens consistently. The setup consists of a Node.js script (parent process) that spawns a Bash script (child process) responsible for initializing and starting PostgreSQL. The expectation is that Execa should return after PostgreSQL starts, but instead, it never does.
The text was updated successfully, but these errors were encountered: