Env, for one, is specifically not intended for use outside of Parsoid.

Should I rebase the security branch with latest changes to master?

On my laptop

Note function names are case insensitive for when you're grepping.

For development and debugging purposes, Parsoid also supports accessing an external MediaWiki installation via its action API. Parsoid/JS doesn't require that external wiki to have installed the ParsoidBatchAPI extension, but Parsoid/PHP depends on that currently (* TODO: Verify *).

The extension implementation is as follow,

After the upgrade, I confirmed the host was still running the currently deployed version,

I ran, SSH_AUTH_SOCK=/run/keyholder/proxy.sock ssh -l deploy-service wtp2011 'depool service=parsoid' from deployment.eqiad.wmnet and it's now showing {"wtp2011.codfw.wmnet": {"weight": 10, "pooled": "no"}, "tags": "dc=codfw,cluster=parsoid,service=parsoid"}

With that ^ the rt test script at least runs

A quick test with, node bin/roundtrip-test.js --domain ve --parsoidURL http://localhost/rest.php "Main Page", is returning,

I don't think the last fix deployment has fixed anything regarding that ticket. The Parsoid output is still broken so far I can see.

In the meantime, here's an edit that fixes it,
https://en.wikipedia.org/w/index.php?title=Maine&type=revision&diff=908732865&oldid=908276611&diffmode=source

The content seems to contain {{#tag:ref|Maine does not ... <references group="nb" /> |group="nb"}}, which results in references in references.

How do we pass in the rt testing flag to Parsoid?

The parsoid config is only used to get prefixes, which isn't really needed.

There should probably be better test coverage of this bin or at least fixing this,
https://github.com/wikimedia/parsoid/blob/master/bin/toolcheck.sh#L19-L21

Trying to address T178914: parse.js should have standard arguments as part of this port might be something worth considering.

@Arlolra has some WIP patches as well so maybe he has some insight into this question.

genTest is not relevant in the post-javascript world, so I'm crossing those off

This simplifies as, [[{{1x|Main{{!}}Page}}]]

Change 516451 merged by jenkins-bot:

Change 509531 merged by jenkins-bot:

Probably from,
https://it.wikipedia.org/wiki/Nati_nel_1974
https://it.wikipedia.org/wiki/Nati_nel_1992
etc.

A post-deploy test seems to preserve headline spacing,
https://office.wikimedia.org/w/index.php?title=User:ABreault_(WMF)/sandbox&type=revision&diff=253119&oldid=253118&diffmode=source

As @cscott says,

The JS mock API and the ApiHelper.php don't exactly play nice together, in that they have different ideas of which formatversion to use. There's also some redundancy with the JS baseconfigs and the ApiHelper.php cached data.

Only on private wikis.

Since templated regions might expand or contract between parses, the encoding should probably include both dsr[0] and dsr[1]. Contractions that expose nodes could result in additional dirty diff'ing, but shouldn't produce corruption.

I guess the next steps are,

Right, I think I've exhausted my usefulness here, thanks.

If there's a solution to assign stable ids to the nested content, why not just use that for the entire page?

dsr isn't applied in templated regions (all data-parsoid is dropped in there as is), it only corresponds to the top-level page.

Basically, this amounts to, if we have valid dsr info, use that for generating an id. If not, discard data-parsoid for that node.

For the most part, this corresponds with the code here,
https://github.com/wikimedia/parsoid/blob/master/lib/wt2html/pp/handlers/CleanUp.js#L194-L214