This provides a proper fix for the pendingGenerateTimeout invalid response issue in #177 & #184. This is done by hijacking abandoned pending generates, where the originating request has already responded (using a timeout).
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.
This provides a proper fix for the
pendingGenerateTimeout
invalid response issue in #177 & #184. This is done by hijacking abandoned pending generates, where the originating request has already responded (using a timeout).