3f7b53589c
Should fix the flood of buffer overflow errors we see from Supervisor. The one "change" this PR has, is that all the logs from the Docker container will now be coming from `stderr`, not `stdout`. I don't expect it to cause any problems, but it _is_ a change in behaviour nonetheless. Why do that? Because of the way Supervisor event listening works. This fix is based on the conversation at https://github.com/Supervisor/supervisor/issues/1417. Essentially that `stdout` should be reserved as a communication channel between Supervisord and the event-listener, and for logging, we should use `stderr`. **/test sanity** <!-- This is an auto-generated comment: Cypress test results --> > [!TIP] > 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉 > Workflow run: <https://github.com/appsmithorg/appsmith/actions/runs/9592028116> > Commit: 34a29eabc8dc82fb6a43b143e400d725d197a655 > <a href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=9592028116&attempt=1" target="_blank">Cypress dashboard</a>. > Tags: `@tag.Sanity` <!-- end of auto-generated comment: Cypress test results --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Refactor** - Improved logging by switching to `print` statements with explicit flushing for more reliable output handling. <!-- end of auto-generated comment: release notes by coderabbit.ai --> |
||
|---|---|---|
| .. | ||
| ansible | ||
| aws | ||
| aws_ami | ||
| digital_ocean | ||
| docker | ||
| helm | ||
| heroku | ||
| packer | ||