Page MenuHomePhabricator

Strip marker (UNIQ / QINU) issues (tracking)
Open, MediumPublic

Description

Replacing of this tracking task to a proper tag is under discussion at T127350: Convert T28213 Strip marker issues (tracking) to a "Strip-Marker" tag.

MediaWiki parser uses the strip markers (\127UNIQ--tagname-8 hex digits-QINU\127 strings) internally for certain operations while processing the input. They aren't supposed to appear in the output, but sometimes they do. Here the different issues of this kind are tracked.

UNIQ/QINU tends to be shown when there is either a broken or invalid template call on a page. It is sometimes also displayed if an extension tag has a bug in its PHP code where it processes some of the wikitext only partially.

Details

Reference
bz26213

Related Objects

StatusSubtypeAssignedTask
OpenNone
OpenNone
ResolvedNone
ResolvedNone
OpenNone
Declinedmkroetzsch
InvalidNone
ResolvedReedy
OpenNone
ResolvedReedy
OpenNone
ResolvedNone
Resolvedtstarling
OpenNone
OpenNone
OpenNone
ResolvedJeroenDeDauw
OpenNone
ResolvedNone
OpenNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedNone
OpenNone
DeclinedNone
ResolvedNone
DeclinedNone
DeclinedPRODUCTION ERRORNone
OpenNone
DeclinedNone
InvalidNone
ResolvedUmherirrender
ResolvedNone
ResolvedEsanders
OpenNone
ResolvedNone
ResolvedNone
ResolvedNone
ResolvedBawolff
ResolvedNone
OpenNone
Resolveddemon
ResolvedAmire80
OpenNone
DeclinedCenarium
OpenNone
InvalidNone
DuplicateNone
ResolvedNone
ResolvedNone
OpenNone
OpenNone
InvalidNone
ResolvedJMinor
InvalidNone
ResolvedNone
OpenNone
ResolvedPhysikerwelt
Resolvedmobrovac
DeclinedPhysikerwelt
DeclinedPhysikerwelt
ResolvedPhysikerwelt
ResolvedPhysikerwelt
InvalidEsanders
OpenNone
Resolvedmobrovac
Resolvedmobrovac
ResolvedPhysikerwelt
OpenNone
OpenNone
Resolved Pablo-WMDE
OpenNone
OpenBUG REPORTMGChecker
ResolvedBUG REPORTNone
ResolvedBUG REPORTNone
ResolvedNone
OpenNone

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

#2700 seems to get closer to the root of what is happening on these

Tim suggests that we replace .UNIQ.*QINU. with some big error message that says "FIX YOUR MARKUP". Maybe with the new parser this is a moot point?

r100262 for an attempted way to spot these sooner.

[specific dep. issues can have high prio, this tracker bug should be "normal"]

Anybody interested in a #UNIQ project to track and tag related issues better?

Anybody interested in a #UNIQ project to track and tag related issues better?

Define "better"?

Having the option to watch the project (receiving notifications for all associated tasks) and maintain an own workboard.

Having the option to watch the project (receiving notifications for all associated tasks) and maintain an own workboard.

Following all reports sounds useless and a workboard redundant.

These are all variants of "MediaWiki's parser is dark and full of terrors". I'm not sure a project makes sense here.

Qgil removed a project: Project-Admins.
Qgil set Security to None.
Amire80 renamed this task from UNIQ issues (tracking) to UNIQ / QINU issues (tracking).Aug 2 2015, 9:33 AM
Amire80 updated the task description. (Show Details)
Amire80 edited projects, added MediaWiki-Parser; removed MediaWiki-General.
Danny_B renamed this task from UNIQ / QINU issues (tracking) to Strip marker issues (tracking).Feb 7 2016, 9:22 PM
Danny_B updated the task description. (Show Details)
Danny_B added a subscriber: Danny_B.

It would be good to update the ticket description a first aid guide for fighting those markers.

It would be good to update the ticket description a first aid guide for fighting those markers.

AFAICS, that's the purpose of the linked page: https://www.mediawiki.org/wiki/Strip_marker

Aklapper renamed this task from Strip marker issues (tracking) to Strip marker (UNIQ / QINU) issues (tracking).Dec 21 2016, 10:29 AM
Aklapper removed a subscriber: wikibugs-l-list.

Proposing to decline this task / close this task as invalid. Is someone really interested in following (not: finding, as that can be done via searching) all and any strip marker issues, or is this categorization for the sake of categorization (without someone doing that constant work)? If interested, then please elaborate.
If someone was interested, then this ticket should be convert into a project tag and people could subscribe to that project instead. See T127350.
See https://www.mediawiki.org/wiki/Phabricator/Help#.22Tracking.22_tasks

Second and last call to decline this task and close this task as invalid. If anyone cares, please speak up. Thanks.

matmarex added a subscriber: matmarex.

I care, please don't close it. Tasks like this are helpful for de-duplicating bug reports with similar error messages, but potentially different causes.

@matmarex: Thanks. In that case, are you fine with T127350 ?

I guess I'd be "fine" with that, but it doesn't sound like much of an improvement. And I'm definitely against adding a workboard, those are the worst.

@matmarex: You are free to ignore workboards (we unfortunately cannot easily stop people from (over)categorizing stuff for unknown reasons).
I'd say it's an improvement to be able to follow projects, instead of (ab)using parent tasks for project tracking (due to Bugzilla's historical limitations).