64c2d704da
When the `max-row-limit` was hit, the goroutine reading from the results channel would stop reading from the channel, but it didn't signal to the sender that it was no longer reading from the results. This caused the sender to continue trying to send results even though nobody would ever read it and this created a deadlock. Include an `AbortCh` on the `ExecutionContext` that will signal when results are no longer desired so the sender can abort instead of deadlocking. |
||
|---|---|---|
| .. | ||
| config.go | ||
| config_test.go | ||
| handler.go | ||
| handler_test.go | ||
| listen.go | ||
| listen_test.go | ||
| response_logger.go | ||
| response_writer.go | ||
| service.go | ||