Problem

If by mistake I send a request that I know would timeout (ex: SELECT * { ?s ?p ?o }), the only way to correct it today is to open a new tab, copy/paste my request and correct it (ex: SELECT * { ?s ?p ?o } LIMIT 5). In the meantime, the first tab is still waiting for a certain timeout error, keeping resources unnecessarily busy. I assume that closing that tab doesn't cancel the request either.

Possible solution

Replace the #execute-button by a Cancel button while the query is executing, which would make a request to inform BlazeGraph that this query should be cancelled.