How to walk to LaGuardia Airport in New York City - Curbed NY
Queue backlog has been fully processed at 19:46 UTC.
Since then, our instance process events normally.
The home feeds have been rebuilt so we're sure they are coherent and in chronological order.
All looks good since.
Timeline is currently updating again.
I increased the workers amount, provisioning a new machine to temporarily help to process the queue. With that, we currently process 30 tasks / seconds.
That means with 130 000 tasks to process, plus a little bit for the new tasks incoming, in 2 hours, queue will be empty.
We've got a queue incident on the Mastodon instances.
Some users on plemora pushed HUGE mp4 videos, and the queue was stucked to process them.
That gave processes like 97.2% CPU and 300 Mb RAM running dozens of minute hour each (the server isn't optimized for video rendering).
And so while video convert occurred, all the workers are busy, and we don't have timeline updates.
No data is lost, as all is saved in Redis as jobs to process.
Hey a green fireball-like #meteor spotted from E to ESE :) Cool view.
#maintenance Show more
Mastodon instance updated to 2.6.1
Write-in du mercredi soir #NaNoWriMo
Pendant que j'avais le dos tourné l'excellent @Calimaq a écrit un article passionnant, vas donc voir :
So a #NaNoWriMo kick-start, it's a badge, a bingo card and some challenge words to put in the story.
Still one Python workshop to give then I can go to our local #NaNoWriMo kick start event.
An evening to eat chat play board games meet each other. Then at midnight we start writing.
@Fralambert Depuis la mise à jour, j'ai l'impression que la colonne Local timeline se charge sans aucun souci (mais vu que c'est la première qui s'affiche parfois, j'imagine que c'est juste qu'elle est en cache du navigateur en local storage ou autre ?)
Mastodon instance is now up-to-date.
newjack.city flood Show more
I wondered why newjack.city bots weren't followed me.
Apparently, the secret trigger was to post on the federated timeline without a mention.
Database migration status update Show more
So the very slow PostgreSQL migration to get statuses statistics is done, with 100973033896636693 the last status ID.
"some hours" release notes said. Indeed, that's correct, at least for a definition of "some" still accepting 80.
Currently, the migration code is busy with ~6 156 470 rows for silent mentions, with an announced time of 13 minutes remaining.
Infrastructure, devops, social justice, free culture, Wikimedia.
Nasqueron is a budding community of creative people, writers, developers and thinkers. We focus on free culture, ethics and to be a positive change. We share values like respect, justice and equity.