Page MenuHomePhabricator

Random behaviour of template expansion using parser functions.
Closed, ResolvedPublic

Description

There seems to be a bug in the ParserFunctions code or related that causes all pages using a
certain template to randomly display either the text:

{{Navvi_Joohr_Joodousende}}

or:

{{#ifexpr:((2-1+01)>(2006+1248)/1000)}}

instead of the expanded template Navvi_Joohr_Joodousende.

This affects many "year" articles in the Wikipedia of Ripuarian languages - in fact all those
already using the template Navvi_Joohr_Fooß - and can be seen at the very end of them, e.g.
http://ksh.wikipedia.org/wiki/1228


Version: unspecified
Severity: major
URL: http://ksh.wikipedia.org/wiki/1232

Details

Reference
bz7007

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 9:22 PM
bzimport set Reference to bz7007.
bzimport added a subscriber: Unknown Object (MLST).

robchur wrote:

See comment #1 on bug 7005, same behaviour.

*** This bug has been marked as a duplicate of 7005 ***

I cannot see any relation to the comment #1 on bug 7005 for three reasons:

  1. There is nothing random reported in bug 7005
  2. all affected pages have (should have) identical navigation bars on their top and

their end, only the order reversed. Top bars are always good, while the last of the
bottom navigation bars consistently fails - one of two observed failiures results is
randomly selected at a probability of 1:2, it seems, different with every invocation
of the page. Even if failiure were intended by programmers (why?) - random behaviour
is a bug on its own.

  1. If it were truly a newly imposed size limitation (on whatever), I have to file a

bug against am incorrect or inconsistent implementation of the limit, since here the
few words "et zweijte, et eetßte Johdousend füür, unn_et eetßte, et zweijte, et
drette Johdousend noh Krißtoß" (with wikilinks) only were above the limit, while
elsewhere full pages of tables of data can be transcluded unmolested.

robchur wrote:

The template expansion is not occurring because the expansion size limit is
being reached on certain pages. It's the same behaviour.

*** This bug has been marked as a duplicate of 7005 ***