Timeline for Clicking on "Run Query" for a cached query before the cached results appear on the screen returns a json object instead of the query results
Current License: CC BY-SA 4.0
32 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 11 at 13:44 | history | edited | Franck Dernoncourt | CC BY-SA 4.0 |
added 165 characters in body
|
| Nov 11 at 1:11 | history | reopened |
Franck Dernoncourt Sonic the Anonymous Hedgehog NoDataDumpNoContribution John Omielan Jeremy |
||
| Nov 10 at 16:39 | comment | added | Franck Dernoncourt | @SonictheAnonymousHedgehog exactly. I ran into this issue well over a hundred times and I wasn't trying to click fast or push the system. Sometimes the cached results take a few seconds to load | |
| Nov 10 at 16:37 | vote | accept | Franck Dernoncourt | ||
| Nov 10 at 14:56 | comment | added | rene Mod | @SonictheAnonymousHedgehog sure, anyone that wants to spend time on it can suggest a fix. Not sure who merges these PRs nowadays. | |
| Nov 10 at 10:08 | history | edited | Sonic the Anonymous Hedgehog | CC BY-SA 4.0 |
added 117 characters in body; edited title
|
| Nov 10 at 10:05 | comment | added | Sonic the Anonymous Hedgehog | @rene It's very far from a rare edge case for users with slow Internet connections. I was able to reproduce the issue consistently on the first query in the above comment with example queries by throttling my Internet connection to 1 Mbps. | |
| Nov 10 at 9:25 | comment | added | Sonic the Anonymous Hedgehog | @rene Would a community PR that fixes the issue be accepted? | |
| Nov 10 at 8:45 | history | undeleted | Franck Dernoncourt | ||
| Nov 10 at 8:44 | history | deleted | Franck Dernoncourt | via Vote | |
| Nov 10 at 7:49 | comment | added | Franck Dernoncourt | @rene ok that's a [status-declined] then. Anyway can you post as an answer? The question is obviously clear. | |
| Nov 10 at 7:47 | comment | added | rene Mod | It is by-design because that is how it has been since 2010-ish and has worked 99,99999% of the time. The site needs javascript to work, it doesn't have a fallback for proper operation without javascript. Maybe the submit button should start out disabled and only be enabled when DataStackExchnage.ready runs but then again if time is spent it might be better spent on solving issues that are beneficial to more general use, not edge cases. | |
| Nov 10 at 7:38 | comment | added | Franck Dernoncourt | @rene "that endpoint only returns json to be processed by javascript" why is that by design? That's very poor UX. btw why not post as an answer? | |
| Nov 10 at 7:10 | comment | added | rene Mod | This has nothing todo with the result being cached or not. What you're seeing is caused by the javascript in query.js, specially the DataStackExchange.ready event, not having run yet. Until that ready event is executed the Run button is a plain form submit (the action attribute on the form points to it) to the query controller run endpoint and that endpoint only returns json to be processed by javascript. Conditions between your browser and data.se might cause slow resolving, loading and executing javascript, at least slower then your fabulous reaction time. status-bydesign | |
| Nov 10 at 5:50 | history | edited | Franck Dernoncourt | CC BY-SA 4.0 |
added 5 characters in body
|
| Nov 10 at 5:49 | review | Reopen votes | |||
| Nov 11 at 1:19 | |||||
| Nov 10 at 4:38 | history | closed |
José Carlos Santos Robert Longson Rubén Franck Dernoncourt CPlus |
Needs details or clarity | |
| Nov 8 at 19:31 | comment | added | Franck Dernoncourt | @NoDataDumpNoContribution I typically run across this issue when the cached results are slow to load. | |
| Nov 8 at 18:39 | comment | added | NoDataDumpNoContribution | I might have arthritis because I seem to be too slow. :) Maybe it's then not a very bad bug because simply waiting a bit bypasses it | |
| Nov 8 at 15:58 | history | edited | SpevacusMod | CC BY-SA 4.0 |
appended answer 404140 as supplemental
|
| Nov 8 at 14:32 | answer | added | Franck Dernoncourt | timeline score: 2 | |
| Nov 8 at 10:30 | comment | added | Franck Dernoncourt | @Glorfindel only need to click one time on it. The bug only affects cached queries | |
| Nov 8 at 8:18 | comment | added | Glorfindel Mod |
The button gets disabled (in the HTML) when you click on it, so it doesn't matter how fast I click, nothing strange happens.
|
|
| Nov 7 at 21:58 | review | Close votes | |||
| Nov 10 at 4:38 | |||||
| Nov 7 at 21:55 | history | edited | Franck Dernoncourt | CC BY-SA 4.0 |
added 49 characters in body; edited title
|
| Nov 7 at 21:55 | comment | added | Franck Dernoncourt | @KyleMit that'll be easier to repro with a query with a long output, since need to click "run query" before the cached result appear on screen. And/or you can throttle the internet connection. | |
| Nov 7 at 21:53 | comment | added | Franck Dernoncourt | @Lino data.stackexchange.com/stackoverflow/query/540572/… ; data.stackexchange.com/meta.stackexchange/query/1682302/… ; data.stackexchange.com/stackoverflow/query/483627/… etc | |
| Nov 7 at 21:48 | history | edited | Franck Dernoncourt | CC BY-SA 4.0 |
added 88 characters in body
|
| Nov 7 at 21:48 | comment | added | Franck Dernoncourt | @KyleMit I was using my phone for the screenshot so no user scripts there. I repro on Windows with Chrome (incognito), nothing in the console: i.sstatic.net/rSDOiNkZ.png | |
| Nov 7 at 21:05 | comment | added | KyleMit StaffMod | @FranckDernoncourt, do you have any console errors or user scripts? It's not happening to me when I run this query | |
| Nov 7 at 21:02 | comment | added | Franck Dernoncourt | @Lino any query that is cached and when clicking fast enough. a gif would be useful to show that but GIF size limit is extremely small and easy to hit; increase it to allow for more practical uploads | |
| Nov 7 at 20:49 | history | asked | Franck Dernoncourt | CC BY-SA 4.0 |
