In T107914#3192851, @santhosh wrote:

Yes, it is not just plain page fetch from Parsoid. CXserver internally fetch the page from parsoid, parse it and segments the content to sentences using our language specific sentence segmentation algorithm. It also adds identifiers and various attributes for sections, sentences, links, references etc. So this end point cannot be replaced with https://{domain}/api/rest_v1/page/html/{title}/{revision}

Does this look sensible?

https://{domain}/api/rest_v1/translate/page/{language}/{title}/{revision}

Fetches segmented mediawiki page {title} matching optional {revision} for translation from {language}

Alternatives are being discussed on the PR. Please chime in there.

In T107914#3299419, @KartikMistry wrote:

T162576 is done; Waiting for deploy: https://gerrit.wikimedia.org/r/356127

Do we have an ETA for the deployment?

In T107914#3305567, @mobrovac wrote:

In T107914#3192851, @santhosh wrote:

Yes, it is not just plain page fetch from Parsoid. CXserver internally fetch the page from parsoid, parse it and segments the content to sentences using our language specific sentence segmentation algorithm. It also adds identifiers and various attributes for sections, sentences, links, references etc. So this end point cannot be replaced with https://{domain}/api/rest_v1/page/html/{title}/{revision}

Does this look sensible?

https://{domain}/api/rest_v1/translate/page/{language}/{title}/{revision}

Fetches segmented mediawiki page {title} matching optional {revision} for translation from {language}

Alternatives are being discussed on the PR. Please chime in there.

@santhosh and @Nikerabbit Please have a look too.

In T107914#3299419, @KartikMistry wrote:

T162576 is done; Waiting for deploy: https://gerrit.wikimedia.org/r/356127

Do we have an ETA for the deployment?

I can deploy it on Monday. Verifying it once again and I'll sync on this later today.

Change 360692 had a related patch set uploaded (by Mobrovac; owner: Mobrovac):
[mediawiki/services/cxserver@master] Let the page loader accept full project domains as params as well

https://gerrit.wikimedia.org/r/360692

Change 360692 merged by jenkins-bot:
[mediawiki/services/cxserver@master] Let the page loader accept full project domains as params as well

https://gerrit.wikimedia.org/r/360692

T162576 is done; Waiting for deploy: https://gerrit.wikimedia.org/r/356127

Do we have an ETA for the deployment?

I can deploy it on Monday. Verifying it once again and I'll sync on this later today.

We've deployed new end point code of cxserver. Thanks @mobrovac for spotting the issue and quick fix!

@mobrovac: So the current status is that the cxserver changes are done, but the public API has not been finalized & deployed yet?

Change 366312 had a related patch set uploaded (by Mobrovac; owner: Mobrovac):
[mediawiki/services/restbase/deploy@master] Config: Add the CXServer host URI

https://gerrit.wikimedia.org/r/366312

Change 366312 merged by Mobrovac:
[mediawiki/services/restbase/deploy@master] Config: Add the CXServer host URI

https://gerrit.wikimedia.org/r/366312

Mentioned in SAL (#wikimedia-operations) [2017-07-19T19:08:42Z] <mobrovac@tin> Started deploy [restbase/deploy@c5938f4]: Expose the translation API end points and fix SwaggerUI - T107914 T170729

Mentioned in SAL (#wikimedia-operations) [2017-07-19T19:16:44Z] <mobrovac@tin> Finished deploy [restbase/deploy@c5938f4]: Expose the translation API end points and fix SwaggerUI - T107914 T170729 (duration: 08m 02s)

The RESTBase portion of this task has been completed. The public API has been discussed and deployed. It is now live in production. The next step is for the Content Translation team to start using these end points in the CX extension, so that cxserver.wm.org can be sunset.

Thanks @mobrovac I'll submit patch for CX soon (T163203)

@mobrovac While checking, https://es.wikipedia.org/api/rest_v1/#!/Transforms/doMT

Request URL: https://es.wikipedia.org/api/rest_v1/transform/html/from/en/Apertium

{
  "type": "https://mediawiki.org/wiki/HyperSwitch/errors/internal_error",
  "method": "post",
  "detail": "TypeError: Cannot read property 'status' of undefined",
  "uri": "/es.wikipedia.org/v1/transform/html/from/en/Apertium"
}

There was a bug in RESTBase's code. The fix was merged and deployed. Thank you @KartikMistry for reporting!

Since there is no blocker for this configuration and v2 is still in development (see: https://phabricator.wikimedia.org/T183139) I'll go ahead and start submitting needed configuration patches now.

@mobrovac I'm planning to schedule this soon. What timeframe works for you?

@KartikMistry are you referring to T163203: Update CX to use the new Restbase provided public API instead of CXServer ? On our side, the public API is out, so we should be ready as all of the blockers have been resolved.

@mobrovac It seems we need to implement /list/{tool}/$from/$to in REST API, which is used in CX.