Page MenuHomePhabricator

Step 1: Error States of Data-Bridge [Tracking] (impact: medium)
Open, MediumPublic

Description

This ticket collects and groups possible error states of the bridge app, in order to group and not forget them. We have the privilege to decide if we want to cater to each of these individually (for the known unknowns) or we let them fall back to the generic error screen which we'll have to create regardless (for the unknown unknowns).

Please add more error states here and feel free to group them as groups emerge.

Scenarios:

  • entity loading failed
    • server does not respond (no internet)
    • server responds with bad data (e.g. some html)
    • server responds with server error (e.g. 500)
    • server responds with bad request or similar (e.g. 400 if hrefRegExp is badly done and Q0 requested)
    • entity does not exist at server
    • entity does not exist at server, but is a redirect
  • property label loading failed (possible options mentioned during T227759 were: trying to load it again, showing the property id with a little message, showing the generic error handler)
  • data type not supported (yet) - as tracked by T231204: track Bridge openings by property datatype
  • snak type novalue/somevalue not yet supported
  • more than one statement in statement group not yet supported
  • there is no statement for the property on the entity yet
  • saving failed
  • purging the parser cache, after saving was a success, has failed. --> The user might see outdated data when reloading

Other

  • page is protected at client
  • page is protected at repo

Related Objects

StatusSubtypeAssignedTask
OpenNone
OpenNone
ResolvedCharlie_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedMichael
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedMichael
ResolvedTonina_Zhelyazkova_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedCharlie_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedTonina_Zhelyazkova_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedTonina_Zhelyazkova_WMDE
ResolvedTonina_Zhelyazkova_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedMichael
ResolvedMichael
ResolvedMatthias_Geisler_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedMatthias_Geisler_WMDE
ResolvedTonina_Zhelyazkova_WMDE
ResolvedPablo-WMDE
ResolvedLucas_Werkmeister_WMDE
DeclinedMatthias_Geisler_WMDE
DeclinedMatthias_Geisler_WMDE
ResolvedLucas_Werkmeister_WMDE
OpenMichael
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedPablo-WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedMichael
ResolvedPablo-WMDE
ResolvedCharlie_WMDE
ResolvedPablo-WMDE
ResolvedNone
ResolvedPablo-WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
OpenCharlie_WMDE
OpenCharlie_WMDE
InvalidCharlie_WMDE
OpenCharlie_WMDE
InvalidCharlie_WMDE
OpenCharlie_WMDE
OpenCharlie_WMDE
OpenCharlie_WMDE

Event Timeline

Michael created this task.Jul 15 2019, 2:55 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 15 2019, 2:55 PM
Pablo-WMDE updated the task description. (Show Details)Sep 4 2019, 1:15 PM
Pablo-WMDE updated the task description. (Show Details)Sep 10 2019, 11:08 AM
Michael updated the task description. (Show Details)Oct 1 2019, 9:54 AM
Michael updated the task description. (Show Details)Oct 8 2019, 11:14 AM
darthmon_wmde renamed this task from Error States of Data-Bridge [Tracking] to Step 1: Error States of Data-Bridge [Tracking].Dec 5 2019, 1:17 PM
Lydia_Pintscher triaged this task as Medium priority.Dec 8 2019, 11:53 AM
Lydia_Pintscher renamed this task from Step 1: Error States of Data-Bridge [Tracking] to Step 1: Error States of Data-Bridge [Tracking] (impact: medium).Dec 8 2019, 1:22 PM
Pablo-WMDE updated the task description. (Show Details)Dec 10 2019, 9:58 AM
Pablo-WMDE updated the task description. (Show Details)Dec 10 2019, 10:02 AM

@Lydia_Pintscher please group things by permanent and "something can be done about it" errors and create different screens.

Michael updated the task description. (Show Details)Tue, Jan 21, 1:36 PM

entity does not exist at server
entity does not exist at server, but is a redirect

Note to self so I don’t forget: if we want the user to report a problem with a certain page (e. g. it consistently yields broken bridge links), and we want to make the target page configurable, the standard MediaWiki way is to put the target page in an interface message called “something-url” (e. g. currentevents-url, policy-url, portal-url).

Pablo-WMDE updated the task description. (Show Details)Mon, Jan 27, 3:02 PM

@Lydia_Pintscher who is responsible for tracking the completed error messages in this ticket. it looks like some of them are already done or in doing at least but it's currently not being reflected in this ticket.