Page MenuHomeMiraheze

Cargo table rows are sometimes duplicating when the corresponding page is edited
Closed, InvalidPublic

Description

On the Sagan 4 Alpha wiki, we have recently had an issue where some rows on our cargo table have been duplicating upon editing the relevant page. No more than 2 copies of the same page's row have appeared at a time so far.

This is the relevant table (and the only one we have at the moment): https://sagan4alpha.miraheze.org/wiki/Special:CargoTables/SpeciesInfo

And here is an example of a page which has duplicate rows (selected because it's on the first page): https://sagan4alpha.miraheze.org/wiki/Acuo

Note that at the time of posting, there are only a few pages with a duplicate row because I rebuilt the table in an attempt to fix it; more will no doubt appear when other pages are edited, the most duplicates I've seen at a time being around 300. This doesn't seem to happen for all pages, and while I initially thought it was restricted to very old pages from before we moved to Miraheze or added Cargo, I've seen a few newer ones duplicate too.

Event Timeline

Unknown Object (User) added a comment.Mar 3 2021, 16:16

I apologise for all these Cargo errors that have been occurring as of late. This particular error is sorta tricky to resolve, due to:

  • It apparently fixes if the extension is updated.
  • Other errors apparently occur if the extension is updated. (See T6915)

As such, I have absolutely no idea what to do here, whether updating it is more worth the errors that happen then, or if these errors are less the impact. We will have determine the biggest impact and go from there. Again, apologies for this.

@Universal_Omega Are either of these issues reported upstream? It seems to me that the best option would be to wait until the extension has fixed the issue with the version active in T6915, and then upgrade to the fixed version (after verifying that it doesn't additionally break things further).

Unknown Object (User) closed this task as Invalid.Mar 7 2021, 05:59
Unknown Object (User) claimed this task.
Unknown Object (User) added a project: Upstream.
In T6920#136538, @Void wrote:

@Universal_Omega Are either of these issues reported upstream? It seems to me that the best option would be to wait until the extension has fixed the issue with the version active in T6915, and then upgrade to the fixed version (after verifying that it doesn't additionally break things further).

Looks like it was reported upstream. https://phabricator.wikimedia.org/T264103. That seems like the same issue, if I'm mistaken please feel free to reopen this task.