Hello, is it possible to svn up the
/home/wporg/public_html/ directory on all sandboxes?
There was a change in core to
WP_Site which got reverted later. A sandbox which still has the old
WP_Site will pollute the cache with a broken object which ends in a site_id = 0 entry in the database and making the site inaccessible.
See https://wordpress.slack.com/archives/core-multisite/p1467394608000460 for background.
There are no cache instructions on SVGs on the CDN, could you please add some on?
$ curl -I https://s.w.org/images/core/emoji/2/svg/1f937.svg
HTTP/1.1 200 OK
Date: Wed, 20 Jul 2016 05:44:19 GMT
Last-Modified: Mon, 18 Jul 2016 07:14:38 GMT
Server: ECS (syd/EBEC)
X-nc: MISS lax 186
The cache can be set to a long time without causing problems, I’m fine with a month or more.
Also, I’m not sure if it’s possible/desired to compress the data, but I imagine SVGs will compress moderately well.
Hello! @adityakane is a new super deputy for the community team and he needs proxy access. His public key is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDJRKfcLQ4RmBTyw+z0gpVGkd6TEISbVoFYgBW//olFw78eyt1JjfmNQJBUmn2xpxzIjUjSOEHxSwXbqT4no1Rj+15ahEpfqeBwhobVAjXoVpuS8XY+prCno5mVI5cEJNF5uwUotLUi8W0ma7LX8Nnev7kKBvNEHJwWP+EPaanJezVjoIgmuK8dOwiejuHXdicF/Z/8tUqH3x+xo7Ljpj5etlVn9zN+yigL55eLv+RXPOH73EAb+jcBAKLLbUroWxqH/ak76fwfwN0Wm9RxWP1OqO2YjxOKDmbxLpoCBsfWFa0zc9Rl9Qce3fBYqapn1SNv6j3BdKx2hnNKb4FehSzV Aditya@Adityas-MacBook-Air.local
Please create a sandbox for @gibrown and give him commit to the meta repository. He will be assisting with Elasticsearch in the plugin directory. You can re-use his Automattic SSH key.
Since switching plugins.svn.wordpress.org linting to PHP7 it looks like the fatal error outputs are not including the actual error, only the fact an error occured. This causes a bit of confusion as some things are being blocked (correctly) with no obvious cause.
Transmitting file data .svn: E165001: Commit failed (details follow):
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:
PHP error in: test-plugin-3/trunk/plugin.php:
Errors parsing test-plugin-3/trunk/plugin.php
svn: E165001: Your commit message was left in a temporary file:
svn: E165001: '/home/www/tmp/sdf/svn-commit.tmp'
In that case, it should’ve included a message of
Fatal error: 'continue' not in the 'loop' or 'switch' context in plugin.php on line 20 (Note: This is one of the new PHP7 parse fatal errors)
This can be tested by attempting to commit to a plugin with a
continue; statement in global scope (for example, a file as
I can’t see the issue in the pre-commit script, but i assume the error is probably going to STDOUT rather than STDERR.
Hi, for an upcoming update of GlotPress I need a new column
user_id_last_modified for the translations table.
ALTER TABLE translate_translations ADD COLUMN user_id_last_modified bigint(20) DEFAULT NULL;
Running this query on my local dump took 9 min 32.67 sec (35207550 rows affected).
@barry: Can you run the query on each server like you did for the index change? Thank you!
Hey folks! It looks like all outgoing e-mail via our SupportPress install on WordCamp.org (support.wordcamp.org) is broken. I’m getting the following error when attempting to send manually via
SMTP Error: Could not connect to SMTP host.
Let me know if you need any additional details, and thanks!
There’s a virus message on the
wp-testers mailing list archive.
(low-priority) Another #https report came in, this time for https://svn.buddypress.org/ which is not using the buddypress cert, but rather than WordPress.org wildcard.
Although https://buddypress.svn.wordpress.org/ is the canonical SVN location, https://svn.buddypress.org/ shows up in search results and is affected by the HTTPSEverywhere-type browser extensions too.
The number of reports for 502 Bad Gateway errors is increasing recently.
My first report for 502 errors was for
https://*.wordpress.org/?fetch-custom-header=/plugins/ requests on Jan 7th. This was solved by @barry, “some memory corruption probably caused by a bug in pecl-memcache that we are working on fixing“.
Around April 3rd I got a few reports for translate.wordpress.org but couldn’t confirm them.
On April 13th I reported that the
https://*.wordpress.org/?fetch-custom-header=/plugins/ issue happens again. This issue is still there, see #dotorg-warnings.
Since this Monday we’re getting reports for 502 Bad Gateway errors on our make sites. For example
https://make.wordpress.org/polyglots/feed/p2.ajax returns a 502 which prevents adding new comments.
But there are also new reports for translate.wordpress.org (when submitting translations) and for localized sites:
The 502 errors do not happen on our sandboxes, only in production. Can someone please look into this? Thank you!