Timeout throwing an exception for something that has already been handled. about qbit HOT 4 CLOSED

Has this been resolved? I am facing this issue and don't know how to resolve.

from qbit.

I was able to resolve this. It could be that you are running into in another scenario which could be a bug or could be not using the API as expected. Can you create small test case that reproduces the bug? And the issue a PR with said test case.

from qbit.

HI Richard,
Thanks for your prompt reply. After debugging in my code I found that using "context.next()" is causing the issue. Since "context.next" ends the context and if we write response into context somewhere else in the code the exception will occur.For example

`Class Test {
function test_1(){
// some code
context.next();
}
function test_2(){
result = some_code;
context.response().end(result);

}`

from qbit.

Context? context.next()... Not sure any of this is QBit.

from qbit.