Andrew Clayton
Andrew Clayton
> However, it did not go all the way back to ~53MB. I waited for quite a bit, but remained at 109MB. I think it would be better to look...
Looking again with PHP 8.4.5. We do leak memory at startup/shutdown, but not too worried about that. However I don't currently see any per-request memory leak. I.e. the amount of...
I'm really only concerned with the memory usage of Unit. The PHP processes seem to start at around 10M then finish off at around 25M. If you continue your testing,...
Could you confirm exactly which process(es) it is that keeps growing in size? If it's the php application processes then you can always add something like ```json "limits": { "requests":...
> It would be great to know if occasionally killing "unit: router" is ok? I mean it's OK as in in gets restarted by the `main` unit process. Of course...
From @remicollet > and network connectivity is unavailable after the fetch Same issue with RPM build (which are done offline, especially required for reproducible builds) A solution is to vendor...
From @osokin > From [@remicollet](https://github.com/remicollet) > > > and network connectivity is unavailable after the fetch > > Same issue with RPM build (which are done offline, especially required for...
Would you mind splitting the python changes into a separate commit? (within this PR...)
Thanks @gourav-kandoria and the whitespace checker no longer complains :-)
> @ac000 have made the changes. Just one more thing to highlight. The exception as per asgi spect should be of subclass of OSError. (_If send() is called on a...