A long time coming! The interface looks amazing and seems very well thought
out. It's nice to have an official, single go-to for all things tools, user
scripts, gadgets, etc. Huge thanks and kudos to everyone involved!
~ MA
On Thu, Oct 14, 2021 at 3:37 PM Galder Gonzalez Larrañaga <
Hello again! Thinking about this more, I'm wondering if it makes sense to
have a tool to assist with parsing the dblists at noc.wikimedia.org. I know
the official recommendation is to not to connect to slices, but the issue
is how to work locally. I alone maintain many tools that are capable of
On Thu, Nov 19, 2020 at 12:44 AM MusikAnimal wrote:
> Hello Joaquin!
>
> Hey MA, I've checked, and while not explicitly disallowed, the fact that
>> this could work is more of an implementation detail that shouldn't really
>> be relied on.
>>
>> The sections an
Hello Joaquin!
Hey MA, I've checked, and while not explicitly disallowed, the fact that
> this could work is more of an implementation detail that shouldn't really
> be relied on.
>
> The sections and where the instances are on them are organized to maintain
> the service, and are not supposed to
Technically, cross-wiki joins aren't completely disallowed, you just have
to make sure each of the db names are on the same slice/section, right?
~ MA
On Wed, Nov 11, 2020 at 4:11 PM Maarten Dammers wrote:
> Hi Joaquin,
> On 10-11-2020 21:26, Joaquin Oltra Hernandez wrote:
>
> TLDR: Wiki
or noc.wikimedia.org if that fails, perhaps? Meta_p is expected to
> be on s7 in the new design.
>
> Brooke Storm
> Staff SRE
> Wikimedia Cloud Services
> bst...@wikimedia.org
> IRC: bstorm
>
> On Nov 10, 2020, at 3:01 PM, MusikAnimal wrote:
>
> Ah yes, 8 tunnels is more th
Hi! Most tools query just a single db at a time, so I don't think this will
be a massive problem. However some such as Global
Contribs[0] and GUC[1] can theoretically query all of them from a single
request. Creating new connections on-the-fly seems doable in production,
the issue is how to work
When I go to any patch I see the non-fatal error "Plugin install error:
TypeError: self.onAction is not a function from
https://gerrit.wikimedia.org/r/plugins/delete-project/static/delete-project.js
"
I was about to create a Phabricator task for this, then realized the issue
was my browser's
Y/iJTQUOhcWr7x9JvoRxT2MZw1T">
>
> and similar changes for the other linked-to resources. Two specific
> questions:
>
>- The integrity token is the same, no matter which mirror I get it
>from?
>- I can drop the crossorigin attribute since I'm not doing C
> most if not all of the CSS and Javascript didn't load because of cross
site scripting failures
The Content Security Policy violations are report-only, if that's what
you're referring to. Popper, Bootstrap, jQuery and Selectize are all
available via https://cdnjs.toolforge.org/ which will get
Is the source code public? Maybe the queries could be improved. I ran into
many such issues too after the actor migration, but after taking advantage
of specialized views[0] and join decomposition (get just the actor IDs,
i.e. rev_actor, then the actor_names in a separate query), my tools are
11 matches
Mail list logo
