[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

Bugreporter added a comment. This does not address the issue raised in {T136479#2338442 } - I'm going to file a new task for it. TASK DETAIL https://phabricator.wikimedia.org/T136479 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

VIGNERON added a comment. @Gehel very true. That said, it won't hurt performances either and what about all the other problems of not being able to stop a query? (I hate when I have to restart my browser and/or computer who froze just because I dumbly forgot to remove a `wdt:P279*`) TASK

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

Bugreporter added a comment. @WikidataFacts: Does this task requires upstream fix? TASK DETAIL https://phabricator.wikimedia.org/T136479 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Bugreporter Cc: Bugreporter, Maxlath, NoInkling,

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

Smalyshev added a comment. My concern here is that it will encourage very bad pattern of behavior - running a bad query, seeing it takes long, abandoning it, tweaking, running it again, etc. so that at the end the server ends up with 20 heavy queries running. Yes, I know you could just open a new

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

Nikki added a comment. If this ticket includes cancelling the query on the server, should we make a new ticket for simply being able to run a new query before the existing one has timed out? It used to be possible before the run button started being disabled, so it seems like making that possible

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

gerritbot added a comment. Change 316044 had a related patch set uploaded (by Smalyshev): Add ability to cancel queries https://gerrit.wikimedia.org/r/316044TASK DETAILhttps://phabricator.wikimedia.org/T136479EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

gerritbot added a comment. Change 316042 had a related patch set uploaded (by Smalyshev): Add URL to cancel running query https://gerrit.wikimedia.org/r/316042TASK DETAILhttps://phabricator.wikimedia.org/T136479EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To:

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

Edgars2007 added a comment.I usually introduce some error in query and then press Run :)TASK DETAILhttps://phabricator.wikimedia.org/T136479EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferences/To: Edgars2007Cc: Edgars2007, Jonas, Deskana, Smalyshev, Nikki, Aklapper,

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

Jonas added a comment. When I hit that problem I just press F5 to reload the page, because the query in the editor is still preserved. I am not sure if canceling the query is worth the effort at the moment, because of the strict Blazegraph execution limit. In the future when that

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

Nikki added a comment. I usually end up right clicking the tab and duplicating it, that way I don't lose what I currently have on the clipboard. :) I suppose refreshing the page would work too but I never trust browsers/pages to not lose something if I do that. Also, I didn't mention

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

Smalyshev added a comment. Another note: cancel requires POST support as it seems, which currently is not supported. Also, since we have more than one server, we need some kind of affinity on Varnish side, which I am not sure whether we have or not. @Deskana one query is probably no big

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

Deskana added a comment. Do we know that such queries have a big performance hit or cause undue strain on the servers? I agree that in an ideal world this feature would be useful, but if these queries are not causing any significant issues then practically speaking it may not be worth

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

WikidataFacts added a comment. @Smalyshev: Good to know. So the client would send the cancel request while the query `GET` request is still pending, and that would then return… 204 No Content? 408 Request Timeout? (I suppose it doesn’t matter – the client knows it canceled the query, it

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

Smalyshev added a comment. Looks like there is a way to do it: https://wiki.blazegraph.com/wiki/index.php/REST_API#queryId TASK DETAIL https://phabricator.wikimedia.org/T136479 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Smalyshev Cc:

[Wikidata-bugs] [Maniphest] [Commented On] T136479: Allow cancelling / aborting queries

Nikki added a comment. I wanted to ask for pretty much the same thing. :) I often make stupid mistakes that mean my query will either time out or return far too many results. It used to be possible to just click "Run" again, but now that button gets disabled until it returns results or