Wikitech-l

wikitech-l@lists.wikimedia.org

26 participants
23119 discussions

[Toolforge][GRID SHUTDOWN] Toolforge Grid Engine has been shutdown
by Bryan Davis 15 Mar '24

15 Mar '24

As of 2024-03-14T11:02 UTC the Toolforge Grid Engine service has been shutdown.[0][1] This shutdown is the culmination of a final migration process from Grid Engine to Kubernetes that started in in late 2022.[2] Arturo wrote a blog post in 2022 that gives a detailed explanation of why we chose to take on the final shutdown project at that time.[3] The roots of this change go back much further however to at least August of 2015 when Yuvi Panda posted to the labs-l list about looking for more modern alternatives to the Grid Engine platform.[4] Some tools have been lost and a few technical volunteers have been upset as many of us have striven to meet a vision of a more secure, performant, and maintainable platform for running the many critical tools hosted by the Toolforge project. I am deeply sorry to each of you who have been frustrated by this change, but today I stand to celebrate the collective work and accomplishment of the many humans who have helped imagine, design, implement, test, document, maintain, and use the Kubernetes deployment and support systems in Toolforge. Thank you to the past and present members of the Wikimedia Cloud Services team. Thank you to the past and present technical volunteers acting as Toolforge admins. Thank you to the many, many Toolforge tool maintainers who use the platform, ask for new capabilities, and help each other make ever better software for the Wikimedia movement. Thank you to the folks who who will keep moving the Toolforge project and other technical spaces in the Wikimedia movement forward for many, many years to come. [0]: https://sal.toolforge.org/log/DrOgPI4BGiVuUzOd9I1b [1]: https://wikitech.wikimedia.org/wiki/Obsolete:Toolforge/Grid [2]: https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation#… [3]: https://techblog.wikimedia.org/2022/03/14/toolforge-and-grid-engine/ [4]: https://lists.wikimedia.org/pipermail/labs-l/2015-August/003955.html Bryan, on behalf of the Toolforge administrators -- Bryan Davis Wikimedia Foundation Principal Software Engineer Boise, ID USA [[m:User:BDavis_(WMF)]] irc: bd808

2 2

Reminders about Wikimedia Wishathon
by Srishti Sethi 14 Mar '24

14 Mar '24

Hello, We are now only three weeks away from the Wikimedia Wishathon! Exciting news - User:Lucas Werkmeister has signed up to host a piano concert during a social hour 🎉 Join us and contribute to the development of community wishes between March 15th and 17th! Participate in discussion sessions and work on user scripts, gadgets, extensions, tools and more! The full event schedule is available here: < https://meta.wikimedia.org/wiki/Event:WishathonMarch2024>. Explore the event wiki for project ideas and keep an eye out for non-technical tasks (documentation and design-related) that will soon be added to the Wishathon workboard: < https://phabricator.wikimedia.org/project/view/5906/>. Project breakouts will also be added to the schedule, where you can participate in wish development or explore innovative solutions as a user, developer, or designer. We are seeking volunteers to assist with a wide range of activities such as monitoring discussion channels during hacking hours, answering technical queries, and helping with session note-taking. Check out the Help desk schedule and add yourself to a slot where you are available and interested in providing assistance: < https://meta.wikimedia.org/wiki/Event:WishathonMarch2024/Help_desk>. If you have any questions about the Wishathon, reach out via Telegram: < https://t.me/wmhack>. Cheers, Srishti On behalf of the Wishathon organizing committee *Srishti Sethi* Senior Developer Advocate Wikimedia Foundation <https://wikimediafoundation.org/>

1 2

api error
by Tim Moody 13 Mar '24

13 Mar '24

If I access https://en.wikipedia.org/w/api.php?action=visualeditor&mobileformat=html&fo… I get back Error Our servers are currently under maintenance or experiencing a technical problem. Please try again in a few minutes. See the error message at the bottom of this page for more information. If you report this error to the Wikimedia System Administrators, please include the details below. Request ID: 11569b5b-b74f-4cff-8e28-836d18914c30 Allowed memory size of 1468006400 bytes exhausted (tried to allocate 20480 bytes) However https://en.wikipedia.org/wiki/Timeline_of_the_COVID-19_pandemic_in_Canada does return a page If I access https://en.wikipedia.org/w/api.php?action=visualeditor&mobileformat=html&fo… I get legitimate json. So the api does seem to be working. And https://en.wikipedia.org/wiki/Gout returns a page I'm not sure how to proceed. After a number of hours it has not yet resolved.

2 1

Adding Docker images to the registry via Gitlab
by Sebastian Berlin 12 Mar '24

12 Mar '24

I'm trying to use the new workflow for uploading Docker images to the registry. Following the link under wikitech:Docker-registry#Downloading images <https://wikitech.wikimedia.org/wiki/Docker-registry#Downloading_images> I ended up on mw:GitLab/Workflows/Deploying services to production <https://www.mediawiki.org/wiki/GitLab/Workflows/Deploying_services_to_produ…> as the recommended way to do it. As far as I can tell the service repos should live under repos/mediawiki/services/ in Gitlab and you need to have access to the group to import repos there. I clicked on "Request access" in the menu for that group, but I don't think anything has happened since then. Is there anything else I need to do to be granted access? For context, the service I want to add Docker image for is part of Speechoid, a service bundle(?) for Wikispeech <https://www.mediawiki.org/wiki/Extension:Wikispeech>. Currently we have a few other services that have their code on Gerrit <https://gerrit.wikimedia.org/r/admin/repos/q/filter:wikispeech>. *Sebastian Berlin* Utvecklare/*Developer* Wikimedia Sverige (WMSE) E-post/*E-Mail*: sebastian.berlin(a)wikimedia.se Telefon/*Phone*: (+46) 0707 - 92 03 84

2 3

debian 12 VPS cron
by Tim Moody 10 Mar '24

10 Mar '24

On my debian 11 VPS cron.service is running and there is an /etc/crontab. Same is true on debian 12 machines at home. On my debian 12 VPS cron.service is not running and there is no /etc/crontab. However /etc/cron.daily, etc. exist and have scripts. In the past crontab also controlled daily, etc. Does the cron package need to be installed or is there another mechanism?

1 1

Hello, World!
by Andres Resendez 10 Mar '24

10 Mar '24

yarn add @web3-onboard/core @web3-onboard/injected @web3-onboard/transaction-preview https://registry.npmjs.org/@web3-onboard%2finjected npm i @web3-onboard/core @web3-onboard/injected @web3-onboard/transaction-preview import Onboard from '@web3-onboard/core' import injectedModule from '@web3-onboard/injected-wallets' import { ethers } from 'ethers' const MAINNET_RPC_URL = 'https://mainnet.infura.io/v3/<INFURA_KEY>' const injected = injectedModule() const onboard = Onboard({ wallets: [injected], chains: [ { id: '0x1', token: 'ETH', label: 'Ethereum Mainnet', rpcUrl: MAINNET_RPC_URL }, { id: '0x2105', token: 'ETH', label: 'Base', rpcUrl: 'https://mainnet.base.org' } ] }) const wallets = await onboard.connectWallet() console.log(wallets) if (wallets[0]) { // create an ethers provider with the last connected wallet provider const ethersProvider = new ethers.providers.Web3Provider(wallets[0].provider, 'any') // if using ethers v6 this is: // ethersProvider = new ethers.BrowserProvider(wallet.provider, 'any') const signer = ethersProvider.getSigner() // send a transaction with the ethers provider const txn = await signer.sendTransaction({ to: '0x', value: 100000000000000 }) const receipt = await txn.wait() console.log(receipt) } npm i @web3-onboard/core @web3-onboard/injected-wallets npm audit fix --force accountCenter: { desktop: { enabled: true, position: 'topRight' }, mobile: { enabled: true, position: 'topRight' } }https://explorer.blocknative.com/account//mainnet.infura.io/v3/ <INFURA_KEY.state.get()

1 0

[GRID SHUTDOWN] Grid Engine Is Shutting Down On The 14th Of March
by Seyram Komla Sapaty 09 Mar '24

09 Mar '24

Hello all, We are on the last stretch of the grid engine deprecation process[0] and this means that the grid will be shutting down on Thursday, the 14th of March. You can find a reminder of the full timeline here[1] There's about 30 tools still running on the grid, if you are one of the few left to migrate, kindly ensure they are migrated before the 14th or reach out[2] to the team if you are facing any challenges or need some assistance. We have also reached out on phabricator and via email to the remaining maintainers that still have their tools running on the grid to see if we can help ease the migration or see if there are any blocking issues. If you have a tool that is still on the grid and you cannot meet the above deadline, kindly reach out via the tool migration phabricator ticket or our support channels[2], note that this is a hard deadline and no extensions would be granted but we might be able to help you do the transition. We really appreciate all the effort and feedback given on the new platform, this will help us improve our service and reduce the maintenance burden in the long term for tool maintainers and toolforge admins alike. [0]: https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation [1]: https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation#… [2]: https://wikitech.wikimedia.org/wiki/Portal:Toolforge/About_Toolforge#Commun… -- Seyram Komla Sapaty Developer Advocate Wikimedia Cloud Services

1 0

Changes to JavaScript documentation tools
by Alexandra Paskulin 08 Mar '24

08 Mar '24

Hi everyone, tl;dr The tools we use to document Wikimedia JavaScript code are changing. In the short term, you can read the complete MediaWiki core JavaScript docs using the 1.41 version[0] while we migrate to the new system[1]. If you use JavaScript documentation on doc.wikimedia.org, please share your feedback on wiki[2]. Wikimedia JavaScript codebases are switching from using JSDuck[3] to JSDoc[4] for documentation. Started in 2016, this migration is necessary because JSDuck is currently unmaintained and does not support the ES6 standard[5]. Several Wikimedia JavaScript codebases, including Vector and GlobalWatchlist, already use JSDoc, while several others, such as VisualEditor and MediaWiki core, still use JSDuck. The migration project consists of two parts: changing the codebases to support JSDoc and improving the usability of the JSDoc WMF theme. For more information, see phab:T138401[6]. == Migrating MediaWiki core to JSDoc == We are migrating MediaWiki core to JSDoc incrementally. While the migration is in progress, the master branch docs will be incomplete, containing only those modules that have been migrated. To read the old JSDuck docs, see the MediaWiki 1.41 docs[0]. To help with migration, choose a module from the list in phab:T352308[7], and follow the guide on phab:T138401[6] to translate the tags from JSDuck to JSDoc. == Migrating other codebases == You can find a list of codebases that use JSDuck on phab:T138401[6]. (Please add any that are missing.) To help migrate a codebase that uses JSDuck, follow the instructions to set up JSDoc[8], and use the guide in phab:T138401[6] to translate the tags from JSDuck to JSDoc. == Improving the JSDoc WMF theme == One of the biggest differences between JSDuck and JSDoc is the HTML interface for reading the docs. The WMF theme for JSDoc is not as full-featured as the JSDuck theme, but to support this migration, the Wikimedia Foundation Web, Design Systems, and Technical Documentation teams are working to prioritize and complete a set of improvements to the JSDoc theme, with the goal of releasing version 1 of jsdoc-wmf-theme in 2024. If you use JavaScript documentation on doc.wikimedia.org, please leave a comment on the JSDoc WMF theme talk page[2] and let us know how you use the docs and which features of the theme are the most important to you. Thank you for reading! Alex, Kamil, Jon, Roan, and Anne [0]: https://doc.wikimedia.org/mediawiki-core/REL1_41/js/ [1]: https://doc.wikimedia.org/mediawiki-core/master/js/ [2]: https://www.mediawiki.org/wiki/Talk:JSDoc_WMF_theme [3]: https://github.com/senchalabs/jsduck [4]: https://en.wikipedia.org/wiki/JSDoc [5] https://en.wikipedia.org/wiki/ECMAScript [6]: https://phabricator.wikimedia.org/T138401 [7]: https://phabricator.wikimedia.org/T352308 [8]: https://www.mediawiki.org/wiki/JSDoc -- Alex Paskulin Technical Writer Wikimedia Foundation

1 1

Scheduled production gitlab-cloud-runners cluster upgrade to 1.29 at 1 PM EST
by Sandeep Singh 08 Mar '24

08 Mar '24

Good Morning everyone, As part of task T359594 <https://phabricator.wikimedia.org/T359594>, I wanted to inform you that we are scheduled to upgrade our production gitlab-cloud-runners cluster to 1.29 today at 1 PM EST. This process will be conducted manually through the DigitalOcean Console, and is expected to complete by 2 PM EST. Please Note: 1. CI jobs might experience disruptions during this upgrade window. 2. After the upgrade, I will update the Terraform configuration to match the updated cluster version. Thank you for your understanding. -- Sandeep Singh (he/him) Software Engineer, Release Engineering. Wikimedia Foundation

1 0

1.42.0-wmf.21 train is blocked
by Jaime Nuche 07 Mar '24

07 Mar '24

Hi there, The 1.42.0-wmf.21 version of MediaWiki is once again blocked at group1 due to: - https://phabricator.wikimedia.org/T359509: REST API calls suddenly all returning 400 A previous attempt at a fix didn't work: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1009500 Thank you for your help resolving this issue! -- Your distraught train conductor -- Jaime Nuche Software Engineer III Wikimedia Foundation <https://wikimediafoundation.org/>

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l