Author: Michael G

Rails 7.2 allows to add custom blob key in the ActiveStorage::Blob APIs

Ruby 3.3.3 has been released.

This release includes:

• RubyGems 3.5.11
• Bundler 2.5.11
• REXML 3.2.8
• strscan 3.0.9
• --dump=prism_parsetree is replaced by --parser=prism --dump=parsetree
• Invalid encoding symbols raise SyntaxError instead of EncodingError
• Memory leak fix in Ripper parsing
• Bugfixes for YJIT, **{}, Ripper.tokenize, RubyVM::InstructionSequence#to_binary, --with-gmp, and some build environments

Please see the GitHub releases for further details.

Download

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

  SIZE: 22105219
  SHA1: b71971b141ee2325d99046a02291940fcca9830c
  SHA256: 83c05b2177ee9c335b631b29b8c077b4770166d02fa527f3a9f6a40d13f3cce2
  SHA512: 0388a96127eb6e53b836f7954af51ff62b84cdb7abeab823cb1349993d805b151204e426b9ac04ca8333fbd5e01c386d58bc37d34c4e9286b219dcda7542a150
  

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

  SIZE: 16361160
  SHA1: 70cc5db132ea277487ede490e430e066a7c862d9
  SHA256: 83c0995388399c9555bad87e70af069755b5a9d84bbaa74aa22d1e37ff70fc1e
  SHA512: 27dcae604e6613e1eaa20c6a75ee88b970bb0dd584d9bc0c021ad8da4340858e3c2e874ac841fcca0b0444a0c0146c4650d2d22bac3c9e12853533c37255f8f1
  

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

  SIZE: 26990910
  SHA1: 15a903003fba2fa5ae760263d6aa7b951747e545
  SHA256: a9e4a6650cc40643b2b4a005541587443e373fbdec0c03164502f710cfd87a01
  SHA512: ed5ed5bc26598ba8c39eaae45147159d742e4792d4d8478b2db04bffe25b75b8bd4131a86c010bff91e0368f906bff04e852deab415fefd25cec39bc53f70020
  

Release Comment

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

Posted by k0kubun on 12 Jun 2024

Save on Technical Training & Certification Learn more at Linux Foundation Training

The post Kickstart Your Career & Save Up To 40%! appeared first on Linux.com.

This week, we continued discussions about the role of training data in open source AI. Missed it? Catch up here!

A few days ago, I was pointed to a post on the Mozilla forums, in which developers of Firefox extensions designed to circumvent Russian censorship were surprised to find that their extensions were suddenly no longer available within Russia. The extension developers and other users in the thread were obviously not amused, and since they had received no warning or any other form of communication from Mozilla, they were left in the dark as to what was going on. I did a journalism and contacted Mozilla directly, and inquired about the situation. Within less than 24 hours Mozilla got back to me with an official statement, attributed to an unnamed Mozilla spokesperson: Following recent regulatory changes in Russia, we received persistent requests from Roskomnadzor demanding that five add-ons be removed from the Mozilla add-on store. After careful consideration, we’ve temporarily restricted their availability within Russia. Recognizing the implications of these actions, we are closely evaluating our next steps while keeping in mind our local community. ↫ Mozilla spokesperson via email I and most people I talked to already suspected this was the case, and considering Russia is a totalitarian dictatorship, it’s not particularly surprising it would go after browser extensions that allow people to circumvent state censorship. Other totalitarian dictatorships like China employ similar, often far more sophisticated methods of state control and censorship, too, so it’s right in line with expectations. I would say that I’m surprised Mozilla gave in, but at the same time, it’s highly likely resisting would lead to massive fines and possible arrests of any Mozilla employees or contributors living in Russia, if any such people exist, and I can understand a non-profit like Mozilla not having the means to effectively stand up against the Russian government. That being said, Mozilla’s official statement seems to imply they’re still in the middle of their full decision-making process regarding this issue, so other options may still be on the table, and I think it’s prudent to give Mozilla some more time to deal with this situation. Regardless, this decision is affecting real people inside Russia, and I’m sure if you’re using tools like these inside a totalitarian dictatorship, you’re probably not too fond of said dictatorship. Losing access to these Firefox extensions through the official add-store will be a blow to their human rights, so let’s hope the source code and ‘sideloaded’ versions of these extensions remain available for them to use instead.