Ubuntu-latest workflows will use Ubuntu-24.04 image

NOTICE: THIS ROLLOT HAS BEEN PUT ON HOLD
Breaking changes
Ubuntu 24.04 is ready to be the default version for the "ubuntu-latest" label in GitHub Actions and Azure DevOps.
Target date
This change will be rolled out over a period of several weeks beginning in September 25th, 2024. We plan to complete the migration by October 30th , 2024.
The motivation for the changes
GitHub Actions and Azure DevOps have supported Ubuntu 24.04 in preview mode since May 2024, and starting from July 2024 Ubuntu 24.04 is generally available for all customers. We have monitored customer feedback to improve the Ubuntu 24.04 image stability and now we are ready to set it as the latest.
Platforms affected

[x]  Azure DevOps
[x]  GitHub Actions

Mitigation ways
Steps or options for impact mitigation
If you see any issues with your workflows during transition period:

Switch back to Ubuntu 22 by changing workflow YAML to use runs-on: ubuntu-22.04 We support two latest LTS Ubuntu versions, so Ubuntu 22 will still be available in near future.
File an issue in this repository

Software Differences
The Ubuntu 22.04 image has a different set of software than Ubuntu 24.04. The most significant changes are listed in the table below:

Tool name
Ubuntu 22.04
Ubuntu 24.04
Notes

Clang
13.* 14.* (default)15.*
16.* 17.* 18.* (default)
The most recent versions are installed

GCC / GNU C++ / GNU Fortran
9.* 10.* 11.* 12.* 13.*
12.* 13.* 14.*
The most recent versions are installed

PHP
8.1.*
8.3.*
The most recent version are installed

Java
8.* 11.* (default)17.* 21.*
8.* 11.* 17.* (default)21.*
Default Java switched to 17.* for Ubuntu 24.04 image.

Python
3.7.* (cached)3.8.* (cached)3.9.* (cached)3.10.* (default)3.11.* (cached)3.12.* (cached)
3.9.* (cached)3.10.* (cached)3.11.* (cached)3.12.* (default)
Pre-cached versions currently unavailable. Default version switched to the latest one. On GitHub Actions, actions/setup-python can install any version on-flight so this change doesn't impact users

Go
1.20.* (cached)1.21.* (default)1.22.* (cached)
1.21.* (cached)1.22.* (cached)1.23.* (default)
If your use-case requires using any of these versions, consider using tasks to install Go on-flight: actions/setup-go (GitHub Actions) Go Tool Installer (Azure DevOps)

PyPy
3.7.* (cached)3.8.* (cached)3.9.* (cached)3.10.* (cached)
3.9.* (cached)3.10.* (cached)
Deprecated all the versions besides the most recent ones

Ruby
3.0.* (default)3.1.* (cached)
3.2.* (default)
We need to update 3.3.5

Node.js
16.* (cached)18.* (default)20.* (cached)
16.* (cached)18.* (cached)20.* (default)
If your use-case requires using any of these versions, consider using tasks to install Node.js on-flight: actions/setup-node (GitHub Actions) Node.js Tool Installer (Azure DevOps) Node 16 will be replaced with Node 22

Heroku
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

Leiningen
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

Mono / MSBuild / NuGet
latest available
-
Software is not available for Ubuntu 24 at the moment.

Terraform
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

R
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

SVN
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

Alibaba Cloud CLI
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

Google Cloud CLI
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

Netlify CLI
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

OpenShift CLI
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

ORAS CLI
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

Vercel CLI
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

Bindgen / Cbindgen
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

Cargo audit/clippy/outdated
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

.NET Core SDK
6.* 7.* 8.*
8.*
Please consider using tasks to install any version on-flight: actions/setup-dotnet (GitHub Actions) Use .NET Core (Azure DevOps)

PostgreSQL
14.*
16.*
More recent version are installed

NVM
0.40.1
setup-node
NVM is replaced with setup-node to manage Node.js versions within CI environments

MS SQL Server Client Tools
sqlcmd / SqlPackage
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

MarkdownPS Module
latest available
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

Android Command Line Tools
9.0
12.0
The most recent version are installed

Android SDK Build-tools
34.0.0 33.0.0 33.0.1 33.0.2 33.0.3 32.0.0 31.0.0
34.0.0
The most recent version are installed

Android NDK
25.* (default)26.*
27.* (default)26.*
The most recent version are installed

Cached Docker images
alpine:3.16alpine:3.17alpine:3.18debian:10debian:11moby/buildkit:latestnode:16node:16-alpinenode:18node:18-alpinenode:20node:20-alpineubuntu:20.04ubuntu:22.04
-
Removed from the Ubuntu 24.04 image due to maintenance reasons.

Nuget not being available is a major showstopper for us. But thanks for the heads up!

@ijunaidm
ubuntu-24.04 is still labeled beta in the overview on https://github.com/actions/runner-images/blob/main/README.md#available-images
Will you now be removing the beta tag?

Yes @MikeMcC399 .

@ThibaultLesuisse are you aware that NuGet refers specifically to NuGet.exe (which requires mono on Mac & Linux), as does Azure Pipeline's NuGetCommand, and GitHub Actions' nuget/setup-nuget action?
If you're building your projects with dotnet build, you're much better off restoring with dotnet restore, and not using NuGet.exe or mono at all.

But we need NuGet.exe to sync our custom Artifacts store. And yes I know that commonly you need to run mono nuget.exe to run it on Mac/Linux. But it doesn't change the fact that a lot of tools are now missing for various reasons. This should be communicated.

We're also affected by the removal of Mono.
The official Mono repo only lists 20.04, but the package seem to work fine in newer versions–which is how the 22.04 image got Mono:
https://github.com/actions/runner-images/blob/ae99c16b0cf27c0cca7ef0b08e7bcf13c33f6cfa/images/ubuntu/scripts/build/install-mono.sh#L15-L18
Is there a reason this can't be done for 24.04 as well? I tested it briefly and it's working for our relatively simple needs.
Mono is fairly chunky so we'd rather not install it every single workflow run.

Hi there - my team is scrambling this morning due to this change. I have detailed the issue on the community forum here, but the tl;dr is that this version bump prevents Python packages from being installed for system Python. Unfortunately, it seeds the evaluation of this issue was incorrect:

On GitHub Actions, actions/setup-python can install any version on-flight so this change doesn't impact users

In fact, my team has a large number of workflows created by many different engineers, and around a dozen of our workflows that didn't previously leverage actions/setup-python now have to go through our internal change management process in order to restore stability to our CI/CD
In the future, please announce breaking changes as a deprecation notice on the GitHub Blog. It's the one place we rely on to proactively catch and prevent stability issues from occurring in our pipelines

This morning, several of our CI pipelines broke due to these changes. It would be great to have compatibility with the following dependencies, allowing us to unpin their versions in the future:
`gcloud`
`sbt`
`libncurses.so.5`

We have had issues today due to the change. We are getting this error message when using ubuntu-latest
 unable to load shared object '/home/runner/work/_temp/Library/ragg/libs/ragg.so':
  libtiff.so.5: cannot open shared object file: No such file or directory

When used the previous version ubuntu-22.04 everything runs without issue. I am unsure of what I need to update in our Action scripts to fix this issue.

I think I'm experiencing the same problem as @sayhiben - without either adding an extra step to a Ruby workflow to install an older Python version or deliberately requesting ubuntu-22.04 to avoid the problem completely, any GitHub Package installer that uses pip to install system-level packages inside the container is going to fail with the following output:
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.

    See /usr/share/doc/python3.12/README.venv for more information.

-Readme.md

What's the timeframe for ubuntu-20.04 deprecation?

I am trying to use arm-runner-action with the base specified at ubuntu-latest.  Sometime in the last two weeks my workflow for arm platform started failing because qemu was not getting configured/built?/whatever correctly for the new ubuntu-latest.  The work around is to specify ubuntu-22.04.  The error using ubuntu-latest with<EMAIL_ADDRESS>is:
...
Setting up g++ (4:10.2.1-1) ...
update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode
Setting up dpkg-dev (1.20.13) ...
Setting up build-essential (12.9) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u10) ...
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)
dpkg: error processing package libc-bin (--configure):
 installed libc-bin package post-installation script subprocess returned error exit status 139
Errors were encountered while processing:
 libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)
Error: Process completed with exit code 100.

Removing gcloud is going to break a bunch of our pipelines, this is a pretty major breaking set of changes to remove all these packages.

Would you please kindly update the README and put the ubuntu-latest YAML label back to 22.04 until the migration is fully over and this PR is closed? We found this the hard way in our workflow when we assumed a version of one of the tools only to realize the underlying host was something else than advertised.

to add something positive:
looking forward to an updated curl version by default

Our pipelines broke this morning because Terraform is no longer included. While I have no issue with it being removed (these are GitHub's images and I'm consciously risking my pipelines breaking by relying on ubuntu-latest instead of pinning) it would be nice to have a little more explanation as to why TF was removed. It's now just in a list of other removed tools with the remark "Maintenance reasons". Can anyone elaborate?

Is there an actual reason as to why nuget cli was removed?

We were suddenly hit by removed terraform too... Any particular reason for it? Is it gonna be a permanent change or will you work on bringing it back?

brainstorm idea: would be nice to have <image type>-beta labels available for use in periodic workflows
I usually leave the images specified as <image type>-latest and accept that my workflows will maybe break without notice, because the changes are usually easy to handle and it keeps my repos current
But since the upcoming releases are just tagged by specific version numbers until the latest tag slides to them, there's no way to have a stable workflow that pre-tests things and finds the breaks before they hit our important pipelines
If there was a stable name I could do matrix expansion on for scheduled checks, it might help folks doing their best to stay current but without unexpected issues
Cheers

This morning several of our CI pipelines broke as well because they access the Linux keyring. It would nice to have the libsecret-1-dev dependency restored in Ubuntu 24 since it was part of the image for previous versions.

Not sure if this is now the place to ask or not but since others are, we were using liblzma
I suppose with the removal of a huge huge pile of packages, all their transitives are gone as well which is why the libraries are gone. Not too hard to install them at least.

Similarly, I think that liblapack3 was lost during the upgrade from 2204 to 2404.

See #10783

Referencing this issue here - #10781 is caused by this.  Documentation should be updated to reflect this breaking change, or the interpreter of python that comes with the runner image should be installed independently from the interpreter that ships with ubuntu so that it is no longer externally managed.
This change WILL break a lot of actions and existing workflows which target the ubuntu-latest label.

Hello! This update has broken my ubuntu end-to-end tests with Playwright + Electron. Need to investigate why. For now I'll pin to runs-on: ubuntu-22.04.

If you're building your projects with dotnet build, you're much better off restoring with dotnet restore, and not using NuGet.exe or mono at all.

And what about nuget pack? It crashes even if I'm using dotnet restore and dotnet build

See https://github.com/actions/runner-images/issues/10788 - the new image fails to include nvm and sbt. (setup-node is not a sufficiently capable replacement for nvm, ftr)

This broke all of our playwright tests. I guess you have to crack a few eggs to make an omelet, but I'm missing some "official" word on what is going on. From what I understand, all ubuntu-latest now run on 24.04, and it is fundamentally broken. Is this being worked on? Pinning everything we have running on non-private runners to 22.04 for now...

From what I understand, all ubuntu-latest now run on 24.04, and it is fundamentally broken.

Unfortunately, that's not true. Some of the ubuntu-latest run on 24.04, others are still 22.04 even though the documentation says something else. I wouldn't say 24.04 is fundamentally broken, it just differs from 22.04 and the communication is far from ideal.

From what I understand, all ubuntu-latest now run on 24.04, and it is fundamentally broken.

Unfortunately, that's not true. Some of the ubuntu-latest run on 24.04, others are still 22.04 even though the documentation says something else. I wouldn't say 24.04 is fundamentally broken, it just differs from 22.04 and the communication is far from ideal.

Yes. On master repo, ubuntu-latest runs on Ubuntu LTS 24.04.1, but on my fork it runs in 22.04.5 (see: https://github.com/NuGet/setup-nuget/issues/168).

The team is actively rolling this back, and we expect it to be done in about an hour. Sorry for the pain this caused in breaking you all. We're going to ensure that we don't break you in unexpected ways, announcements aside.
I'll let the teams share any more pertinent details but wanted to come share an update quickly. ⚡ 🙇

Hey everyone - thank you for your input. Based on community feedback we have decided to rollback the ubuntu-latest migration. All runs on ubuntu-latest will go back to Ubuntu-22 while we work out the issues with the image. We apologize for any service disruption you all may have had, and appreciate everyone’s feedback and patience. The rollback will be completed in the next hour.
To give some context for the changes we made - our images have become very large over the past 2 years and we were trying to free up some space to give us some breathing room going forward. There is currently no extra free space left for installing any more tooling, while still maintaining our free space SLA of 14gb. The size of the image also impacts performance of the VMs as well. Since a new OS is always a cutover, we took the opportunity to free up some space. Clearly this was not the right approach, and we apologize for the pain we have caused.
We will re-evaluate our communication and rollout strategy before beginning this migration again.

One request re communication: currently it seems that to know about upcoming changes like this, you need to subscribe to this repo, but there isn't a way to filter that to only announcements so I'm getting a lot of unrelated messages in my inbox. A better communication channel for image updates would be appreciated.

@geekosaur Its announced in the GitHub Changelog: https://github.blog/changelog/2024-09-25-actions-new-images-and-ubuntu-latest-changes/
It has eg RSS and also has RSS for specific tags, so you can eg. subscribe to all actions tagged changelog items through: https://github.blog/changelog/label/actions/feed/
That will get you all GitHub Actions related announcements and it should have given you this info, but this time it actually didn’t contained enough information, see: https://github.com/actions/runner-images/issues/10788#issuecomment-2416557822

Huge thanks to github for listening to feedback! I'm more than happy to help brainstorm ideas to reduce the image size in a non-breaking way.

Hey everyone - thank you for your input. Based on community feedback we have decided to rollback the ubuntu-latest migration. All runs on ubuntu-latest will go back to Ubuntu-22 while we work out the issues with the image. We apologize for any service disruption you all may have had, and appreciate everyone’s feedback and patience. The rollback will be completed in the next hour.
...

Thank you for the transparency on this issue and a swift resolution @lkfortuna :)

Ironically, my CI worked fine under 24.04, but when the revert occurred I started seeing some weird errors about GLIBCXX versions.
It turns out, the caches were populated under 24.04. If anyone else runs into this, I was able to resolve by clearing the cache for that job. This is perhaps a danger of caching based on the runs-on key, but I don't know if there is an easy way to get the os version from the environment

It's probably better to change all documentation to say using *-latest is strongly discouraged, at least if you're using any tool outside of a very basic set that is guaranteed to always be available (e.g. apt and setup actions). Even then, it's probably better to encourage everyone to just pin it.
Or have something like e.g. ubuntu-22.04-or-later (or just use this "or later" logic on regular ubuntu-22.04) which uses the specified version if available, otherwise automatically use whichever earliest next version is available (not sure if it's already like this) to let everyone pin it with the least trouble.

it seems that to know about upcoming changes like this, you need to subscribe to this repo, but there isn't a way to filter that to only announcements
It has eg RSS and also has RSS for specific tags

RSS is not great for communication... the ideal would be for everyone who has authored any action with ubuntu-* to receive email notifications once a new Ubuntu version is available and production-ready, so they see if it's worth manually migrating it. You could add a setting to the profile to disable that if desired. This notification can be enabled for everyone by default, because it's not like it's gonna happen e.g. every month. It's very infrequent, right?

RSS is not great for communication... the ideal would be for everyone who has authored any action with ubuntu-* to receive email notifications once a new Ubuntu version is available and production-ready, so they see if it's worth manually migrating it

The availability of this release was announced months ago, people should ideally have tested it then and the list of changes in this issue should have been attached or linked to from that announcement.
Automated update notifications for runner versions can be configured in Renovate (and possibly Dependabot, I don’t know)
A new LTS of Ubuntu is released every other year, so that specifically is not a high frequency, and is supported for 5 years
A new ubuntu runner image should probably be in beta like now for 3-6 month and be out of beta for at least another 3-6 months before becoming the default image. That leaves enough room for the community to adapt.

You don't know what you don't know. It's easy to get blindsided. It's not necessarily anyone's fault. I've found it's easier to avoid these types of things by just never relying on latest.

@voxpelli it would be easier to test and have a canary workflow if there were a sliding -beta tag, I use -latest but it is difficult as maintainer in a bunch of repos to go around  manually changing them all to a numbered release tag that will then be obsolete after

Additionally, there's an existing deprecation message vehicle for actions that could be used - the warnings that pop up when you're indirectly using an about-to-be-removed node runtime, for example.

would be easier to test and have a canary workflow if there were a sliding -beta tag

That would be great! Create an issue if there is none! Maybe -next would be even better? Or both? ubuntu-next? And -latest would have been better named -default, -current, -stable or such

the warnings that pop up when you're indirectly using an about-to-be-removed node runtime, for example

Those changes are breaking changes within an existing runner image I believe, not about moving to a new image

If ubuntu-latest were actually "stable" then we wouldn't be here right now. It's correctly named latest, and arguably 22.04 is stable.

If ubuntu-latest were actually "stable" then we wouldn't be here right now. It's correctly named latest, and arguably 22.04 is stable.

Providing different packages or not providing others is not about stability.

If smaller image would mean that my workflows start much faster, I would be fine installing the deps myself, especially if installation is shorter than time saved on starting the job. Unfortunately I have not observed this…
What I liked in gitlab CI was that it allowed you to use any docker image. Which would mean anybody could prepare an image shaved to his needs. But I guess than you would run the trouble of caching those images on the runners…?

Why ubuntu-latest is pointing now to the ubuntu-22.04 version?
A couple of hours before, it was ubuntu-24.04.
https://github.com/actions/runner-images

For one of our workflows, it was the rollback to 22.04 that broke things... :innocent:

I though it was GitHub bugs that rolling -latest back to 22.04, which break some of my workflows that I already upgraded. I should always using specific version instead of -latest from now on.

If the action/workflow is set to a value that doesn't exist, will it fail? Or just wait? I changed ubuntu-latest to ubuntu-24 and... it's queued forever.

@jr0me it should be ubuntu-24.04 i believe.

the agent names are documented here for github actions: https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories
and here for Azure Pipelines: https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#software
Although it doesn't answer the question of what the expected behaviour is when specifying an agent pool that doesn't exist.

More info has been published for Azure Devops - https://learn.microsoft.com/en-us/azure/devops/release-notes/2024/sprint-246-update#azure-pipelines-1 - "later this year"

When will GitHub Larger Runners' ubuntu-latest tag be moved to Ubuntu 24.04?

https://github.blog/changelog/2024-09-25-actions-new-images-and-ubuntu-latest-changes/
it says:
The ubuntu-latest label will migrate to Ubuntu 24 over the course of the next month, beginning September 23rd and finishing on October 30th. During migration, you can determine if your job has migrated by viewing the “Runner Image” information in the “Set up job” step of your Actions logs.
it says october 30, and tody is october 31

https://github.blog/changelog/2024-09-25-actions-new-images-and-ubuntu-latest-changes/
it says:
The ubuntu-latest label will migrate to Ubuntu 24 over the course of the next month, beginning September 23rd and finishing on October 30th. During migration, you can determine if your job has migrated by viewing the “Runner Image” information in the “Set up job” step of your Actions logs.
it says october 30, and today is october 31

See the notice at the beginning of this thread.

Hey everyone, an update here. 👋 We have made changes to the issue body above, and have set a date for re-rollout of the ubuntu-latest migration.
new dates are as follows:

Rollout will begin on December 5th and will complete on January 17th, 2025.

Notable changes to the image is that we have re-installed NVM and gcloud cli. Please see issue body for more details. A changelog is going out today announcing the new dates as well.
I tried to be as transparent with you all in the issue as possible. Thanks for your patience and understanding here.

Thanks for bringing black gcloud! I was seriously planning on putting off updating my pipelines until 2026.

Will .net 9 get added after that comes out later this month? Given that it isn't an LTS release

@lkfortuna Are there any plans for the dotnet guys that are using 24.04? We are feeling a bit left out lately.
Installing dotnet manually does increase build time for every build.
Not having Mono/MsBuild/NuGet is annoying as installing those isn't trivial. SqlPackage would be nice as well.
Are you open to PR to add those or is the decision to not include them final?

List of node versions need an update? Node 16 was already removed for ubuntu-24.04 in https://github.com/actions/runner-images/issues/10677 , right?

There's an issue with the .NET SDK on the new Ub24 images - it's using a much older build of the SDK that has security vulnerabilities.
Ubuntu 22 has .NET 8.0.403 installed, while Ubuntu 24 has .NET 8.0.110. Besides security vulnerabilities, this is causing issues in our build pipeline
Can we have this updated to .NET 8.0.404 (which is the latest build), as well as have .NET 9 installed as well?

@artiomchi is right, this is also a blocker in my opinion to move ubuntu-latest to ubuntu-24.04. #10656 was closed as fixed but it is definitely not!

I'm a bit confused about the choices made for Node.JS here, considering that both Ubuntu and Node bumps once a year, and that node 16 support is long gone now.
Current plan:
Ubuntu 22:
16.* (cached)
18.* (default)
20.* (cached)
Ubuntu 24:
16.* (cached)
18.* (cached)
20.* (default)
Why not have it:
Ubuntu 24:
18.* (cached)
20.* (default)
22.* (cached)

For Leiningen users — consider setup-clojure action.
      - name: Install clojure tools
        uses<EMAIL_ADDRESS>        with:
          lein: latest

@artiomchi @mario-d-s if you have a look at the docs for installing the .NET SDK on Ubunutu 24.04, the table shows that Microsoft is no longer providing any builds for Ubuntu 24.04. This means only Ubunutu's own build of the .NET SDK is available.
For reasons I don't understand, Ubunutu, Redhat, and any other Linux distro that uses the https://github.com/dotnet/dotnet mono-repo only get the .1xx SDKs, never the 200, 300, or 400 builds that Microsoft builds.
Additionally, if you look at the .NET 8 releases page, https://dotnet.microsoft.com/en-us/download/dotnet/8.0, the 8.0.11 runtime came out with 3 SDKS in November, 8.0.404, 8.0.307 and 8.0.111.  In October, the 8.0.10 runtime came out with the 8.0.403, 8.0.306, and 8.0.110 SDKs.
So, the 8.0.110 SDK was current and fully patched as of October's Patch Tuesday, although there is an update since the November Patch Tuesday.  But it's only 1 build old, not a "much older build".

@zivkan you are right that it isn't a very old build per se, and that it is indeed recently patched against security vulnerabilities.
That said, the current Ubuntu 22.04 images have the .2xx, .3xx and .4xx feature bands of .NET8 all available. So, moving to 24.04 by default that does not have those SDKs available is nevertheless a regression.
There is no good reason to exclude those either, it's just that the install script in this repo is currently broken on 24.04. I assume most people on .NET8 move with the latest feature bands by default, so repointing ubuntu-latest to 24.04 will cause increased build times for many affected because the .NET SDK has to be downloaded ad-hoc.

@CrAzYgRl24  what does it mean?

How do I stop getting notifications on this? Having a flag on all of our pipeline builds is very noisy and reduces the value of CICD.  We ALWAYS want to be latest, so just manually switching to 24.04 on the yaml is a bad option.

I didn't see Yarn listed so just want to confirm.
On Ubuntu 22, Yarn 1.22.22 is installed.
Will Yarn stay the same on Ubuntu 24?

I didn't see Yarn listed so just want to confirm.
On Ubuntu 22, Yarn 1.22.22 is installed. Will Yarn stay the same on Ubuntu 24?

@elawad Yarn 1.22.22 is included in the image build: https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2404-Readme.md#package-management

@ijunaidm  Please please please add node 22 to this before you ship it tomorrow, so you have at least 1 node version with security support through the lifetime of this image. Look how many people unanimously agree it's a bad decision to only ship already-dated node versions, in an image that's supposed to last the next 2 years.

It does say "Node 16 will be replaced with Node 22" in the table above. The question is when?

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Can't wait for roll out 😃 . Should this work?
runs-on: ubuntu-latest -> ubuntu-24.04

Is there an expectation that Terraform will eventually be added to this Ubuntu image? If so, what would the timeline look like?

It does say "Node 16 will be replaced with Node 22" in the table above. The question is when?

"Rollout will begin on December 5th and will complete on January 17th, 2025."

Does @ijunaidm speak for @GitHub? If so can you please update your profile?

There are notes at top like:

Node 16 will be replaced with Node 22

And the rollout begins tomorrow.
Does these words mean that the ubuntu-runner will be updated between today and tomorrow to support Node 22? Or that ubuntu-runner is being released tomorrow and that another change will be made later to support Node 22?
Same questions for the other mentions of future work in the top post.

@ThibaultLesuisse can you not juse a specific version of Ubuntu instead of @latest?

Hi!
Is this affecting Ubuntu LArge runners, too? For some hours our Actions are not receiving any ubuntu-larger runner.

Why only .Net SDK 8.0 as the latest? We are a month into the latest release and unable to use this on the Ubuntu image for .net 9.

@MrMTaylor , same with Node, were 7 months into 22, and it's not clear yet to what extend it's being supported.

Rollout will begin on December 5th and will complete on January 17th, 2025.
Breaking changes Ubuntu 24.04 is ready to be the default version for the "ubuntu-latest" label in GitHub Actions and Azure DevOps.
Target date This change will be rolled out over a period of several weeks beginning December 5th and will complete on January 17th, 2025.
The motivation for the changes GitHub Actions and Azure DevOps have supported Ubuntu 24.04 in preview mode since May 2024, and starting from July 2024 Ubuntu 24.04 is generally available for all customers. We have monitored customer feedback to improve the Ubuntu 24.04 image stability and now we are ready to set it as the latest. There are a set of packages listed below that we have removed from the Ubuntu 24 image. Please review the list carefully to see if you will be impacted by these changes. We have made cuts to the list of packages so that we can maintain our SLA for free disk space. The images have grown so large we are in danger of violating our SLA if we keep the package list as-is.
The factors we took into consideration when removing packages are as follows:

How long does it take to install the tool at runtime?
How much space does it take up on the image?
How many users are there of the tool?

We understand that our reasoning may not make sense to some of you out there, but please bear in mind that we tried to keep disruptions as minimal as possible, and tried to keep the best interests of the community at large in mind. There is a very large and diverse community using our images, and as much as we would like to, we cannot pre-install every tool on these images.
Platforms affected

[x]   Azure DevOps
[x]   GitHub Actions

Mitigation ways Steps or options for impact mitigation If you see any issues with your workflows during transition period:

Switch back to Ubuntu 22 by changing workflow YAML to use runs-on: ubuntu-22.04 We support two latest LTS Ubuntu versions, so Ubuntu 22 will still be maintained for the next 2 years.
File an issue in this repository

Software Differences The Ubuntu 22.04 image has a different set of software than Ubuntu 24.04. The most significant changes are listed in the table below:
Tool name	Ubuntu 22.04	Ubuntu 24.04	Notes
Clang

13.*

14.* (default)

15.*

16.*

17.*

18.* (default)

The most recent versions are installed
GCC / GNU C++ / GNU Fortran

9.*

10.*

11.*

12.*

13.*

12.*

13.*

14.*

The most recent versions are installed
PHP	8.1.*	8.3.*	The most recent version are installed
Java

8.*

11.* (default)

17.*

21.*

8.*

11.*

17.* (default)

21.*

Default Java switched to 17.* for Ubuntu 24.04 image.
Python

3.7.* (cached)

3.8.* (cached)

3.9.* (cached)

3.10.* (default)

3.11.* (cached)

3.12.* (cached)

3.9.* (cached)

3.10.* (cached)

3.11.* (cached)

3.12.* (default)

Pre-cached versions currently unavailable. Default version switched to the latest one. On GitHub Actions, actions/setup-python can install any version on-flight so this change doesn't impact users
Go

1.20.* (cached)

1.21.* (default)

1.22.* (cached)

1.21.* (cached)

1.22.* (cached)

1.23.* (default)

If your use-case requires using any of these versions, consider using tasks to install Go on-flight:

actions/setup-go (GitHub Actions)
Go Tool Installer (Azure DevOps)

PyPy

3.7.* (cached)

3.8.* (cached)

3.9.* (cached)

3.10.* (cached)

3.9.* (cached)

3.10.* (cached)

Deprecated all the versions besides the most recent ones
Ruby

3.0.* (default)

3.1.* (cached)

3.2.* (default)

We need to update 3.3.5
Node.js

16.* (cached)

18.* (default)

20.* (cached)

16.* (cached)

18.* (cached)

20.* (default)

If your use-case requires using any of these versions, consider using tasks to install Node.js on-flight:

actions/setup-node (GitHub Actions)
Node.js Tool Installer (Azure DevOps)
Node 16 will be replaced with Node 22

Heroku	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Leiningen	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Mono / MSBuild / NuGet	latest available	-	Software is not available for Ubuntu 24 at the moment.
Terraform	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
R	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
SVN	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Alibaba Cloud CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Netlify CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
OpenShift CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
ORAS CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Vercel CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Bindgen / Cbindgen	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Cargo audit/clippy/outdated	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
.NET Core SDK

6.*

7.*

8.*

8.*

Please consider using tasks to install any version on-flight:

actions/setup-dotnet (GitHub Actions)
Use .NET Core (Azure DevOps)

PostgreSQL	14.*	16.*	More recent version are installed
MS SQL Server Client Tools	sqlcmd / SqlPackage	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
MarkdownPS Module	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Android Command Line Tools	9.0	12.0	The most recent version are installed
Android SDK Build-tools

34.0.0

33.0.0

33.0.1

33.0.2

33.0.3

32.0.0

31.0.0

34.0.0

The most recent version are installed
Android NDK

25.* (default)

26.*

27.* (default)

26.*

The most recent version are installed
Cached Docker images

alpine:3.16
alpine:3.17
alpine:3.18
debian:10
debian:11
moby/buildkit:latest
node:16
node:16-alpine
node:18
node:18-alpine
node:20
node:20-alpine
ubuntu:20.04
ubuntu:22.04

Removed from the Ubuntu 24.04 image due to maintenance reasons.

Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package gtk4
Error: Process completed with exit code 100.

I presume GTK4 no longer being available is related to this although all the references above still are to 22.04.  Not sure how to proceed.

K

David-Allen-Arteaga#11https://github.com/actions/runner-images/issues/10636#topDa #11135

We're also affected by the removal of Mono.
The official Mono repo only lists 20.04, but the package seem to work fine in newer versions–which is how the 22.04 image got Mono:
https://github.com/actions/runner-images/blob/ae99c16b0cf27c0cca7ef0b08e7bcf13c33f6cfa/images/ubuntu/scripts/build/install-mono.sh#L15-L18
Is there a reason this can't be done for 24.04 as well? I tested it briefly and it's working for our relatively simple needs.
Mono is fairly chunky so we'd rather not install it every single workflow run.

B

jquery.creditCardValidator.coffee (1).txt
ValidMYCard-Credit-Card-Generator-Validiator-master (2).zip

Rollout will begin on December 5th and will complete on January 17th, 2025.
Breaking changes Ubuntu 24.04 is ready to be the default version for the "ubuntu-latest" label in GitHub Actions and Azure DevOps.
Target date This change will be rolled out over a period of several weeks beginning December 5th and will complete on January 17th, 2025.
The motivation for the changes GitHub Actions and Azure DevOps have supported Ubuntu 24.04 in preview mode since May 2024, and starting from July 2024 Ubuntu 24.04 is generally available for all customers. We have monitored customer feedback to improve the Ubuntu 24.04 image stability and now we are ready to set it as the latest. There are a set of packages listed below that we have removed from the Ubuntu 24 image. Please review the list carefully to see if you will be impacted by these changes. We have made cuts to the list of packages so that we can maintain our SLA for free disk space. The images have grown so large we are in danger of violating our SLA if we keep the package list as-is.
The factors we took into consideration when removing packages are as follows:

How long does it take to install the tool at runtime?
How much space does it take up on the image?
How many users are there of the tool?

We understand that our reasoning may not make sense to some of you out there, but please bear in mind that we tried to keep disruptions as minimal as possible, and tried to keep the best interests of the community at large in mind. There is a very large and diverse community using our images, and as much as we would like to, we cannot pre-install every tool on these images.
Platforms affected

[x]   Azure DevOps
[x]   GitHub Actions

Mitigation ways Steps or options for impact mitigation If you see any issues with your workflows during transition period:

Switch back to Ubuntu 22 by changing workflow YAML to use runs-on: ubuntu-22.04 We support two latest LTS Ubuntu versions, so Ubuntu 22 will still be maintained for the next 2 years.
File an issue in this repository

Software Differences The Ubuntu 22.04 image has a different set of software than Ubuntu 24.04. The most significant changes are listed in the table below:
Tool name	Ubuntu 22.04	Ubuntu 24.04	Notes
Clang

13.*

14.* (default)

15.*

16.*

17.*

18.* (default)

The most recent versions are installed
GCC / GNU C++ / GNU Fortran

9.*

10.*

11.*

12.*

13.*

12.*

13.*

14.*

The most recent versions are installed
PHP	8.1.*	8.3.*	The most recent version are installed
Java

8.*

11.* (default)

17.*

21.*

8.*

11.*

17.* (default)

21.*

Default Java switched to 17.* for Ubuntu 24.04 image.
Python

3.7.* (cached)

3.8.* (cached)

3.9.* (cached)

3.10.* (default)

3.11.* (cached)

3.12.* (cached)

3.9.* (cached)

3.10.* (cached)

3.11.* (cached)

3.12.* (default)

Pre-cached versions currently unavailable. Default version switched to the latest one. On GitHub Actions, actions/setup-python can install any version on-flight so this change doesn't impact users
Go

1.20.* (cached)

1.21.* (default)

1.22.* (cached)

1.21.* (cached)

1.22.* (cached)

1.23.* (default)

If your use-case requires using any of these versions, consider using tasks to install Go on-flight:

actions/setup-go (GitHub Actions)
Go Tool Installer (Azure DevOps)

PyPy

3.7.* (cached)

3.8.* (cached)

3.9.* (cached)

3.10.* (cached)

3.9.* (cached)

3.10.* (cached)

Deprecated all the versions besides the most recent ones
Ruby

3.0.* (default)

3.1.* (cached)

3.2.* (default)

We need to update 3.3.5
Node.js

16.* (cached)

18.* (default)

20.* (cached)

16.* (cached)

18.* (cached)

20.* (default)

If your use-case requires using any of these versions, consider using tasks to install Node.js on-flight:

actions/setup-node (GitHub Actions)
Node.js Tool Installer (Azure DevOps)
Node 16 will be replaced with Node 22

Heroku	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Leiningen	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Mono / MSBuild / NuGet	latest available	-	Software is not available for Ubuntu 24 at the moment.
Terraform	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
R	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
SVN	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Alibaba Cloud CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Netlify CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
OpenShift CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
ORAS CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Vercel CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Bindgen / Cbindgen	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Cargo audit/clippy/outdated	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
.NET Core SDK

6.*

7.*

8.*

8.*

Please consider using tasks to install any version on-flight:

actions/setup-dotnet (GitHub Actions)
Use .NET Core (Azure DevOps)

PostgreSQL	14.*	16.*	More recent version are installed
MS SQL Server Client Tools	sqlcmd / SqlPackage	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
MarkdownPS Module	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Android Command Line Tools	9.0	12.0	The most recent version are installed
Android SDK Build-tools

34.0.0

33.0.0

33.0.1

33.0.2

33.0.3

32.0.0

31.0.0

34.0.0

The most recent version are installed
Android NDK

25.* (default)

26.*

27.* (default)

26.*

The most recent version are installed
Cached Docker images

alpine:3.16
alpine:3.17
alpine:3.18
debian:10
debian:11
moby/buildkit:latest
node:16
node:16-alpine
node:18
node:18-alpine
node:20
node:20-alpine
ubuntu:20.04
ubuntu:22.04

Removed from the Ubuntu 24.04 image due to maintenance reasons.

https://gitkraken.dev/connect?source=gitlens&provider=github,gitlab,jira&token=2q4oNe1xgue0N6nNCPWbSUIoATG

If I've specified ubuntu-latest, is there a way to print out or check the actual image used?
I'm fine with updating to 24.04 as needed, I just want to know it's working for my CI.

You can just specfify ubuntu-24.04 then?

If I've specified ubuntu-latest, is there a way to print out or check the actual image used?
I'm fine with updating to 24.04 as needed, I just want to know it's working for my CI.

You can just specify ubuntu-24.04 then?

Well, yes. I suppose it's an odd question lol.

If I've specified ubuntu-latest, is there a way to print out or check the actual image used?

If you mean in run it self, at the start of the job is Set up job step where it's defined. If you need it before I think there is no way to check which will be used in this transition period

I'm sorry for asking this here, but I'm not sure where else to ask...
How can I build one of the images to experiment with it? Or is there prebuilt .iso files that I can download?

How can I build one of the images to experiment with it?

@Parad0x84 : You don't build those, you use them – see "GitHub Docs: GitHub Actions/GitHub-hosted runners/About GitHub-hosted runners"

You don't build those, you use them

@m-ueberall I know, but I wanna experiment with them locally. Instead of uploading to github 50 times and waiting for 30 mins compilation each time, I wanna perfect my setup locally and then upload to github and validate my setup

Look into https://github.com/nektos/act

Cached Docker images
- 	Removed from the Ubuntu 24.04 image due to maintenance reasons.

Do Actions still support Docker? What is the effect of the removal of the cached Docker images?

#11131

TWEAKING 🎼BEATS#TRIXMIXING1AI ❤

TWEAKING 🎼BEATS#TRIXMIXING1AI ❤

TWEAKING 🎼BEATS#TRIXMIXING1AI ❤

TWEAKING 🎼BEATS

We hebben vandaag problemen gehad door de verandering. We krijgen deze foutmelding bij het gebruik vanubuntu-latest
 unable to load shared object '/home/runner/work/_temp/Library/rang/libs/ragg.so':
  libtiff.so.5: cannot open shared object file: No such file or directory

Bij gebruik van de vorige versie ubuntu-22.04 draait alles zonder problemen. Ik weet niet zeker wat ik moet updaten in onze Action scripts om dit probleem op te lossen.

De uitrol start op 5 december en zal op 17 januari 2025 voltooid zijn.
Belangrijke wijzigingen Ubuntu 24.04 is klaar om de standaardversie te worden voor het label 'ubuntu-latest' in GitHub Actions en Azure DevOps.
Streefdatum Deze wijziging wordt over een periode van enkele weken doorgevoerd, te beginnen op 5 december en zal op 17 januari 2025 voltooid zijn.
De motivatie voor de wijzigingen GitHub Actions en Azure DevOps ondersteunen Ubuntu 24.04 in preview-modus sinds mei 2024 en vanaf juli 2024 is Ubuntu 24.04 algemeen beschikbaar voor alle klanten. We hebben feedback van klanten gemonitord om de stabiliteit van de Ubuntu 24.04-image te verbeteren en nu zijn we klaar om deze als de nieuwste in te stellen. Hieronder staan een aantal pakketten die we uit de Ubuntu Sommige hebben verwijderd. Bekijk de lijst zorgvuldig om te zien of deze wijzigingen gevolgen voor u hebben. We hebben de lijst met pakketten ingekort, zodat we onze SLA voor gratis schijfruimte kunnen behouden. De images zijn zo groot geworden dat we het risico lopen onze SLA te schenden als we de pakketlijst ongewijzigd laten.
Bij het verwijderen van pakketten hebben wij rekening gehouden met de volgende factoren:

Hoe lang duurt het om de tool tijdens runtime te installeren?
Hoeveel ruimte neemt het in beslag op de afbeelding?
Hoeveel gebruikers hebben de tool?

We begrijpen dat onze redenering voor sommigen van jullie misschien niet logisch is, maar houd er rekening mee dat we hebben geprobeerd om verstoringen zo minimaal mogelijk te houden en de beste belangen van de community in het algemeen in gedachten te houden.
Betrokken platforms

[x]   Azure DevOps
[x]   GitHub-acties

Manieren om de impact te beperken Stappen of opties voor impact beperking Als u problemen ondervindt met uw workflows tijdens de overgangsperiode:

Schakel terug naar Ubuntu 22 door de workflow Yale te wijzigen. runs-on: ubuntu-22.04We ondersteunen de twee nieuwste LTS Ubuntu-versies, dus Ubuntu 22 wordt de komende 2 jaar nog steeds onderhouden.
Dien een probleem in deze repository in

Software en verschillen De Ubuntu 22.04-image heeft een andere set software dan Ubuntu 24.04. De belangrijkste wijzigingen staan in de onderstaande tabel:
Gereedschapskist	Ubuntu 22.04	Ubuntu 24.04	Notities
Klang

13.*

14.* (standaard)

15.*

16.*

17.*

18.* (standaard)

De meest recente versies zijn geïnstalleerd
GCC / GNU C++ / GNU Fortran

9.*

10.*

11.*

12.*

13.*

12.*

13.*

14.*

De meest recente versies zijn geïnstalleerd
PHP	8.1.*	8.3.*	The most recent version are installed
Java

8.*

11.* (default)

17.*

21.*

8.*

11.*

17.* (default)

21.*

Default Java switched to 17.* for Ubuntu 24.04 image.
Python

3.7.* (cached)

3.8.* (cached)

3.9.* (cached)

3.10.* (default)

3.11.* (cached)

3.12.* (cached)

3.9.* (cached)

3.10.* (cached)

3.11.* (cached)

3.12.* (default)

Pre-cached versions currently unavailable. Default version switched to the latest one. On GitHub Actions, actions/setup-python can install any version on-flight so this change doesn't impact users
Go

1.20.* (cached)

1.21.* (default)

1.22.* (cached)

1.21.* (cached)

1.22.* (cached)

1.23.* (default)

If your use-case requires using any of these versions, consider using tasks to install Go on-flight:

actions/setup-go (GitHub Actions)
Go Tool Installer (Azure DevOps)

Piept

3.7.* (cached)

3.8.* (cached)

3.9.* (cached)

3.10.* (cached)

3.9.* (cached)

3.10.* (cached)

Dedicated all the versions besides the most recent ones
Ruby

3.0.* (default)

3.1.* (cached)

3.2.* (default)

We need to update 3.3.5
Node.js

16.* (cached)

18.* (default)

20.* (cached)

16.* (cached)

18.* (cached)

20.* (default)

If your use-case requires using any of these versions, consider using tasks to install Node.js on-flight:

actions/setup-node (GitHub Actions)
Node.js Tool Installer (Azure DevOps)
Node 16 will be replaced with Node 22

Hero	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Leiningen	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Mono / Build / Negen	latest available	-	Software is not available for Ubuntu 24 at the moment.
Terrarium	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
R	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
SVN	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Alibaba Cloud CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Netflix CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Op shift CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
ORAS CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Vercel CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Binden / Bindingen	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Cargo audit/cliënt/outdated	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
.NET Core SDK

6.*

7.*

8.*

8.*

Please consider using tasks to install any version on-flight:

actions/studenten (GitHub Actions)
Use .NET Core (Azure DevOps)

PostgreSQL	14.*	16.*	More recent version are installed
MS SQL Server Client Tools	sal cmd / Sal package	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Markering Module	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Android Command Line Tools	9.0	12.0	The most recent version are installed
Android SDK Build-tools

34.0.0

33.0.0

33.0.1

33.0.2

33.0.3

32.0.0

31.0.0

34.0.0

The most recent version are installed
Android Nd

25.* (default)

26.*

27.* (default)

26.*

The most recent version are installed
Cached Docker images

alpine:3.16
alpine:3.17
alpine:3.18
debian:10
debian:11
moby/build kit:latest
node:16
node:Helpende
node:18
node:Alpine
node:20
node:20-alpine
ubuntu:20.04
ubuntu:22.04

Removed from the Ubuntu 24.04 image due to maintenance reasons.

@ThibaultLesuisse are you aware that NuGet refers specifically to NuGet.exe (which requires mono on Mac & Linux), as does Azure Pipeline's NuGetCommand, and GitHub Actions' nuget/setup-nuget action?

Nuget.exe and the Nuget for dotnet restore are not the same and not guaranteed compatible, especially when it comes to mixed PackageRef and non-PackageRef solutions. (example)

Hmm my CI seems to be failing now due to 24.04.
We're building .NET.
8.0.11 SDK is installed:
https://github.com/open-telemetry/opentelemetry-dotnet/actions/runs/12347120203/job/34486836823?pr=6032#step:3:15
Yet when executing tests it reports not available: https://github.com/open-telemetry/opentelemetry-dotnet/actions/runs/12347120203/job/34486836823?pr=6032#step:6:366
Is it this? https://github.com/actions/runner-images/pull/11007

We're also affected by the removal of Mono.
The official Mono repo only lists 20.04, but the package seem to work fine in newer versions–which is how the 22.04 image got Mono:

Perhaps they don't want to support a piece of si^Moftware that their own maintainers don't keep updated?
<...>

Mono is fairly chunky so we'd rather not install it every single workflow run.

For this and most other issues I see listed above, using a container image to run your workflow will make a lot of sense. You basically control most aspects of the environment in this way.

sbt was not available today in ubuntu-latest, it seems: https://github.com/polyvariant/better-tostring/actions/runs/12353445866
and yet, it's not on the list of removed tools. Is that intentional?

In case this helps anyone, it looks like kcov is not available in Ubuntu 24.04 (it was removed from upstream Debian, and then added back -- so it may come back in Ubuntu 25).  For now, though, tests using it will break.

Please make future breaking changes opt-in until a certain cut-off date when they become opt-out instead of this

good

good

We are experiencing all kind of issues in very unexpected ways. For example these apt commands fail with the new runners:
sudo add-apt-repository ppa:rmescandon/yq
sudo apt update
sudo apt install yq -y

As well as openssl and a bunch of other features
Would have been nice to get more warnings on what commands will break. For me at least, it's very hard looking at this list and looking at the code of an action, and understanding if it breaks or not. I would not be expecting apt or openssl to break even after reading this post 🙇
I expect a lot of open source actions will fail in the following days... 🙇

Plesse send my wallet address

Why was Vercel CLI removed from the Ubuntu 24.04 image, and could it be re-included?
Summary
With the Ubuntu 24.04 rollout, I noticed that the Vercel CLI is no longer pre-installed on the GitHub Actions/Azure DevOps runner image. It was previously included (or at least available without manual installation) on Ubuntu 20.04/22.04.
Questions

Why was the Vercel CLI removed?
I understand that some tools are removed to reduce image size, but I'd like to know if there's a specific usage metric or reason behind removing Vercel.
Is there a possibility of re-including it?
If there's enough demand from the community, could the Vercel CLI be brought back in a future update?

Use Case

Many teams deploy to Vercel from GitHub Actions.
Installing Vercel CLI manually (npm i -g vercel) adds extra steps/time to CI/CD pipelines.

Potential Solutions

Add Vercel CLI back if it meets the usage criteria.
Provide an official recommendation (or setup action) for easily installing Vercel CLI if re-inclusion isn’t feasible.

Thank you for your time!

The removal of NuGet is causing issues for some of my projects. We use vcpkg to manage C++ dependencies, and rely on its NuGet support to publish those dependencies to GitHub Package Registry to that they are available for subsequent builds (we can't rely on GitHub Actions caching because the 7 day eviction policy is way too short for us).
vcpkg fetch nuget and the NuGet/setup-nuget action both fail to give me a working copy of NuGet on Ubuntu 24.04.
Is there a supported way to get NuGet working on the newer runners?

[ düğüm:22 ]

tags:

'v[0-9]+.[0-9]+'
'v[0-9]+.[0-9]+.[0-9]+'

hi

Sounds about right.

Is there any way to hide this warning:

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

yes, we realise this is the case: not sure we need 4 warnings every time our GitHub Actions workflows run 😅
Thanks! ❤

remove form me

there's apparently a extraheader orphan somewhere in this .yml?

But all job checks passed.

Glad it was merged.

Rollout will begin on December 5th and will complete on January 17th, 2025.
Breaking changes Ubuntu 24.04 is ready to be the default version for the "ubuntu-latest" label in GitHub Actions and Azure DevOps.
Target date This change will be rolled out over a period of several weeks beginning December 5th and will complete on January 17th, 2025.
The motivation for the changes GitHub Actions and Azure DevOps have supported Ubuntu 24.04 in preview mode since May 2024, and starting from July 2024 Ubuntu 24.04 is generally available for all customers. We have monitored customer feedback to improve the Ubuntu 24.04 image stability and now we are ready to set it as the latest. There are a set of packages listed below that we have removed from the Ubuntu 24 image. Please review the list carefully to see if you will be impacted by these changes. We have made cuts to the list of packages so that we can maintain our SLA for free disk space. The images have grown so large we are in danger of violating our SLA if we keep the package list as-is.
The factors we took into consideration when removing packages are as follows:

How long does it take to install the tool at runtime?
How much space does it take up on the image?
How many users are there of the tool?

We understand that our reasoning may not make sense to some of you out there, but please bear in mind that we tried to keep disruptions as minimal as possible, and tried to keep the best interests of the community at large in mind. There is a very large and diverse community using our images, and as much as we would like to, we cannot pre-install every tool on these images.
Platforms affected

[x]   Azure DevOps
[x]   GitHub Actions

Mitigation ways Steps or options for impact mitigation If you see any issues with your workflows during transition period:

Switch back to Ubuntu 22 by changing workflow YAML to use runs-on: ubuntu-22.04 We support two latest LTS Ubuntu versions, so Ubuntu 22 will still be maintained for the next 2 years.
File an issue in this repository

Software Differences The Ubuntu 22.04 image has a different set of software than Ubuntu 24.04. The most significant changes are listed in the table below:
Tool name	Ubuntu 22.04	Ubuntu 24.04	Notes
Clang

13.*

14.* (default)

15.*

16.*

17.*

18.* (default)

The most recent versions are installed
GCC / GNU C++ / GNU Fortran

9.*

10.*

11.*

12.*

13.*

12.*

13.*

14.*

The most recent versions are installed
PHP	8.1.*	8.3.*	The most recent version are installed
Java

8.*

11.* (default)

17.*

21.*

8.*

11.*

17.* (default)

21.*

Default Java switched to 17.* for Ubuntu 24.04 image.
Python

3.7.* (cached)

3.8.* (cached)

3.9.* (cached)

3.10.* (default)

3.11.* (cached)

3.12.* (cached)

3.9.* (cached)

3.10.* (cached)

3.11.* (cached)

3.12.* (default)

Pre-cached versions currently unavailable. Default version switched to the latest one. On GitHub Actions, actions/setup-python can install any version on-flight so this change doesn't impact users
Go

1.20.* (cached)

1.21.* (default)

1.22.* (cached)

1.21.* (cached)

1.22.* (cached)

1.23.* (default)

If your use-case requires using any of these versions, consider using tasks to install Go on-flight:

actions/setup-go (GitHub Actions)
Go Tool Installer (Azure DevOps)

PyPy

3.7.* (cached)

3.8.* (cached)

3.9.* (cached)

3.10.* (cached)

3.9.* (cached)

3.10.* (cached)

Deprecated all the versions besides the most recent ones
Ruby

3.0.* (default)

3.1.* (cached)

3.2.* (default)

We need to update 3.3.5
Node.js

16.* (cached)

18.* (default)

20.* (cached)

16.* (cached)

18.* (cached)

20.* (default)

If your use-case requires using any of these versions, consider using tasks to install Node.js on-flight:

actions/setup-node (GitHub Actions)
Node.js Tool Installer (Azure DevOps)
Node 16 will be replaced with Node 22

Heroku	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Leiningen	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Mono / MSBuild / NuGet	latest available	-	Software is not available for Ubuntu 24 at the moment.
Terraform	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
R	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
SVN	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Alibaba Cloud CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Netlify CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
OpenShift CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
ORAS CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Vercel CLI	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Bindgen / Cbindgen	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Cargo audit/clippy/outdated	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
.NET Core SDK

6.*

7.*

8.*

8.*

Please consider using tasks to install any version on-flight:

actions/setup-dotnet (GitHub Actions)
Use .NET Core (Azure DevOps)

PostgreSQL	14.*	16.*	More recent version are installed
MS SQL Server Client Tools	sqlcmd / SqlPackage	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
MarkdownPS Module	latest available	-	Removed from the Ubuntu 24.04 image due to maintenance reasons.
Android Command Line Tools	9.0	12.0	The most recent version are installed
Android SDK Build-tools

34.0.0

33.0.0

33.0.1

33.0.2

33.0.3

32.0.0

31.0.0

34.0.0

The most recent version are installed
Android NDK

25.* (default)

26.*

27.* (default)

26.*

The most recent version are installed
Cached Docker images

alpine:3.16
alpine:3.17
alpine:3.18
debian:10
debian:11
moby/buildkit:latest
node:16
node:16-alpine
node:18
node:18-alpine
node:20
node:20-alpine
ubuntu:20.04
ubuntu:22.04

Removed from the Ubuntu 24.04 image due to maintenance reasons.

شكرا اهتمامكم لنا
في الثلاثاء، ٣١ ديسمبر ٢٠٢٤ ٦:٢٦ م shahedy2276541 @.***>
كتب:

Rollout will begin on December 5th and will complete on January 17th, 2025.
Breaking changes Ubuntu 24.04 is ready to be the default version for
the "ubuntu-latest" label in GitHub Actions and Azure DevOps.
Target date This change will be rolled out over a period of several
weeks beginning December 5th and will complete on January 17th, 2025.
The motivation for the changes GitHub Actions and Azure DevOps have
supported Ubuntu 24.04 in preview mode since May 2024, and starting from
July 2024 Ubuntu 24.04 is generally available for all customers. We have
monitored customer feedback to improve the Ubuntu 24.04 image stability and
now we are ready to set it as the latest. There are a set of packages
listed below that we have removed from the Ubuntu 24 image. Please review
the list carefully to see if you will be impacted by these changes. We have
made cuts to the list of packages so that we can maintain our SLA for free
disk space. The images have grown so large we are in danger of violating
our SLA if we keep the package list as-is.
The factors we took into consideration when removing packages are as
follows:

How long does it take to install the tool at runtime?
How much space does it take up on the image?
How many users are there of the tool?

We understand that our reasoning may not make sense to some of you out
there, but please bear in mind that we tried to keep disruptions as minimal
as possible, and tried to keep the best interests of the community at large
in mind. There is a very large and diverse community using our images, and
as much as we would like to, we cannot pre-install every tool on these
images.
Platforms affected

Azure DevOps
GitHub Actions

Mitigation ways Steps or options for impact mitigation If you see any
issues with your workflows during transition period:

Switch back to Ubuntu 22 by changing workflow YAML to use runs-on:
ubuntu-22.04 We support two latest LTS Ubuntu versions, so Ubuntu 22
will still be maintained for the next 2 years.
File an issue in this repository

Software Differences The Ubuntu 22.04 image has a different set of
software than Ubuntu 24.04. The most significant changes are listed in the
table below:
Tool name Ubuntu 22.04 Ubuntu 24.04 Notes
Clang

13.*
14.* (default)
15.*
16.*
17.*
18.* (default)
The most recent versions are installed
GCC / GNU C++ / GNU Fortran

9.*
10.*
11.*
12.*
13.*
12.*
13.*
14.*
The most recent versions are installed
PHP 8.1.* 8.3.* The most recent version are installed
Java

8.*
11.* (default)
17.*
21.*
8.*
11.*
17.* (default)
21.*
Default Java switched to 17.* for Ubuntu 24.04 image.
Python

3.7.* (cached)
3.8.* (cached)
3.9.* (cached)
3.10.* (default)
3.11.* (cached)
3.12.* (cached)
3.9.* (cached)
3.10.* (cached)
3.11.* (cached)
3.12.* (default)
Pre-cached versions currently unavailable. Default version switched to the
latest one. On GitHub Actions, actions/setup-python
https://github.com/actions/setup-python can install any version
on-flight so this change doesn't impact users
Go

1.20.* (cached)
1.21.* (default)
1.22.* (cached)
1.21.* (cached)
1.22.* (cached)
1.23.* (default)
If your use-case requires using any of these versions, consider using
tasks to install Go on-flight:

actions/setup-go https://github.com/actions/setup-go (GitHub
Actions)
Go Tool Installer
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/go-tool?view=azure-devops
(Azure DevOps)

PyPy

3.7.* (cached)
3.8.* (cached)
3.9.* (cached)
3.10.* (cached)
3.9.* (cached)
3.10.* (cached)
Deprecated all the versions besides the most recent ones
Ruby

3.0.* (default)
3.1.* (cached)
3.2.* (default)
We need to update 3.3.5
Node.js

16.* (cached)
18.* (default)
20.* (cached)
16.* (cached)
18.* (cached)
20.* (default)
If your use-case requires using any of these versions, consider using
tasks to install Node.js on-flight:

actions/setup-node https://github.com/actions/setup-node (GitHub
Actions)
Node.js Tool Installer
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/node-js?view=azure-devops
(Azure DevOps)
Node 16 will be replaced with Node 22

Heroku latest available - Removed from the Ubuntu 24.04 image due to
maintenance reasons.
Leiningen latest available - Removed from the Ubuntu 24.04 image due to
maintenance reasons.
Mono / MSBuild / NuGet latest available - Software is not available for
Ubuntu 24 at the moment.
Terraform latest available - Removed from the Ubuntu 24.04 image due to
maintenance reasons.
R latest available - Removed from the Ubuntu 24.04 image due to
maintenance reasons.
SVN latest available - Removed from the Ubuntu 24.04 image due to
maintenance reasons.
Alibaba Cloud CLI latest available - Removed from the Ubuntu 24.04 image
due to maintenance reasons.
Netlify CLI latest available - Removed from the Ubuntu 24.04 image due to
maintenance reasons.
OpenShift CLI latest available - Removed from the Ubuntu 24.04 image due
to maintenance reasons.
ORAS CLI latest available - Removed from the Ubuntu 24.04 image due to
maintenance reasons.
Vercel CLI latest available - Removed from the Ubuntu 24.04 image due to
maintenance reasons.
Bindgen / Cbindgen latest available - Removed from the Ubuntu 24.04 image
due to maintenance reasons.
Cargo audit/clippy/outdated latest available - Removed from the Ubuntu
24.04 image due to maintenance reasons.
.NET Core SDK

6.*
7.*
8.*
8.*
Please consider using tasks to install any version on-flight:

actions/setup-dotnet https://github.com/actions/setup-dotnet
(GitHub Actions)
Use .NET Core
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/dotnet-core-tool-installer?view=azure-devops
(Azure DevOps)

PostgreSQL 14.* 16.* More recent version are installed
MS SQL Server Client Tools sqlcmd / SqlPackage - Removed from the Ubuntu
24.04 image due to maintenance reasons.
MarkdownPS Module latest available - Removed from the Ubuntu 24.04 image
due to maintenance reasons.
Android Command Line Tools 9.0 12.0 The most recent version are installed
Android SDK Build-tools

34.0.0
33.0.0
33.0.1
33.0.2
33.0.3
32.0.0
31.0.0
34.0.0
The most recent version are installed
Android NDK

25.* (default)
26.*
27.* (default)
26.*
The most recent version are installed
Cached Docker images

alpine:3.16

alpine:3.17

alpine:3.18

debian:10

debian:11

moby/buildkit:latest

node:16

node:16-alpine

node:18

node:18-alpine

node:20

node:20-alpine

ubuntu:20.04

ubuntu:22.04

Removed from the Ubuntu 24.04 image due to maintenance reasons.

—
Reply to this email directly, view it on GitHub
https://github.com/actions/runner-images/issues/10636#issuecomment-2566573341,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BL2VY2KGM5MR45TWMOMUSKL2ILASRAVCNFSM6AAAAABOMAXFGGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRWGU3TGMZUGE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

The lack of mono and nuget seems to irrevocably break our CI.


[Polkadot Wiki Migration] Chill Your Node

This page was migrated from https://wiki.polkadot.network/docs/maintain-guides-how-to-chill

Scan for Vale false positives. Resolved convos = made it on the update list and should go away now. I left comments for the legit flags with suggested edits. Thank you!

Closing this PR as this content is handled in PR #127


Also cancel any ongoing edit-history based prefetches when syncing is enabled, and check for context cancellation right away when processing prefetch requests.

I don't think I understand why we're cancelling those prefetches whenever there might be a sync prefetch scheduled for those same blocks.

@jakob223 if syncing is being enabled with this SetSyncConfig call, it won't get started until the end of the function, after the working set prefetches are canceled (and we wait for them to complete).  If syncing was already enabled, then they shouldn't be happening yet.  I guess we don't strictly have to cancel them since the any full or partial sync should just override them and move the blocks into the right cache, but it makes the logs messier and probably wastes CPU to have them going on in the background for no reason.

you'll have a conflict with your PR to move out handlePrefetchRequest

@jzila yeah known, I'll deal with that when rebasing the other PR, no problem.
I also just added a small test flake fix to this PR, so that we only cancel the prefetches when not in test mode.  Otherwise it messes with very specific ordering requirements on some prefetch-related tests.


fbp-spec support not working

Was disabled while porting to Webpack (#585). Also had some issues before this, so should be verified working against some runtime.
Partially related to #561, as that is area where tests status is

The webpack thing has been fixed, the code is not disabled anymore at least.

Actually there were a bunch of hidden Webpack related issues, https://github.com/flowbased/fbp-spec/pull/86


Add instructions to use in corporate environment

thefuck is extremely useful for developers and other professions that might require using, for example, a locked down Macbook that does not have local administrator access. I think it is important to include some instructions on how to get the tool set up in such an environment because it may not be obvious but fairly straightforward if you know what you're doing.
By the way, since I use it as an example, I got fish installed without admin access too:
ln -s ~/Applications/fish.app/Contents/Resources/base/usr/local/bin/fish ~/bin/fish

Fixes #1252

I think a cleaner way than using thedang --alias | sed .. would be to just specify the alias to be dang:
user@ubuntu:~$ for x in ~/.local/bin/{fuck,thefuck}; do ln -vs "$x" "${x%fuck}dang"; done
'/home/user/.local/bin/dang' -> '/home/user/.local/bin/fuck'
'/home/user/.local/bin/thedang' -> '/home/user/.local/bin/thefuck'
user@ubuntu:~$ thedang --alias dang

            function dang () {
                TF_PYTHONIOENCODING=$PYTHONIOENCODING;
                export TF_SHELL=bash;
                export TF_ALIAS=dang;
                export TF_SHELL_ALIASES=$(alias);
                export TF_HISTORY=$(fc -ln -10);
                export PYTHONIOENCODING=utf-8;
                TF_CMD=$(
                    thefuck THEFUCK_ARGUMENT_PLACEHOLDER "$@"
                ) && eval "$TF_CMD";
                unset TF_HISTORY;
                export PYTHONIOENCODING=$TF_PYTHONIOENCODING;
                history -s $TF_CMD;
            }

user@ubuntu:~$

No need for sed. If you want you could use the above for the instructions for Bash.

@rany2 The --alias argument only changes the name of the alias to type in, not the script that alias is calling. Take a look at TF_CMD in your example. This would've worked for you because thefuck is also in your $PATH, if someone has set this up as thedang instead of thefuck it would not work. sed will change both to remove the word "fuck".

@mensly Sorry I didn't notice. I get why you did it now but I am not sure if sed might unintentionally break something in the future. Might be better to just add an option that allows you to set a custom thefuck

This PR is intended only to document how the current product can be installed and used in a corporate environment, I like the idea of that option you spoke of though I think an alternative would be for the script name thefuck to be replaced with whatever the current command is that called thefuck --alias. Python isn't my main language, but I think sys.argv[0] has this string. I might experiment with this and if it proves useful do another PR after this one is merged.
I faced a lot of technical issues when I was trying to get this working myself and wanted to help others have an easier time. My current employer is actually ok with some casual swearing if it isn't used to hurt people, but I didn't know that when I was getting my computer set up which is why I set it up as dang. My example of configuring for fish is only an example of what is described in the previous paragraph.  I'll add an extra sentence clarifying this.
As for outputting 'No fucks given', modifying the behaviour of the code will depend more on someone's environment. As this is something I haven't needed to do I can't tell you the best solution but I can imagine you could either edit your local copy of the .py file this string is contained in, or modifying the alias to edit stdout:
TF_CMD=$(
    thedang THEFUCK_ARGUMENT_PLACEHOLDER "$@" 2>&1 | sed 's/fuck/dang/'
) && eval "$TF_CMD";

A command line argument to set the error message (both when aliasing and evaluating) would be a better solution, so I might also look into that in the future PR I mentioned. To reiterate, I wanted to document what I needed to do to get the current version working on a corporate-controlled computer but am interested in modifying the software. I have another project I'm focused on at the moment, but worst case scenario this is MIT licensed so I can always publish to PyPI under the name thedang just to make it easier for people like me to use their preferred tools in their day job.

Wiki is the place for that.


Issue 160

Description

Checklist

[X] The documentation reflects the changes.
[ ] I have manually tested the application to make sure the changes don’t cause any downstream issues.
[ ] In case I changed one of the services’ models.py I have performed the appropriate database migrations.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.mitchell glass seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Awesome work @mitchglass97!


Places to buy b1248 and b1236 LED badges

Given my recent experience buying a b1248 on eBay and actually receiving a gd1144 (incorrectly or deceptively labelled as a b1248), I thought I'd share the more promising prospects for online purchasing of b1248 and b1236 badges.
I hope that the wares sold by the following vendors will prove to be compatible with the Firmware @Effix has skillfully designed for this project. Here goes:

Hangel Technology - offers b1248s in six colours. I've had the resolution confirmed via follow-up contact. http://www.hangeltech.com/12x48-Dots-LED-Name-Badge-Programmable-Message-Badge-Name-Card-pd743293.html

Hangel Technology - also offers b1236s in six colours. http://www.hangeltech.com/12x36-Pixels-Programmable-LED-Name-Tag-Badge-Display-pd133293.html

HUIJIE - claims to sell b1248, b1236 and b729 LED Badges (with images that match those specifications). White b1248s are listed with 11*44 resolution while others are consistent with labelling: https://www.aliexpress.com/store/group/LED-NAME-CARD-DISPALY/718814_100133041.html

colortop9 (eBay seller) - sells red b1248s (with one program/brightness button and ARM controller) https://www.ebay.com.au/itm/Programmable-LED-Digital-Scrolling-Message-Name-Tag-Id-Badge-12x48-Pixels-E8O6/302751067892

JD LED - offers red b1248s (with accurate images and specs): https://www.aliexpress.com/item/led-name-card-led-mini-sign-Led-name-badge-LN-1248R/725506574.html

Slw6668888 - offers six colours of b1236s (with images showing correct number of LEDs): https://www.dhgate.com/product/high-quality-12-36-dots-led-name-badge-red/269871612.html?recinfo=17,null,1#svh-1-5|null:null:r0537435988

Shop-fun.com - offers b1236, available colours unclear. Images show unusual layout of pixels, with each column offset half-a-pixel from the next: http://www.shop-fun.com/index.php?route=product/product&keyword=led+badge&category_id=0&product_id=55924

Note: the accuracy of these listings is yet to be tested/confirmed, so buyer beware!

A note for people reading this thread in isolation from other discussion:
Not all 1248 pixel or 1236 pixel badges will be compatible with this replacement firmware and software.
It appears that somewhere between 2015 and 2018, PCBs for 1248s and 1236s were redesigned to use ARM controllers instead of AVRs. I've asked around, and the consensus is that the newer PCB design (which has far fewer complex components) likely reduced the manufacturing cost per unit, but also had the side-effect of making it much harder to flash new firmware onto.
To "unlock" the full potential of the device using @Effix firmware, you will need an older configuration of the device which uses AVRs.


AI Vulnerability Scoring System

Hi there,
what's the plan to include the equivalent of a CVSS for the AI vulnerabilities?
I have been working on a (theoretical) scoring system approach for some time, too long to write here but would be more effective as a small workshop.
Cheers.
PS
Please don't ask me to use Discord!

Hi Priamai,
Please, reach the MITRE ATLAS slack/discord team. I remember they were working on the CVSS scoring for AI vulnerabilities.
-Lionel.


Added badges for Travis and RTD in README.md

Signed-off-by: Tkachuk<EMAIL_ADDRESS>

This change is

Please review @rbbratta @seungweonpark @lijenni @esmacgil
How it looks and works yo can find in my taf fork
https://github.com/NazarTkachuk/taf/blob/badges/README.md

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Could you fix this error please?

I use this library on django and lately I am getting the following error:
File "/usr/lib/python2.6/site-packages/exifread/init.py", line 221, in process_file
hdr.decode_maker_note()
File "/usr/lib/python2.6/site-packages/exifread/classes.py", line 401, in decode_maker_note
tag_dict=makernote.CASIO)
File "/usr/lib/python2.6/site-packages/exifread/classes.py", line 232, in dump_IFD
for i in values:
TypeError: 'NoneType' object is not iterable
I would appreciate if you could look into it.
Thanks!

Closing due to lack of update.


404 Not Found

I have this error when i finish installation does not show any page may i help me please and am using laravel 8.

Hello @NGERERI will you please share the error screenshot with us.


logging: Add log_output flushing to synchronous processing

Even though interrupts are locked before processing in synchronous
call, it is still possible that they will be interrupted by NMI.
In that case log_output module may assert because of buffer
overwriting.
Added flushing of log_output buffer before starting the process to
ensure that output buffer is always in reset state at the beginning.
It is related to #19238 but it does not fix it. The actual root cause in #19238 ( and #19245 probably) is stack guard fault. When all tests started to use LOG_IMMEDIATE by default (https://github.com/zephyrproject-rtos/zephyr/commit/2192499fe0e8951c721e73bb58239da364fd6770) stack usage in tasks increased (because strings are formatted in the context of log call).
This PR fixes logger so it prints correctly when NMI happens while log message
is processed. After this fix usb test mentioned in #19238 fails with:
[00:00:00.004,852] <dbg> usb_descriptor.usb_get_device_descriptor: __usb_descriptor_start 0x20003380
[00:00:00.014,373] <dbg> usb_descriptor.usb_get_device_descriptor: __usb_descriptor_end 0x200033d9
[[00:00:00.023,742] <err> os: ***** MPU FAULT *****
[00:00:00.029,296] <err> os:   Stacking error (context area might be not valid)
[00:00:00.037,261] <err> os:   Data Access Violation
[00:00:00.042,907] <err> os:   MMFAR Address: 0x20002218
[00:00:00.048,919] <err> os: r0/a1:  0x0014a220  r1/a2:  0x519d5540  r2/a3:  0x045e28e8
[00:00:00.057,586] <err> os: r3/a4:  0xd0f94fce r12/ip:  0x0000ac38 r14/lr:  0x00000ec1
[00:00:00.066,284] <err> os:  xpsr:  0x61000000
[00:00:00.071,502] <err> os: Faulting instruction address (r15/pc): 0x0000a192
[00:00:00.079,406] <err> os: >>> ZEPHYR FATAL ERROR 2: Stack overflow
[00:00:00.086,517] <err> os: Current thread: 0x20001820 (main)
[00:00:00.093,017] <err> os: Halting system

@pizi-nordic can you please take another look?
@andrewboie please review in context of #19322


Resource allocation in a VerneMQ cluster

To help us save time and help you faster
I am monitoring a VerneMQ cluster of 3 nodes using Netdata+Prometheus and I am seeing some behavior I do not fully understand. How are resources allocated in a VerneMQ cluster?
Environment

VerneMQ Version: vernemq/vernemq:latest docker image
OS: Debian 10 using Docker (Azure VM scaleset)
Load balancing handled by an Azure load balancer
Cluster size: 3

Expected behaviour

I expect that the three nodes will all send and receive messages about equally. Each node should have a queue with about the same number of messages in it.

Actual behaviour

A single node is sending/receiving all messages. A single node has all of the messages in its queue while the others have none.
I am seeing communication between nodes, and that two of the nodes which have no messages in their queues are however sending data to the one node that does have messages in its queue (via the cluster bandwidth stat).

Additionally I would like to ask what exactly does the "scheduler utilization" indicate?
I'm just trying to understand the behavior I'm observing and if it indicates, for example, that the cluster size is larger than necessary. Or perhaps I am just misunderstanding how the cluster allocates resources and this is perfectly normal? Or is it indicating a problem with the load balancer? I apologize if this is not super clear what I'm asking, please do let me know if you need clarification. Thank you in advance for the help!

@karlokr-p

Each node should have a queue with about the same number of messages in it.

Nodes do not "have a queue". Each consumer has a queue (which is living on the node the consumer is connected to, that's true).
The traffic for that consumer is then routed to that queue and that node.


Hyperlink should be valid and start with https:// or mailto: or valid grn resource

here's a real example from our articles we are trying to import:
555.555.1234

Parser output:
 {'type': 'Text', 'text': {'text': '555.555.1234', 'hyperlink': 'tel:555.555.1234'}}

I have forwarded the request to support tel: links in knowledge articles to product managers.

Thank you!
On Thu, Jun 20, 2024 at 4:08 AM tmelko-genesys @.***>
wrote:

I have forwarded the request to support tel: links in knowledge articles
to product managers.
—
Reply to this email directly, view it on GitHub
https://github.com/MyPureCloud/knowledge-html-converter/issues/6#issuecomment-2180191049,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BC7VOJQXMWOYOKWPD6E4U5DZIKLX5AVCNFSM6AAAAABITKIPQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBQGE4TCMBUHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Record densify bug

In GitLab by @ksiero on Apr 5, 2018, 15:25
I think I've found bug in file record_datatype.cxx.
Datatype_uptr Record_datatype::densify() const
{
    long displacement = 0;
    vector<Record_datatype::Member> densified_members;
    for (auto&& member : m_members) {
        densified_members.emplace_back(displacement, member.type().densify(), member.name());
        displacement += densified_members.back().type().datasize();
    }
    return unique_ptr<Record_datatype> {new Record_datatype{move(densified_members), m_buffersize}};
}

We are returning densified record datatype, but size of the new record is m_buffersize, shouldn't it be m_datasize?

closed via merge request !124

@ksiero does that seem ok to you?

oops, wring place, I meant to post that on the merge request

created branch 85-record-densify-bug


[PRM-494]: updated Reasonable excuse list page title for lsp's

AT's -> https://github.com/hmrc/penalties-acceptance-tests/pull/55


Add mcfunction language

Description
This is an interesting case of "language" that originates from Minecraft server commands. The mcfunction file format is essentially a collection of server commands, one per line, with additional comment support and some unique runtime properties. The idea is simple, but the underlying command system is complex enough to warrant discussion about whether mcfunction should be considered a type of programming language. In any case: mcfunction files are both written and distributed in plain text, naturally giving way to open-source collaboration.
The search results listed in the checklist provide proof that mcfunction is being used across a reasonable number of repositories. There's even an open-source language server in development that includes extensive support for the mcfunction format.
I ran linguist dev on the language-mcfunction repository to get a breakdown of the results and to ensure my changes are functional.
Checklist:

[x] I am adding a new language.

[x] The extension of the new language is used in hundreds of repositories on GitHub.com.

Search results for each extension:

mcfunction:

Using suggested nothack
Using keyword tellraw
Using keyword setblock
Using keyword area_effect_cloud

[x] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

showcase.mcfunction from language-mcfunction

Sample license(s): MIT

[x] I have included a syntax highlighting grammar
I have updated the heuristics to distinguish my language from others using the same extension.

Note: there are no other languages using the extension mcfunction

Not sure why the build "errored" as opposed to failing or passing. Looks like it got part way through script/travis/before_install and then died for no apparent reason:
https://travis-ci.org/github/linguist/jobs/494397050#L1494

Yes, there's something missing. Did you use the provided script to add the grammar as per the contribution guidelines? Did you get any error message?

Yes I followed the contribution guidelines thoroughly. I ran the script, and it was successful. I was able to run linguist and get a breakdown afterwards.
I cross-referenced with some other language PR's (here and here) and couldn't find any evidence of what's missing here.

Maybe you forgot to commit the submodule itself then. It should be under vendor/grammars/name of the grammar repo.

Nice catch. But because language-mcfunction has received commits since I submitted the PR, I'm now facing a problem where the cached license is outdated. And apparently the language is not sorted correctly, but IIRC it was a script that added it. (?) Anyway, I'll fix and try again.

This may or may not be worth consideration, but there is an inconsistency between vendor/README.md and lib/linguist/languages.yml regarding how languages are sorted by name. As far as I can tell, the latter sorts upper-case first whereas the latter disregards case and mixes them together.

As far as I can tell, the latter sorts upper-case first whereas the latter disregards case and mixes them together.

Indeed. @Alhadis What do you think? Let's sort case-sensitively?

Thanks for reviewing!
Small suggestion for CONTRIBUTING.md: add a step for Testing under the Adding an extension to a language and sections Adding a language. I think it could reduce the number of questions as a result of Travis errors, and also encourage contributors to submit cleaner PRs. :)

@Alhadis What do you think? Let's sort case-sensitively?

Sorry, I missed this. Yes, let's. Case-sensitive is strange and feels very machine-line.


Hungarian translation

Created a Hungarian translation of Leaflet.Storage and fixed a grammar mistake in one of the English strings.

I have just noticed that you use Transifex for managing translations. I have uploaded all translations there, so I am closing this pull request.

Thanks, and sorry for the lag!
I'll pull in the new translations and release a new version soon!


CascadinValue changed Drawer side to right

Bug type
Component
Component name
Drawer
What happened?
I added a CascadingValue to my AppLayout. After this change my Drawer changed the side from left to right.

Expected behavior
Drawer should keep on left side
Reproduction link
https://try.mudblazor.com
Reproduction steps

Add simple CascadingValue to AppLayout

Relevant log output
No response
Version (bug)
6.0.10
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Please add a try.mudblazor reproduction link

As far as I know this problem was solved on the discord server @kevinvenclovas can confirm it?
Seems like adding a cascading name fixed the problem.

This has been fixed by #5270.


upgrading to 14.0.2 - .tsx: Unexpected token, expected "}"

Hi, after upgrading to 14.0.2 I get this  error when i run the command gql-gen, but the typescript is perfectly valid. :S
> gql-gen

  √ Parse configuration
  > Generate outputs
    > Generate src/app/shared/models/graphql/types.ts
      √ Load GraphQL schemas
      × Load GraphQL documents
        →   35 |       ],
        Generate
    √ Generate src/app/shared/models/graphql/services.ts

     We found 1 errors

     Failed to generate src/app/shared/models/graphql/types.ts
SyntaxError: C:\Users\<username>\source\repos\<projectname>\MyProject.Web\.tsx: Unexpected token, expected "}" (32:14)

30 |   static forRoot(): ModuleWithProviders {
31 |     return <ModuleWithProviders>{
> 32 |       ngModule: CoreModule,
    |               ^
33 |       providers: [
34 |         ...NB_CORE_PROVIDERS,
35 |       ],

codegen.yml
schema:
  - 'schema.json'
overwrite: true
config:
  avoidOptionals: false
generates:
  src/app/shared/models/graphql/types.ts:
    documents:
      - './src/app/**/*.ts'
    plugins:
      - 'typescript-common'
      - 'typescript-client'
      - 'typescript-server'
  src/app/shared/models/graphql/services.ts:
    documents:
      - './src/app/**/*.gql'
    plugins:
      - 'typescript-common'
      - 'typescript-client'
      - 'typescript-apollo-angular'

I am also encountering this, I tackled it by moving all my queries to files that have the same name. (eq. queries.ts in every directory that has files that use graphql.)

Thats not something I am willing to do... So I downgraded to the 4.0.1.alpha version

@furier @wesselvdv could you check 0.15.0-alpha.7df98bdf?

@kamilkisiela not getting the error with: 0.15.0-alpha.7c1a7d2a

We changed the way we extract documents from ts and js files. Before that we used RegExp, now we use the library that our teammate wrote. It uses AST to find stuff based on the default export of graphql-tag.
I'll release a v0.14.4 soon.

v0.14.4 released

@kamilkisiela I have tried both 0.14.4 and 0.14.5 and they both continue to give me the exact same issue, deleted node_modules and installed packages again, just to make sure and no change :(

Could you also remove yarn.lock?

on it...

still same issue @kamilkisiela

rolling back to 0.15.0-alpha.7c1a7d2a in the meantime

Reproduced and fixed in #982

Released in v0.15.0


more cuts off last line of input when more than one page of output

Running current master on Debian Unstable in WSL2, with both CMD and Windows Terminal.  I think this is probably a bug in more as opposed to WSL2, since it seems to calculate the terminal height correctly, but I don't have a native Linux install available right now to test with.
Easy repro (replace 60 with some number higher than your current terminal # of rows):
for i in {1..60..1}; do echo "$i"; done

vs
for i in {1..60..1}; do echo "$i"; done | target/debug/coreutils more

The last line should be 60 (or whatever you put in the for loop).

Actually, it happens even when the number of lines is exactly the terminal height,  In that case, it exposes an additional difference between coreutils more and util-linux more: util-linux more pages the output, coreutils more just cuts off one line but doesn't page the output.

It simply crashes for me lol
   Compiling coreutils v0.0.6 (/Users/hbina/git/coreutils)
    Finished dev [unoptimized + debuginfo] target(s) in 10.04s
     Running `target/debug/coreutils more`

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

--More--(38%)thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: IoError(Custom { kind: Other, error: "Failed to initialize input reader" })', src/uu/more/src/more.rs:235:51
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Thanks for the report and the easy repro! I think I fixed it.


docs(ontology): update docs and show hint in ontology-form (DSP-1139)

resolves DSP-1139

This is how it works:


Inline non-template functions

There are a lot of non-template functions which are not inlined which causes problems when linking and using percy in multiple source files.
This is a list of some affected functions (in maybe not the most recent version inside mockturtle):
https://github.com/lsils/mockturtle/commit/3491d01519a21f073ca44ce9bc110822157e535c

Fixed