Maniphest: burnup rate chart is not displaying

Phabricator Version: current branch “stable”:
phabricator
51cd3f097928b1ed0a28c44a756185ead1dd1b94 (Sat, Jun 22) (branched from ca56e8590a3df188af5710cf4ef7b3e9780dd780 on origin)
arcanist
feb5f4d42c4fe0001e76428e80d5e88262308802 (Sat, Jun 22) (branched from d92fa96366c0ed50e4257508148aa75192d4fb1f on origin)
phutil
b675a06bf7419ff3b64448cb310e7557530446db (Sat, Jun 22) (branched from 8eaf1b38d41711112269b35bd2f083f6bc567d51 on origin)
php
7.3.6
diff
3.5 at /usr/bin/diff
git
2.11.0 at /usr/bin/git
hg
Not Available
pygmentize
2.2.0 at /usr/bin/pygmentize
svn
Not Available

Steps to reproduce:
open https://phabricator.example.com/maniphest/report/burn/

Actual behaviour:

Expected behaviour:

Display of burnup chart.

Hi herzke,
it works at my machine… The only difference in versions is php5 vs. php7.
Can you reproduce the bug in a phacility test instance?

My versions

  • phabricator
    51cd3f097928b1ed0a28c44a756185ead1dd1b94 (Sat, Jun 22) (branched from ca56e8590a3df188af5710cf4ef7b3e9780dd780 on origin)
  • arcanist
    feb5f4d42c4fe0001e76428e80d5e88262308802 (Sat, Jun 22) (branched from d92fa96366c0ed50e4257508148aa75192d4fb1f on origin)
  • phutil
    b675a06bf7419ff3b64448cb310e7557530446db (Sat, Jun 22) (branched from 8eaf1b38d41711112269b35bd2f083f6bc567d51 on origin)
  • php
    5.6.30-0+deb8u1
  • diff
    3.5 at /usr/bin/diff
  • git
    2.11.0 at /usr/bin/git
  • hg
    Not Available
  • pygmentize
    2.2.0 at /usr/bin/pygmentize
  • svn
    Not Available

This is an unintended interaction between the new Facts application, the phabricator.show-prototypes Config option, and the burnup chart.

The burnup chart is moving to be powered by the “Facts” application, which is currently a prototype. When prototypes are disabled, the chart incorrectly fails to render.

A quasi-workaround is to enable phabricator.show-prototypes, although this causes a lot of other behavioral changes.

The chart itself isn’t in great shape in master so I’m probably not going to try to fast-track a fix here, but will aim to fix this in the next release (circa this Friday) and clean up some of the actual chart behavior if nothing catches on fire too much between now and then.

Thanks for the reply!