Thu, May 28
Not reproducible now.
I've hacked a fix for this into the live pod, but a rebuild of the image is necessary for persistence.
Wed, May 27
Invited @Bstorm as an admin.
I think I'm not familiar enough with toolforge ingress to comment on that part.
Tue, May 26
No. Automation seems broken due to the movement in repo and to travis.com. Probably all that is necessary is to regenerate a .travis.yml with encrypted secrets.
The current images are in https://quay.io/organization/wikimedia-paws-prod/ I can give access to users there, or we can move to a different registry.
Thu, May 21
@RhinosF1 precisely, but the code should only hit wikidata and nl wikipedia.
@SandraF_WMF I would love to help onboard more contributors to PAWS and help with technical scoping of this contribution, sorry it took me a while to notice the comment.
PAWS-public seems to be erroring out with all usernames that go outside ascii.
@MichaelSchoenitzer_WMDE In the meantime you can go to https://paws-public.wmflabs.org/paws-public/47694471/ to see your public notebooks.
I can reproduce this https://paws-public.wmflabs.org/paws-public/User:chicocvenancio/T252306.ipynb it tells me I don't have an account in az:wikibooks.
My best guess is this is this is similar to T168222
Not PAWS related but pywikibot hitting other wikis from the wikidata item.
2020/05/21 18:18:18 [error] 7#7: *325234 lua entry thread aborted: runtime error: rewrite_by_lua(nginx.conf:140):15: Expected value but found invalid token at character 1 stack traceback: coroutine 0: [C]: in function 'decode' rewrite_by_lua(nginx.conf:140):15: in function <rewrite_by_lua(nginx.conf:140):1>, client: XXX.XXX.XXX.XXX server: , request: "GET /paws-public/User:Michael_Sch%C3%B6nitzer_(WMDE)/ HTTP/1.1", host: "paws-public.wmflabs.org" XXX.XXX.XXX.XXX - - [21/May/2020:18:18:18 +0000] "GET /paws-public/User:Michael_Sch%C3%B6nitzer_(WMDE)/ HTTP/1.1" 500 595 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36"
https://paws-public.wmflabs.org/paws-public/User:Michael_Sch%C3%B6nitzer_(WMDE)/ Triggers a 500 by itself.
Is this still ongoing?
Apr 26 2020
I can take a crack this week.
Apr 21 2020
Mar 18 2020
Mar 8 2020
Taking the @bd808 bump on this to help move it forward.
Mar 3 2020
Feb 24 2020
Thanks for the reminders, I have signed up as a co-mentor.
Feb 22 2020
Feb 12 2020
Feb 11 2020
FYI, as @srishakatux suggested last year, discussed in IRC, and discussed with @bd808, @yuvipanda has moved the main repo to the toolforge github organization at my request. https://github.com/toolforge/paws is where the production PAWS code lives in now.
Feb 4 2020
Feb 3 2020
Feb 2 2020
Setting up the Wiki-Loves-Love bot for this year I decided to take advantage of CronJobs. I placed my example CronJob yaml definition and some notes on how to debug it in the Wikitech page.
Jan 31 2020
yeah, my plan then was to actually go the full k8s route with prometheus-operator and such. Have not gotten around to implementing it yet.
Jan 30 2020
Does this include updates to the toolforge prometheus instance? I wanted to funnel PAWS metrics there but it was such an old version when I tried it I gave up on getting it to work.
After being properly informed of the differences in GSCO and Outreachy I am very much considering it a better solution that we focus on Outreachy. The deadline alone means we'd have very little time to plan for GSOC but it seems to may Outreachy stipend for the intern makes it a program I can support more easily.
Jan 28 2020
FYI: mentioned this in https://discourse.jupyter.org/t/planning-to-mentor-a-project-in-outreachy/3191 to try to better coordinate all communities involved.
No problem @aborrero alerted me to All Hands on IRC.
When is the deadline for GSOC submission again? If it is right after this week, we might want to focus on Outreachy. Travel is getting in the way of things quite a bit for me.
February 5 19:00 UTC
In a way, I like the second option most because it isn't quite as dependent on building workarounds to the Kubernetes user security model. I think WMCS could deliver a service account appropriately limited to the task in a rebuilt PAWS cluster in coming quarters that would open that option nicely...but will it be in time?
It is harder to do damage to a cluster with volumes than it is with spinning up pods directly via crons.
Overall, I think with all of this I need to clarify my own understanding a bit to really say anything intelligent, and I'm not sure I have the time to dig in deeply this week. I will try a bit and talk to folks here.
Unless you feel otherwise I think we should hold this until y'all are back from All Hands. That likely means we go with Outreachy but it seems fine to me.
should this be a subtask of T241019?
Jan 23 2020
Regarding the task idea:
That should not be an issue. I'm planning to be off for a two week period in May (around Wikimedia-Hackathon-2020), so we need to have plans ready before that, interns should not have started yet if I'm understanding the timeline correctly.
Jan 22 2020
Seems to be missing a few edits I made a few hours ago with my bot https://xtools.wmflabs.org/autoedits-contributions/pt.wikipedia.org/ChicoBot v https://pt.wikipedia.org/wiki/Especial:Contribui%C3%A7%C3%B5es/ChicoBot
Jan 21 2020
https://meta.wikimedia.org/w/index.php?title=Special:OAuthListConsumers/view/bf7eb39a895d1987ef9300b782fc948b&name=PAWS&publisher=&stage=-1 is the last one, probably not a lot of edits there though
How do we get the CIDs?
How to translate 0a73e346a40b07262b6e36bdba01cba4 to 429?
Jan 20 2020
Maybe add PAWS and the OAuth consumer version as the client in the meantime?
BTW, there are 5 past PAWS OAuth consumers and I will (hopefully) soon move it to a sixth one (T243200).
Jan 17 2020
This does not seem to be the underlying issue here, but PAWS will not have admin permissions. T192237
Jan 9 2020
Dec 4 2019
It has been a while, but I have a working script to add thanks links over at https://github.com/chicocvenancio/wiki_scripts/blob/gh-pages/thankLinksInWatchlist-pt.js It is localized to portuguese and doesn't quite handle genders properly right now, but if there is interest I could clean it up and add i18n for it.
I copied a few of the functions from ext.thanks and added the links manually to the dom.
Nov 4 2019
Sure, makes sense.
@bd808 I don't think these are duplicates. As I understand T174469 is a backend problem that makes accounts that are not attached to Wikitech not have a way to reset passwords. This is more of a feature request to have some indication in Striker of how to reset passwords.
Adding a link to https://wikitech.wikimedia.org/wiki/Special:PasswordReset might be good enough to avoid confusion.
Nov 2 2019
Oct 31 2019
That was it, thanks @Phamhi.
Oct 29 2019
having a separate OAuth flow
This is the part that is complicated in my view, specially doing this securely and with a good UX in PAWS.
Oct 24 2019
Hey @Tgr, I'm not sure setting up automatic OAuth with the beta cluster is straightforward. The reason we can do it with the production wikis is we authenticate the user with them and just use the same OAuth tokens to pass to Pywikibot. As I understand it, there is no way to authenticate with production wikis and use that session with the beta-cluster, so we would need to setup a different authenticator for PAWS specifically for the beta-cluster, this is not impossible but I fear it is a significant amount of development and may create confusion for normal users.
Thanks for creating this ticket. The pod was stuck in terminating state in the node tools-paws-worker-1007 for the past couple of days. I removed it with kubectl -n prod delete pod jupyter--43riscod --force grace-period=0 perhaps someone with root access should check docker to see if/why the container is still running.
Oct 22 2019
@Dominicbm I agree this is a great improvement for PAWS. Unfortunately I do not have the bandwidth to develop this for the foreseeable future and no other volunteers have stepped up.
Oct 2 2019
Sep 9 2019
Aug 30 2019
Aug 15 2019
Aug 13 2019
Aug 12 2019
Aug 8 2019
I've tested with and without the UserAgent, it sometimes works when defaulting to the SPARQLWrapper agent, but without looking at server logs and configuration I don't have much clue on why this is happening. Perhaps someone can investigate and tell us.
Indeed setting a different agent works. https://paws-public.wmflabs.org/paws-public/User:chicocvenancio/T230135.ipynb
This seems relevant https://github.com/RDFLib/sparqlwrapper/issues/139
BTW you can use a ! to run commands directly from the notebooks. IE use !pip install sparqlwrapper instead of using the terminal every server start. see https://paws-public.wmflabs.org/paws-public/User:chicocvenancio/T230135.ipynb
This seems to be an HTTP response from https://query.wikidata.org/
Jul 16 2019
@Mohinem how are you trying to login? There is no login required for Wikimedia wikis.
Jul 12 2019
It seems this is an artifact of the packages installed in the singleuser image clashing in some way. I don't know what packages are the source of this error and have not had the time to investigate this more closely.
Jun 19 2019
In short, currently, don't.
@bd808 should we ask for a VPS project to have a subdomain we can verify ourselves or is there a way to verify tools.wmflabs.org itself?
I would think of having a simple proxy to Toolforge with nginx if a project is indeed necessary.
May 21 2019
May 19 2019
Sorry, this was in PAWS, so maybe something we're doing with Auth there is messing this up.
May 18 2019
Finally tracked this being due to helm attempting to talk directly to k8s with the pod's serviceAccount instead of the Tiller one.
It works again.
Where are the project rooms?
The project rooms are on the 4th floor.