Something like Toolhub but for PAWS.

It is immediate upon saving, the default autosave is 120 seconds, you can change that for any notebook with %autosave seconds where seconds is an integer. Ctrl + S will manually save your notebook and be immediately reflected in the public version.

I see the reasoning, but I worry the assumptions for PAWS and mybinder.org are too divergent for us to solve this easily.

Voilà is also a good option to expose notebooks as tools. CC @Andrawaag

Launch in Binder as in mybinder.org or should it be Launch in PAWS? If the latter, this becomes T264603

Seems we need to set the X-Scheme header to https. I am not sure if we should do this at the haproxy layer or add it in the ingress.

I am not sure why this happened, but PAWS had your server as running even though there was no matching pod in kubernetes. I have deleted it, you should be able to login now.

Got a similar message when looking at a Ticket just now. It went away when I locked the ticket.

This seems like an interesting project.
I think we would need a new component that will have an endpoint with the notebook to be forked and downloads the notebook into the user space. Paws-public would have to add a button to hit that endpoint.

@Edoderoo the error does indicate the Wiki in the last message see https://public.paws.wmcloud.org/User:chicocvenancio/T252306.ipynb

I think that is a mediawiki issue that goes beyond PAWS.

@Geertivp Why does PAWS requires the accounts?

Please see {T179677: Propose a logo for the PAWS project}. The logo was decided as https://commons.wikimedia.org/wiki/File:PAWS.svg Is there a significant reason to review this decision?

Right at the end there:

I think my work there can be safely deleted as it is obsolete by new developments in synapse and mediawiki (with ouath2).

In T258142#6317194, @Xqt wrote:

The repository at gerrit does not have a stable tag anymore https://gerrit.wikimedia.org/r/admin/repos/pywikibot%252Fcore,tags,25
Is there sth. out of sync?

Found password in old laptop backup.

@Arjunaraoc The fix will probably be merged in a couple of days. In the meantime, if you want a workaround you can manually update pywikibot by:

cd /srv/paws/pwb && git pull origin stable

There seems to be a stable tag in pywikibot pointing at rPWBC71e36c1574454d9438deaac08754ee4484dc4797 and a stable branch currently at rPWBCb8358a38b41be7f0d32c0e5178d69a7f555c2563.

In T258142#6316713, @Xqt wrote:

Did PAWS install outdated stable release?

Sounds good.

This is due to youtube blocking video2comons.

In T255635#6233538, @Bstorm wrote:

@Chicocvenancio I'll take that as assent, then! I spoke to @aborrero already about this. I'll set a few of the settings right now. For now, I will allow admins to break the rules, as long as we all basically just agree not to do so except in emergencies. We can use feature branches for most things if not doing a full GitHub fork like I'm doing right now. Thanks!

Makes sense to me. (the terms are from jupyterhub where limits and guarantees were initially backed by other components)

Not reproducible now.

I've hacked a fix for this into the live pod, but a rebuild of the image is necessary for persistence.

Invited @Bstorm as an admin.

I think I'm not familiar enough with toolforge ingress to comment on that part.

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.

@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.

https://paws-public.wmflabs.org/paws-public/User:Michael_Sch%C3%B6nitzer_(WMDE)/ Triggers a 500 by itself.

Is this still ongoing?

I can take a crack this week.

Taking the @bd808 bump on this to help move it forward.

It was https://tools.wmflabs.org/wikiloves/monuments/2019/Brazil/users

Thanks for the reminders, I have signed up as a co-mentor.

I don't see T245012, T226942 as blockers for PAWS.

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.

In T51541#5847780, @Juandev wrote:

Hey, is it set for whole wiki or is it just a user script? If there are people, who think its not worth coding, why not to have it as an option. I would love to use it on cs.pw, commons, cs.wv etc.

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.

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.

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.

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.

In T243459#5836621, @Bstorm wrote:

Sorry, All Hands isn't helping me focus on this. I'll check on how it relates to T241019 today (and talk to people on that who might help me know what to do next here). I am finding my limited involvement in PAWS is not helping me scope these tasks out.

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

For options:
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.

In T236446#5750583, @zhuyifei1999 wrote:

Google isn't responding (they probably don't have the incentive to), gonna wait for a few more days. If it stays like this, I'm gonna get a massive overhaul to how v2c download from YouTube. sneek peek: slimerjs + x11vnc

should this be a subtask of T241019?

Regarding the task idea:

In T243459#5826072, @aborrero wrote:

Also, to take into account: there are strong chances that I will be on vacations during next north hemisphere summer (Jun,Jul, Aug, Sept?) for a yet to be specified period of time, between 1 and 3 weeks.
We should make sure the relevant student aren't left "unattended" during that period.

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.

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

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?

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).