The lack of an uptick in new weekly editors on fawiki during the ip block indicates to me a big difference from ptwiki's implementation. My lack of farsi prevents a deeper investigation, but in ptwiki the interface was hacked to point logged out users at the point of edit. The edit button was changed to point directly to the log-in page and banner explaining the need to create an account linking to the reasoning was put there.

@Isaac indeed. Fixed the link to a permalink to avoid future issues.

6.6.5 was merged.

Other bank transfer methods are also erroring for me.

@EMartin its before we actually make the transaction.

All for the upgrade but just for the record I don't see a path for exploitation here. All requests to openrefine go through the proxy and only authenticated requests pass. And if you're authenticated into a user server, well RCE is the main feature for jupyterhub.

LGTM. Opinionated ways to run the more basic tasks is a good way to reduce the burden on new users.

I guess portaudio19-dev is the missing apt package here.

Thanks to @yuvipanda on the assistance on this. Would've taken me hours to understand it.

Just noting we received a report of this bug in the Portuguese wikipedia telegram group today.

I had to rollback as the new Host validation in openrefine 3.5 broke it with the current settings. I'm not quite sure what best to do here, since we're already proxying it through the jupyter server we could disable the validation. But I think I'll set it up to have the proper value in the next few days.

PR in https://github.com/toolforge/paws/pull/110

Merged and deployed

[2021-11-17 13:47:56,895: ERROR/ForkPoolWorker-14] Task video2commons.backend.worker.main[ea3650a1-4dcd-4341-95a3-7afa84e43b94] raised unexpected: FileNotFoundError(2, 'No such file or directory')
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/celery/app/trace.py", line 450, in trace_task
    R = retval = fun(*args, **kwargs)
  File "/usr/local/lib/python3.7/dist-packages/celery/app/trace.py", line 731, in __protected_call__
    return self.run(*args, **kwargs)
  File "/srv/v2c/video2commons/backend/worker.py", line 132, in main
    pywikibot.Site('commons', 'commons', user=username).login()
  File "/usr/local/lib/python3.7/dist-packages/pywikibot/site/_apisite.py", line 358, in login
    if self.userinfo['name'] == self.user():
  File "/usr/local/lib/python3.7/dist-packages/pywikibot/site/_apisite.py", line 465, in userinfo
    uidata = uirequest.submit()
  File "/usr/local/lib/python3.7/dist-packages/pywikibot/data/api.py", line 1739, in submit
    self._add_defaults()
  File "/usr/local/lib/python3.7/dist-packages/pywikibot/data/api.py", line 1245, in _add_defaults
    and self.site.mw_version >= '1.25wmf5'):
  File "/usr/local/lib/python3.7/dist-packages/pywikibot/site/_apisite.py", line 953, in mw_version
    mw_ver = MediaWikiVersion(self.version())
  File "/usr/local/lib/python3.7/dist-packages/pywikibot/site/_apisite.py", line 929, in version
    version = self.siteinfo.get('generator', expiry=1).split(' ')[1]
  File "/usr/local/lib/python3.7/dist-packages/pywikibot/site/_siteinfo.py", line 296, in get
    preloaded = self._get_general(key, expiry)
  File "/usr/local/lib/python3.7/dist-packages/pywikibot/site/_siteinfo.py", line 237, in _get_general
    default_info = self._get_siteinfo(props, expiry)
  File "/usr/local/lib/python3.7/dist-packages/pywikibot/site/_siteinfo.py", line 162, in _get_siteinfo
    data = request.submit()
  File "/usr/local/lib/python3.7/dist-packages/pywikibot/data/api.py", line 2022, in submit
    self._write_cache(self._data)
  File "/usr/local/lib/python3.7/dist-packages/pywikibot/data/api.py", line 2014, in _write_cache
    with open(self._cachefile_path(), 'wb') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/srv/v2c/apicache-py3/644d1c68a83935b749c8608f05fd23e5e5c1e18f5dce61a6c873727d7791a896'

Not sure how to debug this, is this perhaps a known issue with pywikibot?

Fixed on Fixed on https://github.com/toolforge/video2commons/commit/53d51e96d5db24afe3725eb88bdf90f5884fdd0a.

This error should be fixed with the upgrade to python3.

yeah, let me see if I can get python3 working on the backend

@Hogue this seems to be expected behaviour. PAWS spawns containers for each user based on a pre-built image, every time that container is restarted the image will not have packages installed in its previous generations. The same is true for python packages installed with pip or any other package manager. If there are R packages that would benefit users to have pre-installed we can add them to the image.

as a 4 year old ticket I'm assuming it no longer is an issue.

I am bit worried of us going in the direction of depending more on jupyter notebook classic interface while the jupyter community seems to be discussing how it will declare its abandonment.

Fixed in https://github.com/toolforge/video2commons/pull/141

@mdipietro The commit I made there should be enough to fix the label issue. Not sure about other issues, such as the hub image build.

So I worked a bit on this but didn't finish it, at the end I've noticed @yuvipanda ran into this a few months ago https://github.com/berkeley-dsep-infra/datahub/pull/2264/files

With @Andrew and @LucasWerkmeister helping we have ported the frontend to python3 and its running in toolforge. This particular error is gone. I do expect some other error to show up, please report it and we can try and deal with it.

In T292672#7406964, @Bstorm wrote:

I see your problem with the new setup:

automountServiceAccountToken: false

By not mounting the SA token, there's no "volumes" item in your pod. If there's no volumes item, you cannot do an "add" operation, which is what the mutating webhook controller does.

The maximum file size for any file on Commons is 4 GiB (4,294,967,296 bytes[1]).

While nowhere near the same domain knowledge as @zhuyifei1999 has I think I can take the mantle of maintaining it on life support for the time being. Medium term I think this is the kind of tool with enough complexity and popularity that it needs a team to dedicate professional resources to it. I am hoping Wiki Movimento Brasil can eventually fulfill that role, but that depends on annual plan grants.

Only @Matanya and @Andrew are admins in the vps project. On IRC it was mentioned porting video2commons frontend to python3 as an alternative to hosting the current python2 frontend in the project.

Video2commons still uses python 2. I could not get it to work in Toolforge. Will try to move the front-end to the vps project this week.

I think this is not relevant to PAWS as we don't have mono installed. Please correct me if this is wrong.

Investigating if any workaround while using python 2 is feasiable.

Q34069 is protected to autoconfirmed users though. The edit was probably blocked due to that and the error message is unhelpful.

Doesn't seem to be the same thing as T233168. IE https://pt.wikipedia.org/wiki/Asquenazes is linked to https://www.wikidata.org/wiki/Q34069

@Xeno This has been fully blocked by your team since June 3rd, when I sent you and others on the UCoC facilitation team an email

In T281977#7087999, @Nemo_bis wrote:

including moving their extension to Gerrit if they want

Yep https://public.paws.wmcloud.org/User:Arjunaraocbot/replace.py is the culprit. Delete it and you should be good to go.

this is a weird error to be having in PAWS, seems you're using an outdated version of the replace.py script with PAWS updated pywikibot library. Is it possible you downloaded an old version of the pywikibot at some point into your PAWS home folder?

In T283443#7124711, @Majavah wrote:

The list in T283443#7108018 is missing GitHub merge access

Quay.io access to the repo is also a thing we should provide if there is interest by @yuvipanda

The timeout is now 24 hours. This will be an experiment and we might need to reduce it, but the intention is to support more long running tasks in PAWS.

I was going to add github repo write access to the request but it's already there.

https://github.com/toolforge/paws/pull/62 solved this.

@yuvipanda's https://github.com/toolforge/paws/pull/66 should improve things here. Next step would be to add a button for the link in the PAWS public page.