REPORTS-63 Query errors are not shown
Closed, DeclinedPublic
Actions

Assigned To

Authored By

	JiraBugConverter
	Dec 21 2013, 10:34 PM

Description

This issue was converted from https://jira.toolserver.org/browse/REPORTS-63.
Summary: Query errors are not shown
Issue type: Improvement - An improvement or enhancement to an existing feature or task.
Priority: Minor
Status: Open
Assignee: Merlijn van Deen <valhallasw@arctus.nl>

On Fri, 03 Aug 2012 16:06:49, Merlijn van Deen <valhallasw@arctus.nl> opened the following bug:

When a query fails (due to a syntax error, query killer or something
else), the report stays in 'generating' mode and does not show any
indication of an error.

Version: unspecified
Severity: minor

Details

Reference: bz58829

Event Timeline

• bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 2:17 AM

• bzimport added a project: Tool-tsreports.

• bzimport set Reference to bz58829.

JiraBugConverter created this task.Dec 21 2013, 10:34 PM

On Sun, 05 Aug 2012 16:28:27, Merlijn van Deen <valhallasw@arctus.nl> wrote:

https://github.com/valhallasw/tsreports/pull/5 implements a basic
version of this, but a message for users should be implemented too.

This was an issue again with the connection issues on Labs.

Because we are now using SGE to schedule jobs, we could implement something like:

IF (now - query_begin_time) > (last_runtime) * (cache_factor)

AND (there currently is no SGE job with the same name)

THEN submit a new job.

The 'existing job' test can be handled by jsub -once.

valhallasw removed valhallasw as the assignee of this task.Dec 15 2014, 2:17 PM

I think Quarry does show errors.

REPORTS-63 Query errors are not shownClosed, DeclinedPublicActions

Description

Details

Event Timeline

REPORTS-63 Query errors are not shown
Closed, DeclinedPublic
Actions