Talk:Proton/Flow

I submitted a bug, https://phabricator.wikimedia.org/T330747, you might want to take a look.

I submitted a bug, https://phabricator.wikimedia.org/T330745, you might want to take a look.

i installed mediawiki-services-chromium-render on a linux server and get it up and running. i just want to try if it works with en.wikipedia.org with default settings. but i keep getting internal_http_error 504, i cannot find any more detail. or a log with more details. i try this URL MYSERVER:3030/en.wikipedia.org/v1/pdf/Book/legal/mobile

The Error i get:

[2023-01-17T09:45:34.316Z] LVLTRACE: proton/28996 on RZaplP2: incoming request (request_id=b050eac0-964b-11ed-a1dd-899bf96d7dd4, levelPath=trace/req)

    request: {

      "url": "/en.wikipedia.org/v1/pdf/Book/legal/mobile",

      "headers": {

        "cache-control": "max-age=0",

        "user-agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36",

        "x-request-id": "b050eac0-964b-11ed-a1dd-899bf96d7dd4"

      },

      "method": "GET",

      "params": {

        "0": "/en.wikipedia.org/v1/pdf/Book/legal/mobile"

      },

      "query": {},

      "remoteAddress": "IP",

      "remotePort": 61822

    }

[2023-01-17T09:45:34.527Z] LVLERROR: proton/28996 on RZaplP2: RESTBASE error: 504: internal_http_error (code=504, levelPath=error/request)

    params: {

      "domain": "en.wikipedia.org",

      "title": "Book",

      "format": "legal",

      "type": "mobile"

    }

    --

    id: b05111d0-964b-11ed-b272-d0482b44e063|en.wikipedia.org|Book

Hello when I install npm I have some error in the install so I do a audit fix so now I have 0 error

C:\WINDOWS\system32>npm audit fix --force

npm WARN using --force Recommended protections disabled.

up to date, audited 1 package in 176ms

found 0 vulnerabilities

but when I test I got this error

C:\xampp\htdocs\mediaWikiTest\mediawiki-1.37.1\extensions\mediawiki-services-chromium-render-master>npm test

> proton@1.0.0 test

> npm run lint && PREQ_CONNECT_TIMEOUT=15 nyc --reporter text-summary _mocha

> proton@1.0.0 lint

> eslint --max-warnings 0 --ext .js --ext .json .

'eslint' n’est pas reconnu en tant que commande interne

ou externe, un programme exécutable ou un fichier de commandes.

C:\xampp\htdocs\mediaWikiTest\mediawiki-1.37.1\extensions\mediawiki-services-chromium-render-master>npm run coverage

> proton@1.0.0 coverage

> PREQ_CONNECT_TIMEOUT=15 nyc _mocha

'PREQ_CONNECT_TIMEOUT' n’est pas reconnu en tant que commande interne

ou externe, un programme exécutable ou un fichier de commandes.

So how I can fix that ? what did I miss?

thank you

I installed MediaWiki 1.37.2 on Ubuntu Server 20.04, added the Extension:Collection and stopped on installing proton.

Please describe step by step. What packages need to be installed in the ubuntu server and how to do it. What to download and where to copy. How to set up interaction with MediaWiki: Extension:Collection. How to run proton as a service.

I have not found such information anywhere.

Hello Team

I am using RHEL-7 including applications , php 7.4.13 ,Mysql 8, apache 2.4.37 wiki 1.35.1.

I need to install Proton as I am a bit confused to following this link Proton.

Can anyone provide me simple steps to install proton.

Do we need to install Puppeteer before proton.

Even I am not getting any video on YouTube as well.

Thanks in Advanced

It is frustrating to see that it cannot count over 100 references, resetting numbers to "00" again every time. Doesn't helps when printing big, well-sourced articles.

Is Proton production ready?

If so, will it be documented for use with wikis outside of WMF or integrated with Extension:Collection?

I'm also interested in Proton's integration with Extension:Collection, FWIW.

We're a couple months past the previous update that said we've have a launch date soon. Can anyone provide an update on what's holding up the launch, if help is needed in some area, etc.? It seems we've been more than a year without .pdf book capabilities.

Proton will not deliver book capabilities after all, it will only replace the Electron single-page service.

PediaPress are working on a new book service for us, which they call Collector. It is also running later than anticipated, but they do have a visible test service up at https://pediapress.com/collector Some more information can be gleaned from Talk:Reading/Web/PDF_Functionality.

There is also an independent service at http://mediawiki2latex.wmflabs.org/

The truth is, the WMF refuse to spend any resources on this project because "nobody is using the service". Quite how or why they expected us to use it, when it was so broken it had to be turned off, is beyond me.

Forgot to say, the progress of the single-page product is tracked on Phabricator: https://phabricator.wikimedia.org/project/profile/2960/ Bottom line: although nominally "finished", testing keeps throwing up bugs and until that stops it will keep getting thrown back to triage. No cash = no timescale.

.pdf book capability is huge IMO, for parents and educators world-wide. I'm unfamiliar with the organizational structure of the foundation, other than the requests for donations I've responded to over the years. As a donor, who does one speak to at the foundation about the lack of funding for this project?

The WMF are rather elusive. They have a governance wiki at https://foundation.wikimedia.org/wiki/Home

However the only real reaction I ever got was when I posted on founder Jimbo Wales' Wikipedia talk page almost three years ago now. I later moved that conversation to here.

Perhaps some others closer to the WMF can advise?