Page MenuHomePhabricator

Specifying size for String is causing errors with recreating Cargo tables
Closed, InvalidPublic

Description

Issue Description

When recreating a table, the recreate will either seem to successfully complete or continuously loop and not end. However, when viewing the table, it will throw an MWException stating that the table could not be found.

I originally encountered the issue and thought it was a host-specific issue as reported here, but after a bit of testing, it seems when trying to recreate a table, it will fail if any of the field types is a String with a specified size (eg. String (size=1500)). Wikitext works as a workaround.

Additionally,

  • If the erroneous table created was a replacement table, it is no longer possible to recreate the table again since it will throw an error stating that there is already a replacement table.
  • It is not possible to delete the erroneous table from Special:CargoTables since attempting to delete it will throw the error that the table was not found.

Essentially, this becomes a "ghost" replacement table and prevents the UI from recreating or deleting it, forcing users without access beyond the web interface to not only do the workaround above, but also need to either rename the table (and all instances querying the table) or escalate the issue to someone who can fix the erroneous table.

Steps to Reproduce

  1. Declare a new Cargo table where one of the field types is String (size=1500)
  2. Create the table.
    1. The recreate will either complete successfully or the spinner will continue spinning without ever completing.
  3. On the template page, it'll state that the table was created; however, when viewing the table, an MWException is thrown stating that the table could not be found.

Example:

Event Timeline

Elaeagnifolia renamed this task from Specifying size for String is causing errors with recreating tables to Specifying size for String is causing errors with recreating Cargo tables.Aug 30 2019, 11:59 PM
Restricted Application added subscribers: RhinosF1, Reception123. · View Herald Transcript

The bug isn't valid anymore.