Re: [Toolserver-l] Re-importing of several database clusters

[Platonides]

River Tarnell wrote:
> Hi,
>
> I'm about to re-import several database clusters from WMF: s3, s4, s6
> and s7.  This will be done on the secondary server first, so users won't
> be affected, except that queries on these clusters might be a bit slower
> for a while.
>
> This will resolve the following TS issues:
>
> TS-948 creating of rue.wiki
> TS-926 Cassia and hyacinth are missing the ruewiki-database
> TS-1013 metawiki Database seems to be corrupt
>
> And might resolve the following issues, although they don't provide
> enough information to be sure of the cause:
>
> TS-1024 cswikisource_p needs reimport
> TS-1048 cswiktionary_p needs reimport

cswikisource_p needs reimport is TS-1049, not TS-1024

Also related, TS-1074 (some data missing in s3)
https://jira.toolserver.org/browse/TS-1074

> This reimport might take longer than usual because I will be testing a
> new way of configuring database servers (which hopefully reduce database
> corruption in the future).

Do you know/suspect what caused the corruption? Trainwreck dropped some 
statements, perhaps?

Databases should er... -you know- store data without corrupting it :)

___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

[Toolserver-l] Re-importing of several database clusters

[River Tarnell]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I'm about to re-import several database clusters from WMF: s3, s4, s6 
and s7.  This will be done on the secondary server first, so users won't 
be affected, except that queries on these clusters might be a bit slower 
for a while.

This will resolve the following TS issues:

TS-948 creating of rue.wiki
TS-926 Cassia and hyacinth are missing the ruewiki-database
TS-1013 metawiki Database seems to be corrupt

And might resolve the following issues, although they don't provide 
enough information to be sure of the cause:

TS-1024 cswikisource_p needs reimport
TS-1048 cswiktionary_p needs reimport

This reimport might take longer than usual because I will be testing a 
new way of configuring database servers (which hopefully reduce database 
corruption in the future).

Once this is done, I'll switch user databases to the secondary server 
(during which they will be offline for a couple of hours), and then 
reimport the other server.

s1, s2 and s5 will be done later.

- river.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (SunOS)

iEYEARECAAYFAk4AxugACgkQIXd7fCuc5vIELACdF8k2zkgsakxSo6x+jyrySy2o
KEwAnigGCyqS8td/t7gcQT97wjAwAOvV
=citf
-END PGP SIGNATURE-

___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

Re: [Toolserver-l] Python cgi safery issues

[River Tarnell]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

MZMcBride:
> There's a general expectation that the tools and scripts that you write will
> be released under a free/open source license, but I'm not sure if that's an
> actual requirement ("must") or simply an expectation ("should").

It's preferred, but not required at the moment.

- river.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (SunOS)

iEYEARECAAYFAk4AvMEACgkQIXd7fCuc5vK2nQCfWd4/OIjRkIXzh2B33OPeFf4c
xbEAoLtjr8PZUI9WByx/osYnvVghZkij
=AaN4
-END PGP SIGNATURE-

___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

Re: [Toolserver-l] Python cgi safery issues

[MZMcBride]

Alex Brollo wrote:
> I know python much better than PHP, so I feel myself reasonably comfortable
> with cgi python module dealing with simple tests of html queries. In the
> meantime, I'm worried abut possible safety issues, so what is your suggestion
> to fix any coding/setting mistake? Have I to publish here, or into toolserver
> wiki, my code? As you guess, I'm not so deep into such issues.

It's a bit unclear what you mean by safety issues. I'll assume you mean XSS
vulnerabilities, SQL injection, etc.

It's rather simple, really: sanitize all input and all output. If you do
that, it doesn't really matter how bad or ugly the HTML or CSS is.

You can read 
which has a bit more information about tool security.

As you're working in PHP, you might also find
 useful, though it's
obviously targeted primarily at MediaWiki development.

You should set a default license for your tools/scripts using "setlicense"
and then you can specify licenses for individual tool/scripts as necessary.
There's a general expectation that the tools and scripts that you write will
be released under a free/open source license, but I'm not sure if that's an
actual requirement ("must") or simply an expectation ("should").

If you have specific questions, feel free to ask on this list or IRC.

MZMcBride



___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

Re: [Toolserver-l] Python cgi safery issues

[Mono mium]

No, you don't have to publish the code, but design it with safety in
mind and test protecting against common attacks. You may be interested
in talking to a more experienced developer to take a look, though.

Mono

On Tue, Jun 21, 2011 at 6:05 AM, Alex Brollo  wrote:
> I know python much better than PHP, so I feel myself reasonably comfortable
> with cgi python module dealing with simple tests of html queries. In the
> meantime, I'm worried abut possible safety issues, so what is your
> suggestion to fix any coding/setting mistake? Have I to publish here, or
> into toolserver wiki, my code? As you guess, I'm not so deep into such
> issues.
>
> Thanks!
>
> Alex brollo
>
> ___
> Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
> https://lists.wikimedia.org/mailman/listinfo/toolserver-l
> Posting guidelines for this list:
> https://wiki.toolserver.org/view/Mailing_list_etiquette
>

___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette

[Toolserver-l] Python cgi safery issues

[Alex Brollo]

I know python much better than PHP, so I feel myself reasonably comfortable
with cgi python module dealing with simple tests of html queries. In the
meantime, I'm worried abut possible safety issues, so what is your
suggestion to fix any coding/setting mistake? Have I to publish here, or
into toolserver wiki, my code? As you guess, I'm not so deep into such
issues.

Thanks!

Alex brollo
___
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list: 
https://wiki.toolserver.org/view/Mailing_list_etiquette