March 31, or “three thirty-one,” is something of a talisman in the Mozilla community. It’s the date that, back in 1998, Mozilla first came into being — the date that we open-sourced the Netscape code for the world to use. This year, “three thirty-one” is especially meaningful: It’s Mozilla’s 25 year anniversary. A lot has […]
The post A quarter century of Mozilla appeared first on The Mozilla Blog.
Software development is a social process. What might be a “bug” for
someone might well be a “feature” for someone else. The Guix project
rediscovered it the hard way when, after “fixing a bug” that had been
present in Guix System for years, it was confronted with an uproar in its
user base.
In this post we look at why developers considered the initial behavior a
“bug”, why users on the contrary had come to rely on it, and why
developers remained blind to it. A patch to reinstate the initial
behavior is being reviewed. This
post is also an opportunity for us Guix developers to extend our
apologies to our users whose workflow was disrupted.
Anyone who’s used Guix System in the past has seen this message on the
console during the boot process:
error in finalization thread: SuccessThe following picture shows a typical boot screen (with additional
messages in the same vein):
If you have never seen it before, it may look surprising to you. Guix
System users lived with it literally for years; the message became a
hint that the boot process was, indeed, successful.
A few months ago, a contributor sought to satisfy their curiosity by
finding the origin of the message. It did look like a spurious error
message, after all, and perhaps the right course of action would be to
address the problem at its root—or so they thought.
As it turns out, the message originated in
Guile—check
out the Guile
manual
if you’re curious about finalization. Investigation revealed two
things: first, that this perror call in Guile was presumably reporting
the wrong error code—this was
fixed.
The second error—the core of the problem—lied in Guix System itself.
Remember that, in its quest of memory safety™, statelessness, and fun,
Guix System does it all in Guile Scheme—well, except for the kernel (for
now). As soon as Linux has booted, Guix System spawns Guile to run boot
code that’s in its initial RAM
disk
(“initrd”). Right before executing
shepherd, its service manager, as
PID 1, the initrd code would carelessly close all the file descriptors
above 2 to make sure they do not leak into PID 1. The problem—you
guessed it—is that one of them was the now-famous file descriptor of the
finalization thread’s pipe; the finalization thread would quickly notice
and boom!
error in finalization thread: SuccessOur intrepid developers thought: “hey, we found it! Let’s fix it!”. And
so they
did.
This could have been the end of the story, but there’s more to it than
software. As Xkcd famously captured, this was
bound to break someone’s workflow. Indeed, had developers paid more
attention to what users had to say, they would have known that the
status quo was preferable.
For some time now, users had shown that they held the error/success
message deep in their heart. The message was seen on the blackboard at
the Ten Years of Guix celebration, as a
motto, as a rallying cry, spontaneously put on display:
What’s more, a fellow NixOS hacker and Guix enthusiast, beguiled by this
powerful message, designed
stickers and brought them to FOSDEM in February 2023:
The sticker design builds upon the “test pilot” graphics made by Luis
Felipe for the 1.3.0
release.
The test pilot has a bug on its helmet. In a way, the drawing and error
message both represent, metaphorically, a core tenet of Guix as a
project; just like Haskell is avoiding success at all costs, Guix
seems trapped in an error/success quantum state.
Had it gone too far? Was calling it a “bug” the demonstration of the
arrogance of developers detached from the reality of the community?
Those who installed Guix System starting from version
1.4.0 have
been missing out on the error/success boot message. The patch
submitted today finally reinstates
that message. The review process will determine whether consensus is to
enable it by default—as part of
%base-service—or
whether to make it optional—after all, we also need to accommodate the
needs of new users who never saw this message. This will allow users
to restore their workflow, while also ensuring that those freshly
printed stickers remain relevant.
This incident had broader consequences in the project. It led some to
suggest that we, finally, set up a request-for-comment (RFC) kind of
process that would give all the community a say on important topics—a
process most large free software projects have developed in one form or
another. Such a process could have prevented this incident: instead of
arrogantly labeling it as a “bug”, developers would have proposed an RFC
to remove the message; the discussion period, most likely, would have
made it clear that removal was not a desirable outcome and we would all
have moved on.
This incident made many users uncomfortable, but we are glad that it is
now being addressed. The lessons learned will be beneficial to the
project for the years to come.
Test
pilot
by Luis Felipe distributed under the terms of
CC-BY-SA 4.0;
sticker design distributed under
CC-BY-SA 4.0 as
well. Blackboard picture by Julien Lepiller under
CC0; sticker
pictures under
CC0.Many thanks to the anonymous sticker provider!
GNU Guix is a transactional package manager and
an advanced distribution of the GNU system that respects user
freedom.
Guix can be used on top of any system running the Hurd or the Linux
kernel, or it can be used as a standalone operating system distribution
for i686, x86_64, ARMv7, AArch64 and POWER9 machines.
In addition to standard package management features, Guix supports
transactional upgrades and roll-backs, unprivileged package management,
per-user profiles, and garbage collection. When used as a standalone
GNU/Linux distribution, Guix offers a declarative, stateless approach to
operating system configuration management. Guix is highly customizable
and hackable through Guile
programming interfaces and extensions to the
Scheme language.
#KhutbaeJumma #IslamicInformation #ARYQtv
Watch All The Programs : https://bit.ly/3jmd1RQ
Subscribe Here : https://bit.ly/3dh3Yj1
Official Facebook : https://www.facebook.com/ARYQTV/
Official Website : https://aryqtv.tv/
Watch ARY Qtv Live : http://live.aryqtv.tv/
Programs Shedule : https://aryqtv.tv/schedule/
Islamic Information : https://bit.ly/2MfIF4P
Android App: https://bit.ly/33wgto4
Ios App: https:https://apple.co/2v3zoXW
Baixe o app Panflix: https://www.panflix.com.br/
Baixe o AppNews Jovem Pan na Google Play
https://bit.ly/2KRm8OJ
Baixe o AppNews Jovem Pan na App Store
https://apple.co/3rSwBdh
Inscreva-se no nosso canal:
https://www.youtube.com/c/jovempannews
Entre no nosso site:
http://jovempan.com.br/
Facebook:
https://www.facebook.com/jovempannews
Siga no Twitter:
https://twitter.com/JovemPanNews
Instagram:
https://www.instagram.com/jovempannews/
#JovemPan
#JornalDaManhã
We are looking forward to gathering in person at DrupalCon Pittsburgh!
And current projections show that many will be gathering: registrations are up 32% over last year.
There is much work being done to make DrupalCon Pittsburgh the ultimate Drupal event in North America, one that generates excitement for Drupal and spurs the creativity that abounds within the Drupal Community.
We also recognize that we’re doing this planning work amid rapidly changing pandemic conditions. The Drupal Association has been monitoring COVID-19 trends and has seen a marked decrease in Covid-19 cases both nationally and in Pittsburgh. The CDC reports that weekly cases since January for the U.S. have dropped 67%, and for Allegheny County (which incorporates Pittsburgh), it has dropped 60%. Pittsburgh is currently rated as “low risk” by the CDC. This assessment is matched by the World Health Organization’s trends, which show a significant decline in cases in the U.S.
This is GREAT news! News that I hope makes everyone feel more comfortable in joining us in Pittsburgh.
In January, we updated our health and safety policies prior to opening registration. This update removed a vaccine or daily testing requirement, but retained masking indoors. Let me explain why.
The COVID-19 pandemic forced the Drupal Association to implement extraordinary measures to protect our community. At the same time, we knew the situation would constantly evolve, and our response would also have to evolve. We knew we would have to closely monitor medical, scientific, and public health data and make appropriate changes to the DrupalCon Health and Safety Policies.
We decided early on that we needed a decision rooted in our values: DrupalCon should be a safe, accessible, and inclusive space for everyone in our community. It is often the most vulnerable in our community who are left behind, and so we felt it important to ensure our criteria for policy changes centered on those most at risk.
With that value at heart, we looked at the following criteria:
This last bullet is worth a bit more explanation. The Association realized a decision was needed prior to opening registration for each event and then to stick to the decision. Attendees register with the expectations presented at the time of registration and changing after the fact can make some participants feel like the rules are changing against them unfairly and cause them to question our reasoning. We have observed other conferences that changed health & safety policies mid-registration with significant consequences.. Our default position is to change policies between events’ registration periods, but not during.
In 2020, with no vaccines approved and clear national guidance and legal mandates, it was clear that both DrupalCon North America and Europe would have to become virtual events. Both were held successfully, and we even had an influx of first time attendees who would not otherwise have been able to attend.
In 2021, although the first vaccines were now available under an emergency use authorization, they would not receive full FDA approval until August of that year. At the same time, the pattern of multiple infection waves and new variants had become apparent, and vaccination rates and hospitalization levels were still very high. Both DrupalCon events would again be virtual in 2021.
In 2022, most national and regional public health recommendations began to allow for in-person events again. After a review of Oregon and Multnomah county public health mandates and metrics, it was decided that a Vaccine-or-daily-test requirement and masking was required. Metrics in Europe improved more rapidly than those in North America, and thus DrupalCon Prague did not require vaccination but did include a mask requirement.
We are monitoring the trends but have not changed our health and safety policy for DrupalCon Pittsburgh.
We are following our default position of maintaining policies in place at registration opening. COVID-19 is still identified as a pandemic, with new cases, hospitalizations, and deaths still occurring.
But monitoring is appropriate, as is evolving. If the recent very positive trends continue, the health numbers for Covid prevalence in Pittsburgh may be very low by June. Consequently, some attendees may be frustrated by these continued safety measures and this may affect compliance at the event. A lack of compliance undermines the health benefits of our health and safety policies.
Thus, community feedback is crucial.
I invite feedback from the Drupal community on this blog post and our health and safety policies for DrupalCon Pittsburgh. How we can create an inviting and welcoming atmosphere for all community members amidst a changing world of health metrics.
If you’re so inclined, please share your thoughts with us.
This month has been the same time window where we have to utilize these decision making criteria to set our policies for DrupalCon Lille.
Therefore, we anticipate that DrupalCon Lille will not be requiring proof of vaccination, daily testing, or masking (though masking is still recommended).
We hope that this retrospective and more detailed explanation of our DrupalCon health and safety policy decision criteria is helpful.
I look forward to gathering with the Drupal community in Pittsburgh, meeting as many people as possible, and hearing your ideas about how we can advance Drupal.
Tim Doyle
CEO
Drupal Association
Ruby 3.2.2 has been released.
This release includes security fixes.
Please check the topics below for details.
See the GitHub releases for further details.
https://cache.ruby-lang.org/pub/ruby/3.2/ruby-3.2.2.tar.gz
SIZE: 20467023
SHA1: 670fce00d83771a1349b116e56a8a3b0ad323769
SHA256: 96c57558871a6748de5bc9f274e93f4b5aad06cd8f37befa0e8d94e7b8a423bc
SHA512: bcc68f3f24c1c8987d9c80b57332e5791f25b935ba38daf5addf60dbfe3a05f9dcaf21909681b88e862c67c6ed103150f73259c6e35c564f13a00f432e3c1e46
https://cache.ruby-lang.org/pub/ruby/3.2/ruby-3.2.2.tar.xz
SIZE: 15118856
SHA1: 087af286b70b0e17f88c9c4469b471eca2010161
SHA256: 4b352d0f7ec384e332e3e44cdbfdcd5ff2d594af3c8296b5636c710975149e23
SHA512: a29f24cd80f563f6368952d06d6273f7241a409fa9ab2f60e03dde2ac58ca06bee1750715b6134caebf4c061d3503446dc37a6059e19860bb0010eef34951935
https://cache.ruby-lang.org/pub/ruby/3.2/ruby-3.2.2.zip
SIZE: 24615317
SHA1: a1b6d57019d41dca269b4b16a80784755d34b81d
SHA256: cc216ecb4f49064d8f44e10ecf9218cfd7b28cf4168bb79ecdf171e321db4af1
SHA512: 569a68d89cc9a646cd0319d7cb8d57df3a55c0ac2c64f1f61607cc9c06b3aa8415eb8d38f7893ab3dbf072da9e919fbc454a9338e924c20a6a5110a1fa301d52
Many committers, developers, and users who provided bug reports helped us make this release.
Thanks for their contributions.
Posted by naruse on 30 Mar 2023