Page MenuHomePhabricator

Smith609 (Martin)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Monday

  • Clear sailing ahead.

User Details

User Since
Dec 2 2017, 5:46 PM (97 w, 6 d)
Availability
Available
LDAP User
Unknown
MediaWiki User
Smith609 [ Global Accounts ]

Recent Activity

Oct 11 2018

Restricted Application added a project to T93877: Accept and serve cookies: User-Ryasmeen.
Oct 11 2018, 8:25 PM · User-Ryasmeen, VisualEditor, Citoid

Sep 26 2018

Smith609 added a comment to T205213: Receiving 502 Bad Gateway with nodejs webservice.

That seems to have done it. It's now up and running. Amazing! Thanks again!

Sep 26 2018, 5:18 PM · Tools, cloud-services-team
Smith609 closed T205213: Receiving 502 Bad Gateway with nodejs webservice as Resolved.
Sep 26 2018, 5:17 PM · Tools, cloud-services-team
Smith609 added a comment to T205213: Receiving 502 Bad Gateway with nodejs webservice.

Could you change it within npm start?

Sep 26 2018, 4:53 PM · Tools, cloud-services-team
Smith609 added a comment to T205213: Receiving 502 Bad Gateway with nodejs webservice.

Thanks for the link. It looks like jswebservice.py doesn't refer to the $PATH variable.

Sep 26 2018, 4:38 PM · Tools, cloud-services-team
Smith609 added a comment to T205213: Receiving 502 Bad Gateway with nodejs webservice.

Sounds like you've found the problem! Node v8+ is required for the script.

Sep 26 2018, 3:48 PM · Tools, cloud-services-team
Smith609 renamed T205213: Receiving 502 Bad Gateway with nodejs webservice from Accessing PORT for nodejs webservice to Receiving 502 Bad Gateway with nodejs webservice.
Sep 26 2018, 2:32 PM · Tools, cloud-services-team
Smith609 updated the task description for T205213: Receiving 502 Bad Gateway with nodejs webservice.
Sep 26 2018, 2:32 PM · Tools, cloud-services-team
Smith609 closed T205505: process.env.PORT not defined as Resolved.
Sep 26 2018, 2:30 PM · Toolforge, cloud-services-team
Smith609 closed T205505: process.env.PORT not defined, a subtask of T205213: Receiving 502 Bad Gateway with nodejs webservice, as Resolved.
Sep 26 2018, 2:30 PM · Tools, cloud-services-team
Smith609 added a comment to T205505: process.env.PORT not defined.

That's interesting; having done that, the web service now starts. I wonder why it didn't this morning...
It's certainly useful to know that PORT won't be defined with a webservice shell.

Sep 26 2018, 2:28 PM · Toolforge, cloud-services-team
Smith609 added a comment to T205505: process.env.PORT not defined.

I added port=1969; to help with debugging; it didn't work without this line either.

Sep 26 2018, 1:41 PM · Toolforge, cloud-services-team
Smith609 triaged T205505: process.env.PORT not defined as High priority.
Sep 26 2018, 6:13 AM · Toolforge, cloud-services-team

Sep 23 2018

Smith609 created T205213: Receiving 502 Bad Gateway with nodejs webservice.
Sep 23 2018, 8:00 AM · Tools, cloud-services-team
Smith609 closed T205187: Setting $PATH to kubernetes webservice as Resolved.

I've addressed this by adding export PATH=$HOME/local/bin:$PATH to $HOME/.profile.
webservice --backend=kubernetes nodejs shell then allows me to verify that node -v is v11.0.0.

Sep 23 2018, 7:24 AM · Toolforge, cloud-services-team
Smith609 closed T205187: Setting $PATH to kubernetes webservice, a subtask of T205178: Node JS v8+, as Resolved.
Sep 23 2018, 7:24 AM · Toolforge, cloud-services-team

Sep 22 2018

Smith609 triaged T205178: Node JS v8+ as Normal priority.
Sep 22 2018, 12:56 PM · Toolforge, cloud-services-team
Smith609 created T205187: Setting $PATH to kubernetes webservice.
Sep 22 2018, 12:39 PM · Toolforge, cloud-services-team
Smith609 renamed T205178: Node JS v8+ from Node JS v*+ to Node JS v8+.
Sep 22 2018, 6:51 AM · Toolforge, cloud-services-team
Smith609 updated the task description for T205178: Node JS v8+.
Sep 22 2018, 6:51 AM · Toolforge, cloud-services-team
Smith609 created T205178: Node JS v8+.
Sep 22 2018, 6:50 AM · Toolforge, cloud-services-team

Sep 18 2018

Smith609 added a comment to T178469: Add open-access links in Wikipedia by using an open-access resolver (eg Unpaywall's oaDOI or doai.io).

I'd suggest popping a note on https://en.wikipedia.org/wiki/User_talk:Citation_bot, where the other maintainers (who have a little more time on their hands) will be able to look into the problem and suggest a solution.

Sep 18 2018, 9:43 AM · Library-Card-Platform-Discovery
Smith609 added a comment to T178469: Add open-access links in Wikipedia by using an open-access resolver (eg Unpaywall's oaDOI or doai.io).

Absolutely! See https://en.wikipedia.org/wiki/Wikipedia:UCB for details.

Sep 18 2018, 7:18 AM · Library-Card-Platform-Discovery

Sep 17 2018

Smith609 added a comment to T178469: Add open-access links in Wikipedia by using an open-access resolver (eg Unpaywall's oaDOI or doai.io).

Citation bot is currently activated by users, who keep an eye on its output; as such it is not yet processing large volumes of pages. The plan is to deploy it at a larger scale in the near future (next couple of months), at which point openURLs will start appearing more widely.

Sep 17 2018, 7:04 PM · Library-Card-Platform-Discovery

Dec 2 2017

Smith609 closed T181893: Bot passwords not supported by API as Invalid.
Dec 2 2017, 5:54 PM · MediaWiki-API
Smith609 added a comment to T181893: Bot passwords not supported by API.

Reading the documentation more carefully I see that this error can arise if cookies are not handled correctly, which is likely the cause. Apologies.

Dec 2 2017, 5:53 PM · MediaWiki-API
Smith609 created T181893: Bot passwords not supported by API.
Dec 2 2017, 5:50 PM · MediaWiki-API