A user, ganncamp, encountered an issue with a runaway Data Explorer query that didn’t prompt for a parameter value and appeared to run indefinitely. codinghorror suggested that Data Explorer has a default query timeout protection, which was confirmed by david to be a 10-second timeout. However, ganncamp reported not seeing any notifications or feedback after the timeout period.
david investigated the issue and found that the timeout was working correctly on the server-side, but an error in the client-side was preventing the error from displaying. The issue seemed to be related to a “Null” value for a user. The problem was reported and codinghorror linked to a GitHub pull request (https://github.com/discourse/discourse-data-explorer/pull/151) that will fix the issue.
Hi,
I’m just starting to explore Data Explorer. I plopped in this query: View Count of a specific tag - #2 by SidV
and hit ‘Save Changes and Run’, expecting to be prompted for the parameter value. After waiting a couple minutes, I glanced at my URL and saw to my horror ?id=5¶ms=%7B"user"%3Anull%7D
So… kill my long-running query?
Good question! I believe we have default query timeout protection in Data Explorer, but someone else from the Discourse team would need to confirm that.
Indeed, we have a 10 second timeout on any queries running via data explorer, so no need to worry about things running for too long 
You should receive some feedback in the UI after that 10s has passed. If not then let us know and we’ll dig into it.
Nope. Nothing. No notifications at all. That’s why I created my post. I was hoping a timeout kicked in, but I had no way of knowing.
Oh, interesting! I just gave it a try here on Meta, and it looked like this: (error at the bottom)
Would you mind trying the broken query one more time on your site, and see whether anything like this appears?
You asked for it! 
Aha! The good news is that the 10s timeout is working correctly on the server-side, so the query did indeed get cancelled. Bad news is that there is some error in the client which is stopping the error from displaying. It seems to be related to the “Null” value for a user, rather than the timeout itself.
We’ll get that fixed up - thanks for reporting!
This will be fixed by
https://github.com/discourse/discourse-data-explorer/pull/151
This topic was automatically closed after 17 days. New replies are no longer allowed.
