> My guess is that you are seeing this because your jobs are now running
on a new set of Cloud VPS instances (the Toolforge Buster grid engine
exec nodes) and these new instances have IP addresses that the wikis
have not seen you use before.
I see there are 10 exec nodes for Buster (tools-sgeexec-
OAuth gets around this. If you login with OAuth, those emails don’t happen at
all.
Cyberpower678
English Wikipedia Administrator
English Wikipedia Interface Administrator
> On Feb 16, 2022, at 11:49, Bryan Davis wrote:
>
> On Wed, Feb 16, 2022 at 5:43 AM Peter Bowman wrote:
>>
>> Hello. Y
On Wed, Feb 16, 2022 at 5:43 AM Peter Bowman wrote:
>
> Hello. Yesterday, I started scheduling my cron jobs on the grid with the
> `--release buster` option (previously was defaulting to Stretch). I have
> gotten dozens of "Someone (probably you) recently logged in to your account
> from a new
I can see already that trying to migrate to this new toolforge-jobs framework
is going to be a long and winding road.
First of all, the documentation on "choosing the execution runtime" leaves much
to be desired. There is a list of 23 available runtimes to choose from, but no
guidance on how to
From my perspective of a Toolforge user, one of the issues I see is that it's
often not clear how to map the "friendly command line interface" into concepts
I already understand about the lower level tools.
For example, the webservice script does some useful stuff. But, it wasn't
clear exactly
On 2/15/22 21:46, Maarten Dammers wrote:
Hi,
Why are we upgrading to Buster instead of Bullseye? According to
https://wikitech.wikimedia.org/wiki/Operating_system_upgrade_policy
Buster will be end of life around August this year.
So we're either stuck with an older version for a while or we ha
Hello. Yesterday, I started scheduling my cron jobs on the grid with the
`--release buster` option (previously was defaulting to Stretch). I have
gotten dozens of "Someone (probably you) recently logged in to your account
from a new device" notifications since then. Can I do anything to stop this
o
I was looking at this a couple months back, and ended up writing the oauth
dance myself:
https://github.com/david-caro/wm-what/blob/main/wm_what/app.py#L162
Seemed simpler given the lack of maintenance, and given that I just needed a
very simple integration (using flask
though).
On 02/11 22:2
