Stuart Olivera b76d59e68b ui: don’t consider aborted requests complete ... If an existing request is aborted due to a new request, ignore the completion of the initial request. Example: 1. Chrome dev tools: enable 5 second network latency 2. Execute query 3. A second later, execute the query again 4. Currently, the spinner will hide, and the stats will immediately display, as if the request had completed. Instead, the spinner and stats should wait until the 2nd execution finishes.		2016-10-12 17:20:44 -07:00
..
api/v1	api: Consolidate web API contexts	2016-09-21 03:22:20 +02:00
ui	ui: don’t consider aborted requests complete	2016-10-12 17:20:44 -07:00
federate_test.go	web: add more federation test scenarios	2016-09-15 15:23:55 +02:00
federate.go	storage: Contextify storage interfaces.	2016-09-19 16:29:07 +02:00
web_test.go	Add missing license headers	2016-04-13 16:08:22 +02:00
web.go	Update common/route vendoring for contextFn errors	2016-10-02 23:04:03 +02:00