News

Ruby 3.3.5 Released

by

Ruby 3.3.5 has been released.

This is a routine update that includes minor bug fixes.
We recommend upgrading your Ruby version at your earliest convenience.
For more details, please refer to the GitHub release notes.

Release Schedule

As previously announced, we intend to release the latest stable Ruby version (currently Ruby 3.3) every 2 months following a .1 release.

We expect to release Ruby 3.3.6 on November 5th and Ruby 3.3.7 on January 7th. If any significant changes arise that impact a large number of users, we may release a new version earlier than scheduled.

Download

  • https://cache.ruby-lang.org/pub/ruby/3.3/ruby-3.3.5.tar.gz

    SIZE: 22129139
SHA1: 59444476bbe9e789fc777d8fb4dd456bc057604f
SHA256: 3781a3504222c2f26cb4b9eb9c1a12dbf4944d366ce24a9ff8cf99ecbce75196
SHA512: 5c482059628ef9de5d8a6ad4751f8043f2fc2b159b768265be7f3ee0574ad51d9500ee4fc9146c5978fbd51313039c3de39e7b7a4dedc9bcd5d09a41a713f1a7

  • https://cache.ruby-lang.org/pub/ruby/3.3/ruby-3.3.5.tar.xz

    SIZE: 16403660
SHA1: 692bc3188bdb9ec30b8672543961b011d699590a
SHA256: 51aec7ea89b46125a2c9adc6f36766b65023d47952b916b1aed300ddcc042359
SHA512: dd5c6a7f74854e143e0ca46b9d7c0d1983fc4886f5f733cd108345dbf4b21f61ad978ad6806e05a57b7af28fd9216dd38d7145808188bbb3695a7f3a4eda3883

  • https://cache.ruby-lang.org/pub/ruby/3.3/ruby-3.3.5.zip

    SIZE: 27020194
SHA1: ccb32746aef491ce05be42218301e2c47185e5fc
SHA256: d3c13e124707494935d00ebc5c7983b0252bc13de49223fd31104ba5467a057a
SHA512: bf83af835a74283aff21042538ee1f1eb70ff12dac1edd4672d787547cd29cb7b69a9299682f89c8499eb610737b10a7fc03eca038574cb4ba565205d96b0016

Release Comment

Many committers, developers, and users who provided bug reports helped us make this release.
Thanks for their contributions.

Posted by k0kubun on 3 Sep 2024

libffcall @ Savannah: GNU libffcall 2.5 is released

by

libffcall version 2.5 is released.

New in this release:

  • Added support for the following platforms: (Previously, a build on these platforms failed.)
    • loongarch64: Linux with lp64d ABI.
    • riscv64: Linux with musl libc.
    • hppa: Linux.
    • powerpc: FreeBSD, NetBSD.
    • powerpc64: FreeBSD.
    • powerpc64le: FreeBSD.
    • arm: Android.

  • Fixed support for the following platforms: (Previously, a build on these platforms appeared to succeed but was buggy.)
    • ia64: Linux.
    • arm64: OpenBSD.

  • Simplified the environmental requirements (the library no longer allocates a temporary file in /tmp) on the following platforms:
    • Linux.
    • macOS.
    • FreeBSD 13 and newer.
    • NetBSD 8 and newer.

What we can learn from vintage computing

by
Thanks to open source, no technology ever has to become obsolete, so long as a community remains to support it. You can sync Newtons and Palm Pilots with modern desktops, download web browsers for long-discontinued operating systems, or connect vintage computers like the Apple IIe to the modern internet via WiFi. Every year, new cartridges are released for old-school video game consoles like the Nintendo Entertainment System and Game Boy. People keep old software and online platforms alive as well. The Dreamwidth team forked an old version of the early social network LiveJournal’s source code and built a community around it. The dial-up bulletin board system software WWIV is still maintained and there are plenty of BBSes still around. Teams are working to restore aspects of early online services like AOL and Prodigy. And you can still use Gopher, the hypertext protocol that was — for a brief period in the early 1990s — bigger than the web. ↫ Klint Finley Retrocomputing is about a lot of things, and I feel like it differs per person. For me, it’s a little bit of nostalgia, but primarily it’s about learning, and experiencing hardware and software I was unable to experience when they were new, either due to high cost or just general unavailability. There’s a lot to learn from platforms that are no longer among us, and often it helps you improve your skills with the modern platforms you do still use. The linked article is right: open source is playing such a massive role in the retrocomputing community. The number of open source projects allowing you to somehow use decades-old platforms in conjunction with modern technologies is massive, and it goes far beyond just software – projects like BlueSCSI or very niche things like usb3sun highlights there’s also hardware-based solutions for just about anything retro you want to accomplish. And we really can’t forget NetBSD, which seems to be the go-to modern operating system for bringing new life to old and retro hardware, as it often runs on just about anything. When I got my PA-RISC workstation, the HP Visualize c3750, I couldn’t find working copies of HP-UX, so I, too, opted for NetBSD to at least be able to see if the computer was fully functional. NetBSD is now a tool in my toolbox when I’m dealing with older, unique hardware. Retrocomputing is in a great place right now, with the exception of the ballooning prices we’re all suffering from, with even successful mainstay YouTubers like LGR lamenting the state of the market. Still, if you do get your hands on something retro – odds are there’s a whole bunch of tools ready for you to make the most of it, even today.

Como usar os Aromas na Meditação? – Meditantes PodCast #35

by
Episódio completo em: https://www.youtube.com/watch?v=veGUXtnAXrc&list=PLjXLCSmO7rtqVsiCq4hYS_Fi-8Yk0352a

*Aromas na Meditação, para apoiar nas Práticas Meditativas?*
.
*Episódio 35:* 27/11/2023 (segunda-feira)
*Convidado:* Fabian Lazlo
*Apresentação:* Domício Shanti-Rham
.
Acessa, Inscreva-se, Ative as Notificações, Curte, Comenta e Compartilha!
.
Meditantes PodCast – Experiências em Meditação!
https://meditantes.com.br
.
.
#meditantespodcast, #soumeditante, #shantirham, #podcast, #meditantes, #meditação, #meditation #meditacion #meditacion #meditante, #meditar, #medite, #comomeditarcorretamente, #comomeditar #queromeditar #meditacãoonline #meditaçãoguiada #meditaçãoativa #meditaçãodiaria #meditacãotranscendental, #meditaçãomatinal, #mindfulness, #medite #atençãoplena, #aquieagora, #presente, #presença, #relaxamento, #calma, #tranquilidade, #aovivo, #online #fácil #paratodos

4.5 QA testing cycle starts today!

by
by Simey Lameze.  

Hello Moodle community,

We’re excited to announce that our Moodle 4.5 QA cycle starts today, September 2nd, and will run for five weeks until the release date on October 7th.

About the QA Cycle
The QA cycle is a key part of our development process. This is when our community helps test Moodle’s next version to ensure it’s of the highest quality, reliability, and usability.

How You Can Help
Here’s how you can get involved and make a difference:

  • Exploratory Testing: Try out the latest Moodle features on our QA testing site. Experiment, explore, and share your feedback with us.
  • Issue Reporting: If you find any issues, big or small, please report them on the Moodle Tracker. Your input is crucial to improving Moodle.

For detailed instructions on the QA testing process, please check out the QA testing guide. If you have any questions, feel free to post in this forum or join our Moodle QA chat on Telegram or Matrix.

Thank you for being an essential part of our testing process. Together, we can make Moodle 4.5 a fantastic release! 😊

#! code: Drupal 11: Batch Processing Using Drush

by

This is the second part of a series of articles looking at the Batch API in Drupal. The Batch API is a system in Drupal that allows data to be processed in small chunks in order to prevent timeout errors or memory problems.

In the previous article we looked at how to setup the batch process using a form, with the batch methods being contained within the structure of the form class. When the form was submitted the batch process ran through 1,000 items and then printed out a result at the end.

Whilst there is nothing wrong with running the Batch API with everything in a form class, it is normally better to abstract the batch processing code into a separate class.

Using a separate batch class to contain the process and finish methods is a much better way of setting things up as it allows you to abstract away the batch process from the action that starts it. This means that you can start the batch from anywhere, even a Drush command.

Allowing you batch processes to be run via Drush is a really powerful feature for a module to include. It means that any big process that can be run by a user can be run automatically via a Drush command.

The Batch Class

To create a batch class I normally create a directory called “Batch” inside the module “/src” directory that contains any batch class I need to define. The contents of the class are the two batch methods from the form class used previously, namely the batchProcess() and batchFinished() methods.

The following shows the basic structure of this class.

Read more