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
ResolvedCharlie_WMDE
ResolvedLucas_Werkmeister_WMDE
Resolved Tonina_Zhelyazkova_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedMichael
ResolvedNone
Resolved Pablo-WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedCharlie_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedMichael
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedMichael
Resolved Tonina_Zhelyazkova_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedCharlie_WMDE
ResolvedLucas_Werkmeister_WMDE
Resolved Tonina_Zhelyazkova_WMDE
ResolvedLucas_Werkmeister_WMDE
Resolved Tonina_Zhelyazkova_WMDE
Resolved Tonina_Zhelyazkova_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedMichael
ResolvedMichael
Resolved Matthias_Geisler_WMDE
ResolvedLucas_Werkmeister_WMDE
Resolved Matthias_Geisler_WMDE
Resolved Tonina_Zhelyazkova_WMDE
Resolved Pablo-WMDE
ResolvedLucas_Werkmeister_WMDE
Declined Matthias_Geisler_WMDE
Declined Matthias_Geisler_WMDE
ResolvedLucas_Werkmeister_WMDE
OpenNone
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
Resolved Pablo-WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedMichael
Resolved Pablo-WMDE
ResolvedCharlie_WMDE
Resolved Pablo-WMDE
ResolvedNone
Resolved Pablo-WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
OpenNone
OpenNone
InvalidCharlie_WMDE
OpenNone
InvalidCharlie_WMDE
OpenNone
InvalidNone
ResolvedCharlie_WMDE
Resolved Tonina_Zhelyazkova_WMDE
Resolved Tonina_Zhelyazkova_WMDE
ResolvedMichael
Resolved Tonina_Zhelyazkova_WMDE
ResolvedMichael
Resolved Tonina_Zhelyazkova_WMDE
Resolved Tonina_Zhelyazkova_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedMichael
ResolvedLucas_Werkmeister_WMDE
ResolvedCharlie_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedMichael

Event Timeline

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 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

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

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).

@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.