WDQS timeout errors should be more gracefully handled
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Nashona
	Mar 22 2021, 5:17 PM

Description

Something catastrophic happened when processing page User:Nashona/Other_NU.

This is very likely a bug in inteGraality itself, not a configuration issue.

Please report this on Phabricator.
<class 'pywikibot.exceptions.TimeoutError'> Maximum retries attempted without success.

Trying to manually update a previously created property dashboard, repeatedly gives the above error message.

https://www.wikidata.org/wiki/User:Nashona/Other_NU

Some further investigation - it is timing out when

selector_sparql=wdt:P31/wdt:P279*

is used.

Related Objects

Mentioned In: R2566:2a91226de372: Catch WDQS Timeouts and raise proper exception for all SPARQL queries
R2566:397c5e8294a9: Also catch ServerError to handle WDQS timeouts
R2566:30a2f2bac506: Extend QueryException with the query itself and surface it in the error page
R2566:7e3343a5731d: Catch WDQS Timeouts and raise proper exception
Mentioned Here: R2566:2a91226de372: Catch WDQS Timeouts and raise proper exception for all SPARQL queries
R2566:30a2f2bac506: Extend QueryException with the query itself and surface it in the error page
R2566:7e3343a5731d: Catch WDQS Timeouts and raise proper exception

Event Timeline

Nashona created this task.Mar 22 2021, 5:17 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 22 2021, 5:17 PM

Nashona updated the task description. (Show Details)Mar 26 2021, 5:51 PM

Mentioned in SAL (#wikimedia-cloud) [2021-10-25T21:41:21Z] <wm-bot> <jeanfred> Deploy 7e3343a (T278156)

JeanFred mentioned this in R2566:7e3343a5731d: Catch WDQS Timeouts and raise proper exception.Oct 25 2021, 11:16 PM

JeanFred renamed this task from pywikibot.exceptions.TimeoutError to WDQS timeout errors should be more gracefully handled.Oct 26 2021, 2:24 PM

JeanFred triaged this task as Medium priority.

JeanFred merged a task: T240726: Timeout error on InteGraality.

JeanFred merged a task: T236965: TimeoutError.

JeanFred added subscribers: Jsamwrites, JeanFred, Bodhisattwa.

JeanFred added a subscriber: Hsarrazin.

Basically, a SPARQL timeout error is not something we can solve on integraalit. The issue lies with the underlying queries − either it’s misconfigured or just more likely too expensive (try making a dashboard of all scientific articles… ;-þ)

Wth 7e3343a5731d, this /should/ at least be surfaced to the user with a somewhat helpful error message.

JeanFred mentioned this in R2566:30a2f2bac506: Extend QueryException with the query itself and surface it in the error page.Oct 28 2021, 11:31 AM

Mentioned in SAL (#wikimedia-cloud) [2021-10-28T11:31:38Z] <wm-bot> <jeanfred> Deploy 30a2f2ba (T278156)

With 30a2f2ba the offending SPARQL query should be always surfaced to the user. Closing as Resolved.

JeanFred mentioned this in R2566:397c5e8294a9: Also catch ServerError to handle WDQS timeouts.May 1 2025, 8:46 PM

JeanFred mentioned this in R2566:2a91226de372: Catch WDQS Timeouts and raise proper exception for all SPARQL queries.May 1 2025, 9:01 PM

Mentioned in SAL (#wikimedia-cloud) [2025-05-01T21:02:16Z] <wmbot~jeanfred@tools-sgebastion-10> Deploy 2a91226 (Catch WDQS Timeouts and raise proper exception for all SPARQL queries) for T278156

WDQS timeout errors should be more gracefully handledClosed, ResolvedPublicActions

Description

Related Objects

Event Timeline

WDQS timeout errors should be more gracefully handled
Closed, ResolvedPublic
Actions