Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | None | T312948 v0 Known Bugs to be fixed in v1 | |||
| Open | None | T312054 Make sorting by participants on Special:MyEvents work on SQLite | |||
| Resolved | Daimona | T315465 Allow subclasses of IndexPager to process the offsets from the querystring before using them to build SQL |
Event Timeline
a note on this ticket - am also unable to reproduce it on betacluster, but the bug persists on local env.
Beta uses MariaDB, like patchdemo and prod; only mw-docker uses SQLite (by default).
I've been thinking about this issue, but I'm not sure how to proceed. IndexPager extracts the offsets from the query string and simply treats them as strings. This makes sense for actual strings and for some numeric strings (most notably, timestamps), but not for other things, like in this case. I'm not sure how to fix this properly; the quickest fix that I can think of is to cast num_participants to string in the SELECT.
I personally don't think this is needed, because prod does not use SQLite. The main reason for fixing this now would be so that sorting works when testing locally in Mediawiki-Docker. We will also need to do something about it when we mark the extension as stable (something that's not on our radar yet), either fix this bug or disable sorting by participants on SQLite.
@vyuen: Could you please explain who or what (task?) exactly this task is stalled on ("If a report is waiting for further input (e.g. from its reporter or a third party) and can currently not be acted on")? Thanks.
This is currently blocked on receiving some input/feedback in the subtask. (I guess the "stalled" status could be somewhat redundant since it has a subtask, but it makes it easier to see that this task is blocked when looking at ensemble views like workboards).