Ubuntu-latest workflows will use Ubuntu-20.04

UPDATE: Migration has been finished and all ubuntu-latest builds are using Ubuntu 20.04
Ubuntu-20.04 is ready to be the default version for the “ubuntu-latest” label in GitHub Actions and Azure DevOps. This change will be rolled out over a period of several weeks beginning on November, 30. (December, 22 - January, 4 will be a migration break due to holidays)
If you see any issues with your workflows during this transition period:

File an issue in this repository
Switch back to Ubuntu 18.04 by specifying the “ubuntu-18.04” label. We will continue to  support Ubuntu 18.04.

Note that image software between Ubuntu-18.04 and Ubuntu-20.04 differs not only by the pre-installed versions of tools, but also by the default versions of some tools. See the list of missing and changes software below.
Software differences

Tool name
Ubuntu 18.04
Ubuntu 20.04
Notes

AWS CLI
1.18.173
2.0.62
These two versions have major set of breaking changes. See migration guide for details

.NET Core
2.1.x, 3.0.x, 3.1.x
2.1.x, 3.1.x
.NET Core 3.0 was removed (3.0.100, 3.0.101, 3.0.102, 3.0.103). NET Core 3.0 has reached end of life, meaning it is no longer supported and not recommended to use. If you still need it, consider using setup-dotnet and UseNetCore tasks.

Java
78(default)1112
811(default)
If you need to use other versions of Java, consider using setup-java and Java tool installer tasks.

Android
17.0 - 30.0
27.0 - 30.0
Android Platforms and build tools < 27.0 were removed from image. Consider installation in runtime using sdkmanager

Ruby
2.5.1
2.7.0
Default Ruby was changed from 2.5.x to 2.7.x. Consider using setup-ruby and UseRuby tasks.

Ruby toolcache
<IP_ADDRESS>.7
<IP_ADDRESS>
Ruby 2.4 will become unavailable via install tasks

Python3
3.6.9
3.8.2
Default Python will be updated from 3.6 to 3.8. Consider using setup-python or UsePython to switch version

PHP
<IP_ADDRESS>.48.0
7.48.0
-

Azure PowerShell
1.0.0, 1.6.0, 2.3.2, 2.6.0, 2.8.0, 3.1.0, 3.5.0, 3.8.0, 4.3.0, 4.4.0, 4.6.0, 4.7.0
4.8.0
-

Boost
1.72.0
-
Boost is not pre-installed on Ubuntu 20.04 image

MySQL
5.7
8.0
See migration guide for more details about breaking changes

SVN
1.9.7
1.13.0
-

Swig
3.0.12
4.0.1
-

libcurl apt package
libcurl3
libcurl4
-

Clang
6 8 9 (default)
8 9 10(default)
-

Missing software
Known issues:

libcurl3 missing in the repo, replaced with libcurl4
Python2 is absent on Ubuntu 20, but required for some packages to install. Can be installed via apt-get install python-is-python2 or via toolcache
Python2 pip should be installed separately(curl https://bootstrap.pypa.io/get-pip.py  --output get-pip.py, python2 get-pip.py)
Ansible should be installed from the official Ubuntu repo, ppa:ansible/ansible isn't updated yet
Set condition in git-lfs installation (Ubuntu 18 & 20 can install git-lfs from Ubuntu repo)
Android SDK should be pointed to Java8 explicitly

Deprecated:
Haskell: https://launchpad.net/~hvr/+archive/ubuntu/ghc-eol

ghc-8.0.2
ghc-8.2.2
ghc-8.4.4
ghc-8.6.2
ghc-8.6.3
ghc-8.6.4
ghc-8.8.1
ghc-8.8.2
cabal-install-2.0
cabal-install-2.2
cabal-install-2.4
cabal-install-3.0

.Net Core
2.2 — EOL December 23, 2019:

2.2.402/dotnet-sdk-2.2.402-linux-x64.tar.gz
2.2.401/dotnet-sdk-2.2.401-linux-x64.tar.gz
2.2.301/dotnet-sdk-2.2.301-linux-x64.tar.gz
2.2.300/dotnet-sdk-2.2.300-linux-x64.tar.gz
2.2.207/dotnet-sdk-2.2.207-linux-x64.tar.gz
2.2.206/dotnet-sdk-2.2.206-linux-x64.tar.gz
2.2.205/dotnet-sdk-2.2.205-linux-x64.tar.gz
2.2.204/dotnet-sdk-2.2.204-linux-x64.tar.gz
2.2.203/dotnet-sdk-2.2.203-linux-x64.tar.gz
2.2.202/dotnet-sdk-2.2.202-linux-x64.tar.gz
2.2.110/dotnet-sdk-2.2.110-linux-x64.tar.gz
2.2.109/dotnet-sdk-2.2.109-linux-x64.tar.gz
2.2.108/dotnet-sdk-2.2.108-linux-x64.tar.gz
2.2.107/dotnet-sdk-2.2.107-linux-x64.tar.gz
2.2.106/dotnet-sdk-2.2.106-linux-x64.tar.gz
2.2.105/dotnet-sdk-2.2.105-linux-x64.tar.gz
2.2.104/dotnet-sdk-2.2.104-linux-x64.tar.gz
2.2.103/dotnet-sdk-2.2.103-linux-x64.tar.gz
2.2.102/dotnet-sdk-2.2.102-linux-x64.tar.gz
2.2.101/dotnet-sdk-2.2.101-linux-x64.tar.gz
2.2.100/dotnet-sdk-2.2.100-linux-x64.tar.gz

3.0 — EOL March 3, 2020:

3.0.103/dotnet-sdk-3.0.103-linux-x64.tar.gz
3.0.102/dotnet-sdk-3.0.102-linux-x64.tar.gz
3.0.101/dotnet-sdk-3.0.101-linux-x64.tar.gz
3.0.100/dotnet-sdk-3.0.100-linux-x64.tar.gz

Azure PowerShell

1.0.0
1.6.0
2.3.2
2.6.0
2.8.0
3.1.0
3.5.0

Each major Go release is supported until there are two newer major releases.  We fix critical problems, including critical security problems, in supported releases as needed by issuing minor revisions
GOLang

Go 1.11,1.12,1.13

Java:

Java 7
Default JDK set to 11

PHP

7.1
7.2
7.3

Android:

"platforms;android-26"
"platforms;android-25"
"platforms;android-24"
"platforms;android-23"
"platforms;android-22"
"platforms;android-21"
"platforms;android-19"
"platforms;android-17"
"build-tools;26.0.3"
"build-tools;26.0.2"
"build-tools;26.0.1"
"build-tools;26.0.0"
"build-tools;25.0.3"
"build-tools;25.0.2"
"build-tools;25.0.1"
"build-tools;25.0.0"
"build-tools;24.0.3"
"build-tools;24.0.2"
"build-tools;24.0.1"
"build-tools;24.0.0"
"build-tools;23.0.3"
"build-tools;23.0.2"
"build-tools;23.0.1"
"build-tools;22.0.1"
"build-tools;21.1.2"
"build-tools;20.0.0"
"build-tools;19.1.0"
"add-ons;addon-google_apis-google-24"
"add-ons;addon-google_apis-google-23"
"add-ons;addon-google_apis-google-22"
"add-ons;addon-google_apis-google-21"
"cmake;3.6.4111459"

Why is this being output as a warning? If a user relies on behavior from a specific version, they should be pinning it.

Hi @jhpratt ,
we have added a warning for those workflows who are using ubuntu-latest to notify about the upcoming change and give a time to check workflows and adjust them if needed beforehand the transition.
ubuntu-18.04 is the most popular OS in GitHub Actions and most of the customers are using it by tagging ubuntu-latest, so we should use as many communication channels as possible to reduce the unpredictable impact.

What about node.js lts? Will ubuntu-latest support node.js v14.15.1 (Current LTS)?

@romashko-bo-ma , Every image (both ubuntu 18.04 and 20.04) have Node.JS 8, 10, 12, 14. You should use setup tasks to switch it:

actions/setup-node (GitHub Actions)
UseNode (Azure DevOps)

@romashko-bo-ma , Every image (both ubuntu 18.04 and 20.04) have Node.JS 8, 10, 12, 14. You should use setup tasks to switch it:

actions/setup-node (GitHub Actions)

UseNode (Azure DevOps)

We're currently using actions/setup-node... but why not make support of Nodejs LTS out of the box?

Actually, all ubuntu images have Node.JS 14 as default: https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md#language-and-runtime
But I suggest continue using actions/setup-node. We often see customers' reports where they are unhappy with unexpected default version updates. This task takes less than seconds to run but will guarantee that you are not broken in ftuure.

we have added a warning for those workflows who are using ubuntu-latest to notify about the upcoming change and give a time to check workflows and adjust them if needed beforehand the transition.

Thanks for adding this notice!
Would it be possible to add a way to acknowledge or dismiss the notice once a project has verified support with 20.04? With the rollout currently set to take several weeks, and not starting until November 30, that means at least a few months of notices being added when using ubuntu-latest, even if compatibility has already been confirmed.

Hi, I'm wondering if this recent change could have bring some issue with ca-certificates:
This dockerfile (https://github.com/naubryGV/cpp-clang-check/blob/master/Dockerfile) was working pefectly fine yesterday, but now I'm getting those:
  W: http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease: No system certificates available. Try installing ca-certificates.
  W: http://security.ubuntu.com/ubuntu/dists/focal-security/Release: No system certificates available. Try installing ca-certificates.
  E: The repository 'http://security.ubuntu.com/ubuntu focal-security Release' does not have a Release file.

Not sure if it's the way to report those kind of issues.

Actually, all ubuntu images have Node.JS 14 as default: https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md#language-and-runtime
But I suggest continue using actions/setup-node. We often see customers' reports where they are unhappy with unexpected default version updates. This task takes less than seconds to run but will guarantee that you are not broken in ftuure.

@maxim-lobanov thanks for reply! Agree, unexpected version upgrade can bring issues.

Hi, I'm wondering if this recent change could have bring some issue with ca-certificates:
This dockerfile (https://github.com/naubryGV/cpp-clang-check/blob/master/Dockerfile) was working pefectly fine yesterday, but now I'm getting those:
  W: http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease: No system certificates available. Try installing ca-certificates.
  W: http://security.ubuntu.com/ubuntu/dists/focal-security/Release: No system certificates available. Try installing ca-certificates.
  E: The repository 'http://security.ubuntu.com/ubuntu focal-security Release' does not have a Release file.

Not sure if it's the way to report those kind of issues.

This is not related to this issue. I suggest creating new issue.

Hi, I'm wondering if this recent change could have bring some issue with ca-certificates:
This dockerfile (https://github.com/naubryGV/cpp-clang-check/blob/master/Dockerfile) was working pefectly fine yesterday, but now I'm getting those:
  W: http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease: No system certificates available. Try installing ca-certificates.
  W: http://security.ubuntu.com/ubuntu/dists/focal-security/Release: No system certificates available. Try installing ca-certificates.
  E: The repository 'http://security.ubuntu.com/ubuntu focal-security Release' does not have a Release file.

Not sure if it's the way to report those kind of issues.

This is not related to this issue. I suggest creating new issue.

Will do, thank you.

@maxim-lobanov
FYI: it's working perfectly when I change from:
runs-on: ubuntu-latest
to
runs-on: ubuntu-18.04
And I'm doing nothing but an apt-get update.
I did create another bug entry, but I just find it odd.

Hi @desrosj,

Would it be possible to add a way to acknowledge or dismiss the notice once a project has verified support with 20.04?

You can specify a certain version of Ubuntu instead of ubuntu-latest. This warning targets only those workflows who use ubuntu-latest that resolves to 18.04 or to 20.04 and fails during transition period.

Hi @AlenaSviridenko,

You can specify a certain version of Ubuntu instead of ubuntu-latest.
It's preferable to remain on ubuntu-latest for a few reasons. The notice added here is also a good notifications to test a project against upcoming changes.

Also, changing to use a specific version would mean having to change back to ubuntu-latest later if using latest is preferred.
I was thinking this through, maybe having a secret that could be defined on a repo to suppress these notices (GITHUB_UBUNTU_20, or something similar) would be an easy way to "acknowledge" the repo has tested 20.04 and is ready for the transition.

This warning targets only those workflows who use ubuntu-latest that resolves to 18.04 or to 20.04 and fails during transition period.

I am currently seeing the notices appear for successful jobs within workflows. Unless the notice is for all jobs until the transition period begins and will be switched to failures later?

Actually, yes, it is preferable to stay on ubuntu-latest even from our point of view, because we consider the amount of pipelines that are using this tag when we start transition.

Unless the notice is for all jobs until the transition period begins and will be switched to failures later?
That is correct. Until the transition begins we show it for all ubuntu-latest workflows. After transition is started - we will show it for those who still resolves to 18.04 or who resolves to 20.04 but fails.

I will check with our engineers if it is possible to suppress notice if 20.04 is tested and verified. Thanks!

will https://launchpad.net/~hvr/+archive/ubuntu/ghc be used instead for GHC? or whats the inclusion plan?
thnx :)

publishing code coverage(using cobertura) on ubuntu 20.04 seens to be broke on ubuntu 20.04. Can anyone confirm that?
I'm getting this log:

Hi @cartazio, not sure what do you mean, we are currently installing 3 latest GHC version, please check this code.
Do you mean installing some additional versions?

Hi @ezequielramos, we are not pre-installing cobertura for all Ubuntu images, only for Windows images. Could you please confirm that it is the issue with the image and if yes - file a separate issue in our repo, and we will investigate it.

Python2 pip should be installed separately

FWIW, this breaks GitHub's CodeQL action which suggests using ubuntu-latest but needs pip2 without setting it up. I opened a PR over there: https://github.com/github/codeql-action/pull/316

The README.md currently states:

The Ubuntu 20.04 virtual environment is currently provided as a preview only.

Is this no longer the case? I assume 20.04 is out of preview if it is becoming ubuntu-latest?
I'm trying to decide if I should pin to 18.04 or 20.04, I'd prefer to use the latest stable version.

👋 @paulboocock ,
correct, as soon as Ubuntu 20.04 will become ubuntu-latest this statement will be removed from docs, but actually it is already stable.

Hi @ezequielramos, we are not pre-installing cobertura for all Ubuntu images, only for Windows images. Could you please confirm that it is the issue with the image and if yes - file a separate issue in our repo, and we will investigate it.

Oh... I guess that's not right. My team is using ubuntu-18.04 for a long time and the cobertura is already pre-installed. In fact, we just changed the image from ubuntu-latest to ubuntu-18.04 and this problem stopped to occur.
We are using the task like this, as it is documented on the pipeline documentation, there is nothing there saying about image OS limitation:
          - task: PublishCodeCoverageResults@1
            condition: succeededOrFailed()
            inputs:
              codeCoverageTool: Cobertura
              summaryFileLocation: $(System.DefaultWorkingDirectory)/**/coverage/cobertura-coverage.xml
              reportDirectory: $(System.DefaultWorkingDirectory)/**/coverage
              failIfCoverageEmpty: true

Should I open a separate issue for you to investigate it?

@ezequielramos , hmm, that's interesting, ubuntu-latest still resolves to ubuntu-18.04, because transition hasn't started yet, I am not sure how image label change could help here.
Anyway, this seems to be more related to how PublishCodeCoverageResults task works on different OS versions, and we do not own these tasks, so I think you need to file an issue for Azure Pipelines Tasks team in their repo for investigation https://github.com/microsoft/azure-pipelines-tasks/issues

@AlenaSviridenko well, that's interesting indeed. I'll open an issue for Azure Pipelines Tasks team.
Thank you for your attention! :relaxed:

Will this update coincide with Ubuntu 20.04-LTS as a Base image option under the Deployment Inputs within Pipelines? Or are these completely separate from one another.

Hi @JimmyBanks, yes, ubuntu-20.04 as an immutable image in build options and ubuntu-20.04 that ubuntu-latest will point to - are the same images if that is what you mean.

Hi @JimmyBanks, yes, ubuntu-20.04 as an immutable image in build options and ubuntu-20.04 that ubuntu-latest will point to - are the same images if that is what you mean.

Thank you, in that case should Ubuntu 20.04 not be a selectable Base image during preview for testing? My team updated the pipeline YAML specification to vmImage: 'ubuntu-20.04'; however, the OS being installed on our VM image remains to be 18.04, which we believe is due to the Gallery Base Image options having 18.04 as the latest selectable option available (I've attached an image as an example).

As you can see, we cannot select 20.04 to test against.

Should we expect .NET 5 support on 20.04?

Should we expect .NET 5 preinstalled on 20.04?

Yes, .NET 5 support will come to 20.04 at the same time with 18.04

Node.js CI / build (14.x) on Ubuntu 20.04

@samirm00 , Node.js 14.x is currently a default Node.js version on ubuntu-20.04.

When ubuntu-latest fully rolls out, can you add a link to this GH issue (the differences between 18.04 and 20.04) to the 20.04 readme?

Hi @steved0x , Ubuntu 20.04 README already contains this link. We are usually keeping announcements in README 1 week after full deployment, but if it is needed we can keep this issue 2 weeks after the deployment.

Ansible should be installed from the official Ubuntu repo, ppa:ansible/ansible isn't updated yet

Not sure why they haven't been able to publish a proper repo for Ubuntu 20 yet...
I'm installing Ansible 2.10 via pip on my Ubuntu 20 system.
Works fine, but I guess that may be a different story for keeping dependencies up-to-date.

It seems like Ubuntu 18.04 has Clang 6 by default, not 9

@dsvi,
clang-9 is set by default on Ubuntu-18.04:

nope. apt-get clang gives you this:

nope. apt-get clang gives you this:

The default tag for clang in ubuntu official repo is clang-6, but the default clang version on the image is set to clang-9.
$ sudo apt-cache madison clang
     clang | 1:6.0-41~exp5~ubuntu1 | http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
     clang | 1:6.0-41~exp4 | http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
$ sudo apt-cache madison clang-6.0
 clang-6.0 | 1:6.0-1ubuntu2 | http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

any possibility of adding pnpm as a package manager?

/Rega Hawlery here

/Remove Server

@regamask What are you doing, exactly?

@autumnblazey , feel free to raise separate issue as feature request and we will consider it.
Hello everyone!
If you see any new issues with Ubuntu 20.04 or feature requests, please create separate issues in this repository.

Thanks @ben-hamelin for noticing PHP 8.0 is not in the table, updated it to not confuse others in the future.

PHP 8.0 is available on image side by side with php 7.x so you can use any of them.

How would one do that? I can't seem to find how to use specific software versions in a workflow, but I need to use 7.4 for the moment being and all my CI tests fail cause default version is now PHP 8.0.0
jobs:
  laravel:
    name: Laravel Testsuite
    runs-on: ubuntu-20.04
    steps:
    ...

@madsem ,
If you need to use specific version of PHP, you should specify it as phpx.y, examples: php7.4, php8.0. Alias php is just symlink to latest version so it is expected that it is updated when new version is released. I have posted some additional info in
https://github.com/actions/virtual-environments/pull/2162#issuecomment-747248199

Add this step to your workflow using ubuntu-latest:
   steps:
      - name: Set default PHP7.4
        run: sudo update-alternatives --set php /usr/bin/php7.4

fwiw, I'm pretty sure jq changes from 1.5 to 1.6. This is fairly notable as 1.6 adds some key features.

Hello. Any news when 'latest' switch to 20.04 eventually ? We've switched to hard-coded 20.04 in October and would love to switch back to latest. Or maybe the recommendation is to continue using 20.04 and you will warn people in the future when new version is available ?

Hello. Any news when 'latest' switch to 20.04 eventually ? We've switched to hard-coded 20.04 in October and would love to switch back to latest. Or maybe the recommendation is to continue using 20.04 and you will warn people in the future when new version is available ?

Hello @potiuk , migration is still in progress (it was suspended during holidays).
I don't see drawbacks to continue using ubuntu-20.04 label after migration and you won't need to worry that "latest" will be changed and will break your builds unexpectedly. Since we add only LTS Ubuntu releases to GitHub Action, images are added rarely (the next should be in April 2022, 22.04 😄 ) and we will notify about it in GitHub blog.

Hello @potiuk , migration is still in progress (it was suspended during holidays).
I don't see drawbacks to continue using ubuntu-20.04 label after migration and you won't need to worry that "latest" will be changed and will break your builds unexpectedly. Since we add only LTS Ubuntu releases to GitHub Action, images are added rarely (the next should be in April 2022, 22.04 😄 ) and we will notify about it in GitHub blog.

Deprecated:
Haskell: https://launchpad.net/~hvr/+archive/ubuntu/ghc-eol
* ghc-8.0.2
* ghc-8.2.2
* ghc-8.4.4
* ghc-8.6.2
* ghc-8.6.3
* ghc-8.6.4
* ghc-8.8.1
* ghc-8.8.2
* cabal-install-2.0
* cabal-install-2.2
* cabal-install-2.4
* cabal-install-3.0

I think this misleading and incorrect: see https://launchpad.net/~hvr/+archive/ubuntu/ghc

Deprecated:
Haskell: https://launchpad.net/~hvr/+archive/ubuntu/ghc-eol
* ghc-8.0.2
* ghc-8.2.2
* ghc-8.4.4
* ghc-8.6.2
* ghc-8.6.3
* ghc-8.6.4
* ghc-8.8.1
* ghc-8.8.2
* cabal-install-2.0
* cabal-install-2.2
* cabal-install-2.4
* cabal-install-3.0

I think this misleading and incorrect: see https://launchpad.net/~hvr/+archive/ubuntu/ghc

Deprecated:
Haskell: https://launchpad.net/~hvr/+archive/ubuntu/ghc-eol
* ghc-8.0.2 (incorrect!)
* ghc-8.2.2 (incorrect!)
* ghc-8.4.4 (incorrect!)
* ghc-8.6.2
* ghc-8.6.3
* ghc-8.6.4
* ghc-8.8.1
* ghc-8.8.2
* cabal-install-2.0
* cabal-install-2.2
* cabal-install-2.4 (incorrect!)
* cabal-install-3.0 (incorrect!)

I still this is not accurate: see https://launchpad.net/~hvr/+archive/ubuntu/ghc/+packages?field.name_filter=&field.status_filter=published&field.series_filter=focal
I am not a Ubuntu user but afaict cabal-install-2.4 and 3.0 are still available (3.0 is not that old - current stable is 3.2).
For ghc: 8.0.2, 8.2.2, and 8.4.4 all seem available still too.
(I just finally started used GitHub Actions today, so sorry for all the hoohaa! ;o) It's pretty cool.

Deprecated:
Haskell: https://launchpad.net/~hvr/+archive/ubuntu/ghc-eol
* ghc-8.0.2 (incorrect!)
* ghc-8.2.2 (incorrect!)
* ghc-8.4.4 (incorrect!)
* ghc-8.6.2
* ghc-8.6.3
* ghc-8.6.4
* ghc-8.8.1
* ghc-8.8.2
* cabal-install-2.0
* cabal-install-2.2
* cabal-install-2.4 (incorrect!)
* cabal-install-3.0 (incorrect!)

I still this is not accurate: see https://launchpad.net/~hvr/+archive/ubuntu/ghc/+packages?field.name_filter=&field.status_filter=published&field.series_filter=focal
I am not a Ubuntu user but afaict cabal-install-2.4 and 3.0 are still available (3.0 is not that old - current stable is 3.2).
For ghc: 8.0.2, 8.2.2, and 8.4.4 all seem available still too.
(I just finally started used GitHub Actions today, so sorry for all the hoohaa! ;o) It's pretty cool.

@maxim-lobanov
When can we expect 20.04 to be a base image that is selectable in DevOps -> Releases ->Task -> Build Machine Image?
Right now 14.04.4, 16.04, and 18.04 are selectable, but not 20.04
If this isn't the correct location to bring up this issue, do you know where is?

@maxim-lobanov
When can we expect 20.04 to be a base image that is selectable in DevOps -> Releases ->Task -> Build Machine Image?
Right now 14.04.4, 16.04, and 18.04 are selectable, but not 20.04
If this isn't the correct location to bring up this issue, do you know where is?

@JimmyBanks , Sorry, we are not aware about adding 20.04 to this task since we don't manage it.
As I can see, the source code of this task lives in https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/PackerBuildV1/task.json. I think it makes sense to log an issues against this repository.

@JimmyBanks , Sorry, we are not aware about adding 20.04 to this task since we don't manage it.
As I can see, the source code of this task lives in https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/PackerBuildV1/task.json. I think it makes sense to log an issues against this repository.

Ubuntu-20.04 is ready to be the default version for the “ubuntu-latest” label in GitHub Actions and Azure DevOps. This change will be rolled out over a period of several weeks beginning on November, 30. (December, 22 - January, 4 will be a migration break due to holidays)
If you see any issues with your workflows during this transition period:

File an issue in this repository
Switch back to Ubuntu 18.04 by specifying the “ubuntu-18.04” label. We will continue to  support Ubuntu 18.04.

Note that image software between Ubuntu-18.04 and Ubuntu-20.04 differs not only by the pre-installed versions of tools, but also by the default versions of some tools. See the list of missing and changes software below.
Software differences
Tool name	Ubuntu 18.04	Ubuntu 20.04	Notes
AWS CLI	1.18.173	2.0.62	These two versions have major set of breaking changes. See migration guide for details
.NET Core	2.1.x, 3.0.x, 3.1.x	2.1.x, 3.1.x	.NET Core 3.0 was removed (3.0.100, 3.0.101, 3.0.102, 3.0.103). NET Core 3.0 has reached end of life, meaning it is no longer supported and not recommended to use. If you still need it, consider using setup-dotnet and UseNetCore tasks.
Java	7
8(default)
11
12	8
11(default)	If you need to use other versions of Java, consider using setup-java and Java tool installer tasks.
Android	17.0 - 30.0	27.0 - 30.0	Android Platforms and build tools < 27.0 were removed from image. Consider installation in runtime using sdkmanager
Ruby	2.5.1	2.7.0	Default Ruby was changed from 2.5.x to 2.7.x. Consider using setup-ruby and UseRuby tasks.
Ruby toolcache	2.4
2.5
2.6
2.7	2.5
2.6
2.7	Ruby 2.4 will become unavailable via install tasks
Python3	3.6.9	3.8.2	Default Python will be updated from 3.6 to 3.8. Consider using setup-python or UsePython to switch version
PHP	7.1
7.2
7.3
7.4
8.0	7.4
8.0	-
Azure PowerShell	1.0.0, 1.6.0, 2.3.2, 2.6.0, 2.8.0, 3.1.0, 3.5.0, 3.8.0, 4.3.0, 4.4.0, 4.6.0, 4.7.0	4.8.0	-
Boost	1.72.0	-	Boost is not pre-installed on Ubuntu 20.04 image
MySQL	5.7	8.0	See migration guide for more details about breaking changes
SVN	1.9.7	1.13.0	-
Swig	3.0.12	4.0.1	-
libcurl apt package	libcurl3	libcurl4	-
Clang	6
8
9 (default)	8
9
10(default)	-
Missing software
Known issues:

libcurl3 missing in the repo, replaced with libcurl4
Python2 is absent on Ubuntu 20, but required for some packages to install. Can be installed via apt-get install python-is-python2 or via toolcache
Python2 pip should be installed separately(curl https://bootstrap.pypa.io/get-pip.py  --output get-pip.py, python2 get-pip.py)
Ansible should be installed from the official Ubuntu repo, ppa:ansible/ansible isn't updated yet
Set condition in git-lfs installation (Ubuntu 18 & 20 can install git-lfs from Ubuntu repo)
Android SDK should be pointed to Java8 explicitly

Deprecated:
Haskell: https://launchpad.net/~hvr/+archive/ubuntu/ghc-eol

ghc-8.0.2
ghc-8.2.2
ghc-8.4.4
ghc-8.6.2
ghc-8.6.3
ghc-8.6.4
ghc-8.8.1
ghc-8.8.2
cabal-install-2.0
cabal-install-2.2
cabal-install-2.4
cabal-install-3.0

.Net Core
2.2 — EOL December 23, 2019:

2.2.402/dotnet-sdk-2.2.402-linux-x64.tar.gz
2.2.401/dotnet-sdk-2.2.401-linux-x64.tar.gz
2.2.301/dotnet-sdk-2.2.301-linux-x64.tar.gz
2.2.300/dotnet-sdk-2.2.300-linux-x64.tar.gz
2.2.207/dotnet-sdk-2.2.207-linux-x64.tar.gz
2.2.206/dotnet-sdk-2.2.206-linux-x64.tar.gz
2.2.205/dotnet-sdk-2.2.205-linux-x64.tar.gz
2.2.204/dotnet-sdk-2.2.204-linux-x64.tar.gz
2.2.203/dotnet-sdk-2.2.203-linux-x64.tar.gz
2.2.202/dotnet-sdk-2.2.202-linux-x64.tar.gz
2.2.110/dotnet-sdk-2.2.110-linux-x64.tar.gz
2.2.109/dotnet-sdk-2.2.109-linux-x64.tar.gz
2.2.108/dotnet-sdk-2.2.108-linux-x64.tar.gz
2.2.107/dotnet-sdk-2.2.107-linux-x64.tar.gz
2.2.106/dotnet-sdk-2.2.106-linux-x64.tar.gz
2.2.105/dotnet-sdk-2.2.105-linux-x64.tar.gz
2.2.104/dotnet-sdk-2.2.104-linux-x64.tar.gz
2.2.103/dotnet-sdk-2.2.103-linux-x64.tar.gz
2.2.102/dotnet-sdk-2.2.102-linux-x64.tar.gz
2.2.101/dotnet-sdk-2.2.101-linux-x64.tar.gz
2.2.100/dotnet-sdk-2.2.100-linux-x64.tar.gz

3.0 — EOL March 3, 2020:

3.0.103/dotnet-sdk-3.0.103-linux-x64.tar.gz
3.0.102/dotnet-sdk-3.0.102-linux-x64.tar.gz
3.0.101/dotnet-sdk-3.0.101-linux-x64.tar.gz
3.0.100/dotnet-sdk-3.0.100-linux-x64.tar.gz

Azure PowerShell

1.0.0
1.6.0
2.3.2
2.6.0
2.8.0
3.1.0
3.5.0

Each major Go release is supported until there are two newer major releases.  We fix critical problems, including critical security problems, in supported releases as needed by issuing minor revisions
GOLang

Go 1.11,1.12,1.13

Java:

Java 7
Default JDK set to 11

PHP

7.1
7.2
7.3

Android:

"platforms;android-26"
"platforms;android-25"
"platforms;android-24"
"platforms;android-23"
"platforms;android-22"
"platforms;android-21"
"platforms;android-19"
"platforms;android-17"
"build-tools;26.0.3"
"build-tools;26.0.2"
"build-tools;26.0.1"
"build-tools;26.0.0"
"build-tools;25.0.3"
"build-tools;25.0.2"
"build-tools;25.0.1"
"build-tools;25.0.0"
"build-tools;24.0.3"
"build-tools;24.0.2"
"build-tools;24.0.1"
"build-tools;24.0.0"
"build-tools;23.0.3"
"build-tools;23.0.2"
"build-tools;23.0.1"
"build-tools;22.0.1"
"build-tools;21.1.2"
"build-tools;20.0.0"
"build-tools;19.1.0"
"add-ons;addon-google_apis-google-24"
"add-ons;addon-google_apis-google-23"
"add-ons;addon-google_apis-google-22"
"add-ons;addon-google_apis-google-21"
"cmake;3.6.4111459"

Ubuntu-20.04 is ready to be the default version for the “ubuntu-latest” label in GitHub Actions and Azure DevOps. This change will be rolled out over a period of several weeks beginning on November, 30. (December, 22 - January, 4 will be a migration break due to holidays)
If you see any issues with your workflows during this transition period:

File an issue in this repository
Switch back to Ubuntu 18.04 by specifying the “ubuntu-18.04” label. We will continue to  support Ubuntu 18.04.

Note that image software between Ubuntu-18.04 and Ubuntu-20.04 differs not only by the pre-installed versions of tools, but also by the default versions of some tools. See the list of missing and changes software below.
Software differences
Tool name	Ubuntu 18.04	Ubuntu 20.04	Notes
AWS CLI	1.18.173	2.0.62	These two versions have major set of breaking changes. See migration guide for details
.NET Core	2.1.x, 3.0.x, 3.1.x	2.1.x, 3.1.x	.NET Core 3.0 was removed (3.0.100, 3.0.101, 3.0.102, 3.0.103). NET Core 3.0 has reached end of life, meaning it is no longer supported and not recommended to use. If you still need it, consider using setup-dotnet and UseNetCore tasks.
Java	7
8(default)
11
12	8
11(default)	If you need to use other versions of Java, consider using setup-java and Java tool installer tasks.
Android	17.0 - 30.0	27.0 - 30.0	Android Platforms and build tools < 27.0 were removed from image. Consider installation in runtime using sdkmanager
Ruby	2.5.1	2.7.0	Default Ruby was changed from 2.5.x to 2.7.x. Consider using setup-ruby and UseRuby tasks.
Ruby toolcache	2.4
2.5
2.6
2.7	2.5
2.6
2.7	Ruby 2.4 will become unavailable via install tasks
Python3	3.6.9	3.8.2	Default Python will be updated from 3.6 to 3.8. Consider using setup-python or UsePython to switch version
PHP	7.1
7.2
7.3
7.4
8.0	7.4
8.0	-
Azure PowerShell	1.0.0, 1.6.0, 2.3.2, 2.6.0, 2.8.0, 3.1.0, 3.5.0, 3.8.0, 4.3.0, 4.4.0, 4.6.0, 4.7.0	4.8.0	-
Boost	1.72.0	-	Boost is not pre-installed on Ubuntu 20.04 image
MySQL	5.7	8.0	See migration guide for more details about breaking changes
SVN	1.9.7	1.13.0	-
Swig	3.0.12	4.0.1	-
libcurl apt package	libcurl3	libcurl4	-
Clang	6
8
9 (default)	8
9
10(default)	-
Missing software
Known issues:

libcurl3 missing in the repo, replaced with libcurl4
Python2 is absent on Ubuntu 20, but required for some packages to install. Can be installed via apt-get install python-is-python2 or via toolcache
Python2 pip should be installed separately(curl https://bootstrap.pypa.io/get-pip.py  --output get-pip.py, python2 get-pip.py)
Ansible should be installed from the official Ubuntu repo, ppa:ansible/ansible isn't updated yet
Set condition in git-lfs installation (Ubuntu 18 & 20 can install git-lfs from Ubuntu repo)
Android SDK should be pointed to Java8 explicitly

Deprecated:
Haskell: https://launchpad.net/~hvr/+archive/ubuntu/ghc-eol

ghc-8.0.2
ghc-8.2.2
ghc-8.4.4
ghc-8.6.2
ghc-8.6.3
ghc-8.6.4
ghc-8.8.1
ghc-8.8.2
cabal-install-2.0
cabal-install-2.2
cabal-install-2.4
cabal-install-3.0

.Net Core
2.2 — EOL December 23, 2019:

2.2.402/dotnet-sdk-2.2.402-linux-x64.tar.gz
2.2.401/dotnet-sdk-2.2.401-linux-x64.tar.gz
2.2.301/dotnet-sdk-2.2.301-linux-x64.tar.gz
2.2.300/dotnet-sdk-2.2.300-linux-x64.tar.gz
2.2.207/dotnet-sdk-2.2.207-linux-x64.tar.gz
2.2.206/dotnet-sdk-2.2.206-linux-x64.tar.gz
2.2.205/dotnet-sdk-2.2.205-linux-x64.tar.gz
2.2.204/dotnet-sdk-2.2.204-linux-x64.tar.gz
2.2.203/dotnet-sdk-2.2.203-linux-x64.tar.gz
2.2.202/dotnet-sdk-2.2.202-linux-x64.tar.gz
2.2.110/dotnet-sdk-2.2.110-linux-x64.tar.gz
2.2.109/dotnet-sdk-2.2.109-linux-x64.tar.gz
2.2.108/dotnet-sdk-2.2.108-linux-x64.tar.gz
2.2.107/dotnet-sdk-2.2.107-linux-x64.tar.gz
2.2.106/dotnet-sdk-2.2.106-linux-x64.tar.gz
2.2.105/dotnet-sdk-2.2.105-linux-x64.tar.gz
2.2.104/dotnet-sdk-2.2.104-linux-x64.tar.gz
2.2.103/dotnet-sdk-2.2.103-linux-x64.tar.gz
2.2.102/dotnet-sdk-2.2.102-linux-x64.tar.gz
2.2.101/dotnet-sdk-2.2.101-linux-x64.tar.gz
2.2.100/dotnet-sdk-2.2.100-linux-x64.tar.gz

3.0 — EOL March 3, 2020:

3.0.103/dotnet-sdk-3.0.103-linux-x64.tar.gz
3.0.102/dotnet-sdk-3.0.102-linux-x64.tar.gz
3.0.101/dotnet-sdk-3.0.101-linux-x64.tar.gz
3.0.100/dotnet-sdk-3.0.100-linux-x64.tar.gz

Azure PowerShell

1.0.0
1.6.0
2.3.2
2.6.0
2.8.0
3.1.0
3.5.0

Each major Go release is supported until there are two newer major releases.  We fix critical problems, including critical security problems, in supported releases as needed by issuing minor revisions
GOLang

Go 1.11,1.12,1.13

Java:

Java 7
Default JDK set to 11

PHP

7.1
7.2
7.3

Android:

"platforms;android-26"
"platforms;android-25"
"platforms;android-24"
"platforms;android-23"
"platforms;android-22"
"platforms;android-21"
"platforms;android-19"
"platforms;android-17"
"build-tools;26.0.3"
"build-tools;26.0.2"
"build-tools;26.0.1"
"build-tools;26.0.0"
"build-tools;25.0.3"
"build-tools;25.0.2"
"build-tools;25.0.1"
"build-tools;25.0.0"
"build-tools;24.0.3"
"build-tools;24.0.2"
"build-tools;24.0.1"
"build-tools;24.0.0"
"build-tools;23.0.3"
"build-tools;23.0.2"
"build-tools;23.0.1"
"build-tools;22.0.1"
"build-tools;21.1.2"
"build-tools;20.0.0"
"build-tools;19.1.0"
"add-ons;addon-google_apis-google-24"
"add-ons;addon-google_apis-google-23"
"add-ons;addon-google_apis-google-22"
"add-ons;addon-google_apis-google-21"
"cmake;3.6.4111459"

What's the current status?

What's the current status?

after change to Ubuntu-20.04, the go workflow got panic
see https://github.com/ttys3/go-mydumper/runs/1740128264?check_suite_focus=true#step:4:14
revert to the latest tag, everything goes fine
see https://github.com/ttys3/go-mydumper/runs/1740131357?check_suite_focus=true

after change to Ubuntu-20.04, the go workflow got panic
see https://github.com/ttys3/go-mydumper/runs/1740128264?check_suite_focus=true#step:4:14
revert to the latest tag, everything goes fine
see https://github.com/ttys3/go-mydumper/runs/1740131357?check_suite_focus=true

I started seeing:

Version 3.8.7 with arch x64 not found Available versions: 2.7.18 (x64) 3.5.10 (x64) 3.6.12 (x64) 3.7.9 (x64) 3.8.6 (x64) 3.9.1 (x64)

It it unclear why suddenly only the old python version: 3.8.6 is available.

I started seeing:

Version 3.8.7 with arch x64 not found Available versions: 2.7.18 (x64) 3.5.10 (x64) 3.6.12 (x64) 3.7.9 (x64) 3.8.6 (x64) 3.9.1 (x64)

It it unclear why suddenly only the old python version: 3.8.6 is available.

@Sebschock , we had to rollback an image with Python 3.8.7 because of issue with Android NDK.
We will deploy the new image early next week.
I also suggest specifying Python version as 3.8 to make sure that you are not affected by changing minor version

@Sebschock , we had to rollback an image with Python 3.8.7 because of issue with Android NDK.
We will deploy the new image early next week.
I also suggest specifying Python version as 3.8 to make sure that you are not affected by changing minor version

@karfau, we faced with some unexpected capacity allocation issues, so the process might take a bit longer than we expected, but it still in progress.

@karfau, we faced with some unexpected capacity allocation issues, so the process might take a bit longer than we expected, but it still in progress.

Hello,
I would like to kindly request that the documentation at https://github.com/actions/virtual-environments and https://docs.github.com/en/actions/reference/specifications-for-github-hosted-runners be updated to reflect that ubuntu-latest is 20.04 and not 18.04 -- or at least a note that migration is in-progress if the roll-out is not yet complete.
It took me some time to come across this issue and realize the change had been made in our hosted runners.

@ataylorme I will update the docs to indicate that this transition is in progress. We also have docs changes scheduled to go out as soon as the roll out is complete.

I will update the docs to indicate that this transition is in progress

Thank you @skedwards88! The notifications in the workflow logs are great but we have lots of users that copy/paste the example docs, that use ubuntu-latest, and miss the heads up in the logs. People seems to only look at the logs when things fail 😄

Is there a way I can disable the warning for the upgrade?

Hi @minecraftchest1,
warning will be removed automatically when ubuntu-latest for your workflows will start pointing to Ubuntu 20.04. To remove it now, you'll have to specify an exact version of Ubuntu: ubuntu-18.04 or ubuntu-20.04.

Was the ubuntu-latest already switched to 20.04? I can see that in our GA build log, but this issue is not done so confused.

@mareknovotny, we are switching ubuntu-latest gradually to avoid builds queuing. And some customers can be migrated earlier than the other ones.
Issue will be closed when we finish transition for everyone, which is approximately end of February.

This upgrade broke my aws cli commands.
I was getting the following error
<botocore.awsrequest.AWSRequest object at 0x7f644d689630>
Error: Process completed with exit code 255.

I had to do
jobs:
  build:
    runs-on: ubuntu-18.04
``` in order to get it working for the time being

Hi! I was using ubuntu-latest and the build started failing. I noticed Ubuntu had been switched from 18.04 to 20.04 so to test I specified runs-on: ubuntu-18.04. Except the builds are still insisting on using 20.04.

The logs:
##[section]Starting: Request a runner to run this job
Can't find any online and idle self-hosted runner in current repository that matches the required labels: 'ubuntu-latest'
Can't find any online and idle self-hosted runner in current repository's account/organization that matches the required labels: 'ubuntu-latest'
Found online and idle hosted runner in current repository's account/organization that matches the required labels: 'ubuntu-latest'
##[section]Finishing: Request a runner to run this job
Current runner version: '2.277.1'
##[group]Operating System
Ubuntu
20.04.2
LTS
##[endgroup]
##[group]Virtual Environment
Environment: ubuntu-20.04
Version: 20210208.0
Included Software: https://github.com/actions/virtual-environments/blob/ubuntu20/20210208.0/images/linux/Ubuntu2004-README.md
##[endgroup]

I wonder if it's some kind of caching.

Finally :D

Ubuntu-20.04 is ready to be the default version for the “ubuntu-latest” label in GitHub Actions and Azure DevOps. This change will be rolled out over a period of several weeks beginning on November, 30. (December, 22 - January, 4 will be a migration break due to holidays)
If you see any issues with your workflows during this transition period:

File an issue in this repository

Switch back to Ubuntu 18.04 by specifying the “ubuntu-18.04” label. We will continue to  support Ubuntu 18.04.

Note that image software between Ubuntu-18.04 and Ubuntu-20.04 differs not only by the pre-installed versions of tools, but also by the default versions of some tools. See the list of missing and changes software below.
Software differences
|Tool name|Ubuntu 18.04|Ubuntu 20.04|Notes|
|-|:-:|-|-|
|AWS CLI|1.18.173|2.0.62| These two versions have major set of breaking changes. See migration guide for details|
|.NET Core|2.1.x, 3.0.x, 3.1.x|2.1.x, 3.1.x|.NET Core 3.0 was removed (3.0.100, 3.0.101, 3.0.102, 3.0.103). NET Core 3.0 has reached end of life, meaning it is no longer supported and not recommended to use. If you still need it, consider using setup-dotnet and UseNetCore tasks.|
|Java|78(default)1112|811(default)|If you need to use other versions of Java, consider using setup-java and Java tool installer tasks.|
|Android|17.0 - 30.0|27.0 - 30.0|Android Platforms and build tools < 27.0 were removed from image. Consider installation in runtime using sdkmanager|
|Ruby|2.5.1|2.7.0| Default Ruby was changed from 2.5.x to 2.7.x. Consider using setup-ruby and UseRuby tasks.
|Ruby toolcache|<IP_ADDRESS>.7|<IP_ADDRESS>| Ruby 2.4 will become unavailable via install tasks|
|Python3|3.6.9|3.8.2|Default Python will be updated from 3.6 to 3.8. Consider using setup-python or UsePython to switch version|
|PHP|<IP_ADDRESS>.48.0|7.48.0|-|
|Azure PowerShell|1.0.0, 1.6.0, 2.3.2, 2.6.0, 2.8.0, 3.1.0, 3.5.0, 3.8.0, 4.3.0, 4.4.0, 4.6.0, 4.7.0|4.8.0|-|
|Boost|1.72.0|-| Boost is not pre-installed on Ubuntu 20.04 image|
|MySQL|5.7|8.0|See migration guide for more details about breaking changes|
|SVN|1.9.7|1.13.0|-|
|Swig|3.0.12|4.0.1|-|
|libcurl apt package|libcurl3|libcurl4|-|
|Clang |6 8 9 (default)|8 9 10(default)|-|
Missing software
Known issues:

libcurl3 missing in the repo, replaced with libcurl4

Python2 is absent on Ubuntu 20, but required for some packages to install. Can be installed via apt-get install python-is-python2 or via toolcache

Python2 pip should be installed separately(curl https://bootstrap.pypa.io/get-pip.py  --output get-pip.py, python2 get-pip.py)

Ansible should be installed from the official Ubuntu repo, ppa:ansible/ansible isn't updated yet

Set condition in git-lfs installation (Ubuntu 18 & 20 can install git-lfs from Ubuntu repo)

Android SDK should be pointed to Java8 explicitly

Deprecated:
Haskell: https://launchpad.net/~hvr/+archive/ubuntu/ghc-eol

ghc-8.0.2

ghc-8.2.2

ghc-8.4.4

ghc-8.6.2

ghc-8.6.3

ghc-8.6.4

ghc-8.8.1

ghc-8.8.2

cabal-install-2.0

cabal-install-2.2

cabal-install-2.4

cabal-install-3.0

.Net Core
2.2 — EOL December 23, 2019:

2.2.402/dotnet-sdk-2.2.402-linux-x64.tar.gz

2.2.401/dotnet-sdk-2.2.401-linux-x64.tar.gz

2.2.301/dotnet-sdk-2.2.301-linux-x64.tar.gz

2.2.300/dotnet-sdk-2.2.300-linux-x64.tar.gz

2.2.207/dotnet-sdk-2.2.207-linux-x64.tar.gz

2.2.206/dotnet-sdk-2.2.206-linux-x64.tar.gz

2.2.205/dotnet-sdk-2.2.205-linux-x64.tar.gz

2.2.204/dotnet-sdk-2.2.204-linux-x64.tar.gz

2.2.203/dotnet-sdk-2.2.203-linux-x64.tar.gz

2.2.202/dotnet-sdk-2.2.202-linux-x64.tar.gz

2.2.110/dotnet-sdk-2.2.110-linux-x64.tar.gz

2.2.109/dotnet-sdk-2.2.109-linux-x64.tar.gz

2.2.108/dotnet-sdk-2.2.108-linux-x64.tar.gz

2.2.107/dotnet-sdk-2.2.107-linux-x64.tar.gz

2.2.106/dotnet-sdk-2.2.106-linux-x64.tar.gz

2.2.105/dotnet-sdk-2.2.105-linux-x64.tar.gz

2.2.104/dotnet-sdk-2.2.104-linux-x64.tar.gz

2.2.103/dotnet-sdk-2.2.103-linux-x64.tar.gz

2.2.102/dotnet-sdk-2.2.102-linux-x64.tar.gz

2.2.101/dotnet-sdk-2.2.101-linux-x64.tar.gz

2.2.100/dotnet-sdk-2.2.100-linux-x64.tar.gz

3.0 — EOL March 3, 2020:

3.0.103/dotnet-sdk-3.0.103-linux-x64.tar.gz

3.0.102/dotnet-sdk-3.0.102-linux-x64.tar.gz

3.0.101/dotnet-sdk-3.0.101-linux-x64.tar.gz

3.0.100/dotnet-sdk-3.0.100-linux-x64.tar.gz

Azure PowerShell

1.0.0

1.6.0

2.3.2

2.6.0

2.8.0

3.1.0

3.5.0

Each major Go release is supported until there are two newer major releases.  We fix critical problems, including critical security problems, in supported releases as needed by issuing minor revisions
GOLang

Go 1.11,1.12,1.13

Java:

Java 7

Default JDK set to 11

PHP

7.1

7.2

7.3

Android:

"platforms;android-26"

"platforms;android-25"

"platforms;android-24"

"platforms;android-23"

"platforms;android-22"

"platforms;android-21"

"platforms;android-19"

"platforms;android-17"

"build-tools;26.0.3"

"build-tools;26.0.2"

"build-tools;26.0.1"

"build-tools;26.0.0"

"build-tools;25.0.3"

"build-tools;25.0.2"

"build-tools;25.0.1"

"build-tools;25.0.0"

"build-tools;24.0.3"

"build-tools;24.0.2"

"build-tools;24.0.1"

"build-tools;24.0.0"

"build-tools;23.0.3"

"build-tools;23.0.2"

"build-tools;23.0.1"

"build-tools;22.0.1"

"build-tools;21.1.2"

"build-tools;20.0.0"

"build-tools;19.1.0"

"add-ons;addon-google_apis-google-24"

"add-ons;addon-google_apis-google-23"

"add-ons;addon-google_apis-google-22"

"add-ons;addon-google_apis-google-21"

"cmake;3.6.4111459"

FWIW, sshpass seems to be missing by default on 20.04, I had to hotfix one of our actions adding a line to install it with apt.

@carlescufi, we don't pre-install sshpass directly on Ubuntu 18.04 either, it is coming from with ansible package which is different for 18.04 and 20.04.
Please, file a separate issue if you need this package to be installed on Ubuntu 20.04

@carlescufi, we don't pre-install sshpass directly on Ubuntu 18.04 either, it is coming from with ansible package which is different for 18.04 and 20.04.
Please, file a separate issue if you need this package to be installed on Ubuntu 20.04

Thanks for the info. I do not think installing this package by default is sensible, since it doesn't seem to be widely used. Instead, I have resolved the problem in my own workflow. Thanks!

Hi @AlenaSviridenko
I guess this is is open past the originally estimated completion date ( "a period of several weeks beginning on November, 30").
Would it be possible to provide a new estimate for when latest will concretely refer to versions later than 18.04 ?
Thanks!

Hi @wolf99,
unfortunately, due to some infrastructure and capacity issues, the migration process took longer than we expected. Our current estimated time to complete is the March, 20s.
Sorry for inconveniences, and thank you for your patience.

use

For people running into problems listening on port :8084, that's mono-xsp4 #2821, you'll just have to stop/kill it.

Noice

I'm getting a warning pointing to this issue,
Is there any workaround to hide it ?

I'm getting a warning pointing to this issue,
Is there any workaround to hide it ?

@sudo-nautilus you can switch to using ubuntu-20.04 (or ubuntu-18.04 if you dont want to risk upgrading)

I'm getting a warning pointing to this issue,
Is there any workaround to hide it ?

@sudo-nautilus you can switch to using ubuntu-20.04 (or ubuntu-18.04 if you dont want to risk upgrading)

Kk thanks

``

#2897

#2897

@thebeanespinoza83 u what

Update from 18.04 to 20.04 in Azure Pipelines broke our deployment because of missing GLIBC version:
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/site/wwwroot/.python_packages/lib/site-packages/pyodbc.cpython-36m-x86_64-linux-gnu.so)

We deploy Azure Python Functions with Azure Pipelines, using 'ubuntu-latest' build agent. We need to use Python 3.6 because Python ODBC drivers require this version (pip package pyodbc).
The problem can be avoided by using ubuntu-18.04 build agent, but this is of course a temporary fix only.

Hi @lehmus, please consider using Use Python version task to setup the required Python as a default one. List of available Python versions on the image is in Python section of Ubuntu 20.04 readme

@cartazio

Ubuntu-20.04 is ready to be the default version for the “ubuntu-latest” label in GitHub Actions and Azure DevOps. This change will be rolled out over a period of several weeks beginning on November, 30. (December, 22 - January, 4 will be a migration break due to holidays)
If you see any issues with your workflows during this transition period:

File an issue in this repository
Switch back to Ubuntu 18.04 by specifying the “ubuntu-18.04” label. We will continue to  support Ubuntu 18.04.

Note that image software between Ubuntu-18.04 and Ubuntu-20.04 differs not only by the pre-installed versions of tools, but also by the default versions of some tools. See the list of missing and changes software below.
Software differences
Tool name	Ubuntu 18.04	Ubuntu 20.04	Notes
AWS CLI	1.18.173	2.0.62	These two versions have major set of breaking changes. See migration guide for details
.NET Core	2.1.x, 3.0.x, 3.1.x	2.1.x, 3.1.x	.NET Core 3.0 was removed (3.0.100, 3.0.101, 3.0.102, 3.0.103). NET Core 3.0 has reached end of life, meaning it is no longer supported and not recommended to use. If you still need it, consider using setup-dotnet and UseNetCore tasks.
Java	7
8(default)
11
12	8
11(default)	If you need to use other versions of Java, consider using setup-java and Java tool installer tasks.
Android	17.0 - 30.0	27.0 - 30.0	Android Platforms and build tools < 27.0 were removed from image. Consider installation in runtime using sdkmanager
Ruby	2.5.1	2.7.0	Default Ruby was changed from 2.5.x to 2.7.x. Consider using setup-ruby and UseRuby tasks.
Ruby toolcache	2.4
2.5
2.6
2.7	2.5
2.6
2.7	Ruby 2.4 will become unavailable via install tasks
Python3	3.6.9	3.8.2	Default Python will be updated from 3.6 to 3.8. Consider using setup-python or UsePython to switch version
PHP	7.1
7.2
7.3
7.4
8.0	7.4
8.0	-
Azure PowerShell	1.0.0, 1.6.0, 2.3.2, 2.6.0, 2.8.0, 3.1.0, 3.5.0, 3.8.0, 4.3.0, 4.4.0, 4.6.0, 4.7.0	4.8.0	-
Boost	1.72.0	-	Boost is not pre-installed on Ubuntu 20.04 image
MySQL	5.7	8.0	See migration guide for more details about breaking changes
SVN	1.9.7	1.13.0	-
Swig	3.0.12	4.0.1	-
libcurl apt package	libcurl3	libcurl4	-
Clang	6
8
9 (default)	8
9
10(default)	-
Missing software
Known issues:

libcurl3 missing in the repo, replaced with libcurl4
Python2 is absent on Ubuntu 20, but required for some packages to install. Can be installed via apt-get install python-is-python2 or via toolcache
Python2 pip should be installed separately(curl https://bootstrap.pypa.io/get-pip.py  --output get-pip.py, python2 get-pip.py)
Ansible should be installed from the official Ubuntu repo, ppa:ansible/ansible isn't updated yet
Set condition in git-lfs installation (Ubuntu 18 & 20 can install git-lfs from Ubuntu repo)
Android SDK should be pointed to Java8 explicitly

Deprecated:
Haskell: https://launchpad.net/~hvr/+archive/ubuntu/ghc-eol

ghc-8.0.2
ghc-8.2.2
ghc-8.4.4
ghc-8.6.2
ghc-8.6.3
ghc-8.6.4
ghc-8.8.1
ghc-8.8.2
cabal-install-2.0
cabal-install-2.2
cabal-install-2.4
cabal-install-3.0

.Net Core
2.2 — EOL December 23, 2019:

2.2.402/dotnet-sdk-2.2.402-linux-x64.tar.gz
2.2.401/dotnet-sdk-2.2.401-linux-x64.tar.gz
2.2.301/dotnet-sdk-2.2.301-linux-x64.tar.gz
2.2.300/dotnet-sdk-2.2.300-linux-x64.tar.gz
2.2.207/dotnet-sdk-2.2.207-linux-x64.tar.gz
2.2.206/dotnet-sdk-2.2.206-linux-x64.tar.gz
2.2.205/dotnet-sdk-2.2.205-linux-x64.tar.gz
2.2.204/dotnet-sdk-2.2.204-linux-x64.tar.gz
2.2.203/dotnet-sdk-2.2.203-linux-x64.tar.gz
2.2.202/dotnet-sdk-2.2.202-linux-x64.tar.gz
2.2.110/dotnet-sdk-2.2.110-linux-x64.tar.gz
2.2.109/dotnet-sdk-2.2.109-linux-x64.tar.gz
2.2.108/dotnet-sdk-2.2.108-linux-x64.tar.gz
2.2.107/dotnet-sdk-2.2.107-linux-x64.tar.gz
2.2.106/dotnet-sdk-2.2.106-linux-x64.tar.gz
2.2.105/dotnet-sdk-2.2.105-linux-x64.tar.gz
2.2.104/dotnet-sdk-2.2.104-linux-x64.tar.gz
2.2.103/dotnet-sdk-2.2.103-linux-x64.tar.gz
2.2.102/dotnet-sdk-2.2.102-linux-x64.tar.gz
2.2.101/dotnet-sdk-2.2.101-linux-x64.tar.gz
2.2.100/dotnet-sdk-2.2.100-linux-x64.tar.gz

3.0 — EOL March 3, 2020:

3.0.103/dotnet-sdk-3.0.103-linux-x64.tar.gz
3.0.102/dotnet-sdk-3.0.102-linux-x64.tar.gz
3.0.101/dotnet-sdk-3.0.101-linux-x64.tar.gz
3.0.100/dotnet-sdk-3.0.100-linux-x64.tar.gz

Azure PowerShell

1.0.0
1.6.0
2.3.2
2.6.0
2.8.0
3.1.0
3.5.0

Each major Go release is supported until there are two newer major releases.  We fix critical problems, including critical security problems, in supported releases as needed by issuing minor revisions
GOLang

Go 1.11,1.12,1.13

Java:

Java 7
Default JDK set to 11

PHP

7.1
7.2
7.3

Android:

"platforms;android-26"
"platforms;android-25"
"platforms;android-24"
"platforms;android-23"
"platforms;android-22"
"platforms;android-21"
"platforms;android-19"
"platforms;android-17"
"build-tools;26.0.3"
"build-tools;26.0.2"
"build-tools;26.0.1"
"build-tools;26.0.0"
"build-tools;25.0.3"
"build-tools;25.0.2"
"build-tools;25.0.1"
"build-tools;25.0.0"
"build-tools;24.0.3"
"build-tools;24.0.2"
"build-tools;24.0.1"
"build-tools;24.0.0"
"build-tools;23.0.3"
"build-tools;23.0.2"
"build-tools;23.0.1"
"build-tools;22.0.1"
"build-tools;21.1.2"
"build-tools;20.0.0"
"build-tools;19.1.0"
"add-ons;addon-google_apis-google-24"
"add-ons;addon-google_apis-google-23"
"add-ons;addon-google_apis-google-22"
"add-ons;addon-google_apis-google-21"
"cmake;3.6.4111459"

Just to add that
* Python2 is absent on Ubuntu 20, but required for some packages to install. Can be installed via apt-get install python-is-python2 or via toolcache
* Python2 pip should be installed separately(curl https://bootstrap.pypa.io/get-pip.py --output get-pip.py, python2 get-pip.py)

The Python2 pip instructions aren't correct, for starters curl https://bootstrap.pypa.io/get-pip.py --output get-pip.py, python2 get-pip.py is an invalid command, and if you do:
curl https://bootstrap.pypa.io/get-pip.py --output get-pip.py

And then
python2 get-pip.py

You receive:
ERROR: This script does not work on Python 2.7 The minimum supported Python version is 3.6. Please use https://bootstrap.pypa.io/pip/2.7/get-pip.py instead.

This command fails with the following error on ubuntu-latest, I had to specify ubuntu-18.04 to get it to work again.
aws s3 sync _site s3://my-s3-bucket --delete
<botocore.awsrequest.AWSRequest object at 0x7fce9b685040> Error: Process completed with exit code 255

image](https://user-images.githubusercontent.com/61645258/111494435-85176080-874f-11eb-9c10-690866185086.jpeg)

image](https://user-images.githubusercontent.com/61645258/111494435-85176080-874f-11eb-9c10-690866185086.jpeg)

What is that about?

nnoo ideaa ¯_(ツ)_/¯

Hello everyone!
Migration has been finished and currently, all ubuntu-latest builds are using ubuntu-20.04.

Nice.

Hello everyone!
Migration has been finished and currently, all ubuntu-latest builds are using ubuntu-20.04.

Awesome! Will check it out!

This command fails with the following error on ubuntu-latest, I had to specify ubuntu-18.04 to get it to work again.
aws s3 sync _site s3://my-s3-bucket --delete
<botocore.awsrequest.AWSRequest object at 0x7fce9b685040> Error: Process completed with exit code 255
EDIT: let me know if I should open a new issue for this instead of commenting here. Thanks!

Hi @karissademi, here is a solution I found that doesn't require you to specify the AWS region (many others involve that): https://github.com/aws/aws-cli/issues/5623#issuecomment-801240811
Hope it helps

FRISSÍTÉS: Az áttelepítés befejeződött, és az összes ubuntu-latestverzió az Ubuntu 20.04-et használja
Az Ubuntu-20.04 készen áll az „ubuntu-latest” címke alapértelmezett verziójának a GitHub Actions és az Azure DevOps alkalmazásban. Ez a változás több hetes időszakban kerül bevezetésre november 30-tól kezdődően. (December 22. és január 4. között az ünnepek miatt migrációs szünet lesz)
Ha problémát észlel a munkafolyamatokkal ebben az átmeneti időszakban:

Nyújtson be egy problémát ebben a tárban
Váltson vissza az Ubuntu 18.04-re az „ubuntu-18.04” címke megadásával. Továbbra is támogatjuk az Ubuntu 18.04-et.

Ne feledje, hogy az Ubuntu-18.04 és az Ubuntu-20.04 közötti képszoftver nemcsak az eszközök előre telepített verzióival, hanem egyes eszközök alapértelmezett verzióival is különbözik. Lásd az alábbi hiányzó és módosított szoftverek listáját.
Szoftverbeli különbségek
Eszköz neve	Ubuntu 18.04	Ubuntu 20.04	Megjegyzések
AWS CLI	1.18.173	2.0.62	Ennek a két változatnak számos áttörő változása van. A részletekért lásd az átállási útmutatót
.NET Core	2.1.x, 3.0.x, 3.1.x	2.1.x, 3.1.x	A .NET Core 3.0 eltávolításra került (3.0.100, 3.0.101, 3.0.102, 3.0.103). A NET Core 3.0 elérte az élettartama végét, vagyis már nem támogatott és nem ajánlott használni. Ha még mindig szüksége van rá, fontolja meg a setup- dotnet és a UseNetCore feladatok használatát.
Jáva	7
8 (alapértelmezett)
11
12	8
11 (alapértelmezett)	Ha a Java más verzióit kell használnia, fontolja meg a setup-java és a Java eszköz telepítő feladatainak használatát.
Android	17,0 - 30,0	27,0 - 30,0	Az Android platformokat és a buildeszközöket <27.0 eltávolították a képről. Fontolja meg a futás közbeni telepítést az sdkmanager használatával
Rubin	2.5.1	2.7.0	Az alapértelmezett Ruby-t 2.5.x-ről 2.7.x-re változtatták. Fontolja meg a setup-ruby és a UseRuby feladatok használatát.
Rubin szerszámtár	2,4
2,5
2,6
2,7	2,5
2,6
2,7	A Ruby 2.4 telepítési feladatok révén nem lesz elérhető
Python3	3.6.9	3.8.2	Az alapértelmezett Python 3.6-ról 3.8-ra frissül. Fontolja meg a setup-python vagy a UsePython használatát a verzióváltáshoz
PHP	7,1
7,2
7,3
7,4
8,0	7,4
8,0	-
Azure PowerShell	1.0.0, 1.6.0, 2.3.2, 2.6.0, 2.8.0, 3.1.0, 3.5.0, 3.8.0, 4.3.0, 4.4.0, 4.6.0, 4.7.0	4.8.0	-
Boost	1.72.0	-	A Boost nincs előre telepítve az Ubuntu 20.04 képre
MySQL	5.7	8.0	A változások megtörésével kapcsolatos további részletekért lásd az átállási útmutatót
SVN	1.9.7	1.13.0	-
Vedel	3.0.12	4.0.1	-
libcurl apt csomag	libcurl3	libcurl4	-
Csengés	6
8
9 (alapértelmezett)	8
9
10 (alapértelmezett)	-
Hiányzik a szoftver
Ismert problémák:

libcurl3 hiányzik a repóból, helyette: libcurl4
Python2hiányzik az Ubuntu 20-ból, de néhány csomag telepítéséhez szükséges. Telepíthető apt-get install python-is-python2eszközzáron keresztül vagy eszközzár segítségével
A Python2 pipet külön kell telepíteni ( curl https://bootstrap.pypa.io/get-pip.py  --output get-pip.py, python2 get-pip.py)
Az Ansible programot a hivatalos Ubuntu repóból kell telepíteni, ppa:ansible/ansiblemég nincs frissítve
Feltétel beállítása a git-lfs telepítésében (az Ubuntu 18 és 20 telepítheti a git-lfs-t az Ubuntu repo-ból)
Az Android SDK-t kifejezetten a Java8-ra kell mutatni

Elavult:
**Haskell: ** https://launchpad.net/~hvr/+archive/ubuntu/ghc-eol

ghc-8.0.2
ghc-8.2.2
ghc-8.4.4
ghc-8.6.2
ghc-8.6.3
ghc-8.6.4
ghc-8.8.1
ghc-8.8.2
cabal-install-2.0
cabal-install-2.2
cabal-install-2.4
cabal-install-3.0

.Net Core
2.2 — EOL December 23, 2019:

2.2.402/dotnet-sdk-2.2.402-linux-x64.tar.gz
2.2.401/dotnet-sdk-2.2.401-linux-x64.tar.gz
2.2.301/dotnet-sdk-2.2.301-linux-x64.tar.gz
2.2.300/dotnet-sdk-2.2.300-linux-x64.tar.gz
2.2.207/dotnet-sdk-2.2.207-linux-x64.tar.gz
2.2.206/dotnet-sdk-2.2.206-linux-x64.tar.gz
2.2.205/dotnet-sdk-2.2.205-linux-x64.tar.gz
2.2.204/dotnet-sdk-2.2.204-linux-x64.tar.gz
2.2.203/dotnet-sdk-2.2.203-linux-x64.tar.gz
2.2.202/dotnet-sdk-2.2.202-linux-x64.tar.gz
2.2.110/dotnet-sdk-2.2.110-linux-x64.tar.gz
2.2.109/dotnet-sdk-2.2.109-linux-x64.tar.gz
2.2.108/dotnet-sdk-2.2.108-linux-x64.tar.gz
2.2.107/dotnet-sdk-2.2.107-linux-x64.tar.gz
2.2.106/dotnet-sdk-2.2.106-linux-x64.tar.gz
2.2.105/dotnet-sdk-2.2.105-linux-x64.tar.gz
2.2.104/dotnet-sdk-2.2.104-linux-x64.tar.gz
2.2.103/dotnet-sdk-2.2.103-linux-x64.tar.gz
2.2.102/dotnet-sdk-2.2.102-linux-x64.tar.gz
2.2.101/dotnet-sdk-2.2.101-linux-x64.tar.gz
2.2.100/dotnet-sdk-2.2.100-linux-x64.tar.gz

3.0 — EOL March 3, 2020:

3.0.103/dotnet-sdk-3.0.103-linux-x64.tar.gz
3.0.102/dotnet-sdk-3.0.102-linux-x64.tar.gz
3.0.101/dotnet-sdk-3.0.101-linux-x64.tar.gz
3.0.100/dotnet-sdk-3.0.100-linux-x64.tar.gz

Azure PowerShell

1.0.0
1.6.0
2.3.2
2.6.0
2.8.0
3.1.0
3.5.0

Each major Go release is supported until there are two newer major releases.  We fix critical problems, including critical security problems, in supported releases as needed by issuing minor revisions
GOLang

Go 1.11,1.12,1.13

Java:

Java 7
Default JDK set to 11

PHP

7.1
7.2
7.3

Android:

"platforms;android-26"
"platforms;android-25"
"platforms;android-24"
"platforms;android-23"
"platforms;android-22"
"platforms;android-21"
"platforms;android-19"
"platforms;android-17"
"build-tools;26.0.3"
"build-tools;26.0.2"
"build-tools;26.0.1"
"build-tools;26.0.0"
"build-tools;25.0.3"
"build-tools;25.0.2"
"build-tools;25.0.1"
"build-tools;25.0.0"
"build-tools;24.0.3"
"build-tools;24.0.2"
"build-tools;24.0.1"
"build-tools;24.0.0"
"build-tools;23.0.3"
"build-tools;23.0.2"
"build-tools;23.0.1"
"build-tools;22.0.1"
"build-tools;21.1.2"
"build-tools;20.0.0"
"build-tools;19.1.0"
"add-ons;addon-google_apis-google-24"
"add-ons;addon-google_apis-google-23"
"add-ons;addon-google_apis-google-22"
"add-ons;addon-google_apis-google-21"
"cmake;3.6.4111459"

UPDATE: Migration has been finished and all ubuntu-latest builds are using Ubuntu 20.04
Ubuntu-20.04 is ready to be the default version for the “ubuntu-latest” label in GitHub Actions and Azure DevOps. This change will be rolled out over a period of several weeks beginning on November, 30. (December, 22 - January, 4 will be a migration break due to holidays)
If you see any issues with your workflows during this transition period:

File an issue in this repository
Switch back to Ubuntu 18.04 by specifying the “ubuntu-18.04” label. We will continue to  support Ubuntu 18.04.

Note that image software between Ubuntu-18.04 and Ubuntu-20.04 differs not only by the pre-installed versions of tools, but also by the default versions of some tools. See the list of missing and changes software below.
Software differences
Tool name	Ubuntu 18.04	Ubuntu 20.04	Notes
AWS CLI	1.18.173	2.0.62	These two versions have major set of breaking changes. See migration guide for details
.NET Core	2.1.x, 3.0.x, 3.1.x	2.1.x, 3.1.x	.NET Core 3.0 was removed (3.0.100, 3.0.101, 3.0.102, 3.0.103). NET Core 3.0 has reached end of life, meaning it is no longer supported and not recommended to use. If you still need it, consider using setup-dotnet and UseNetCore tasks.
Java	7
8(default)
11
12	8
11(default)	If you need to use other versions of Java, consider using setup-java and Java tool installer tasks.
Android	17.0 - 30.0	27.0 - 30.0	Android Platforms and build tools < 27.0 were removed from image. Consider installation in runtime using sdkmanager
Ruby	2.5.1	2.7.0	Default Ruby was changed from 2.5.x to 2.7.x. Consider using setup-ruby and UseRuby tasks.
Ruby toolcache	2.4
2.5
2.6
2.7	2.5
2.6
2.7	Ruby 2.4 will become unavailable via install tasks
Python3	3.6.9	3.8.2	Default Python will be updated from 3.6 to 3.8. Consider using setup-python or UsePython to switch version
PHP	7.1
7.2
7.3
7.4
8.0	7.4
8.0	-
Azure PowerShell	1.0.0, 1.6.0, 2.3.2, 2.6.0, 2.8.0, 3.1.0, 3.5.0, 3.8.0, 4.3.0, 4.4.0, 4.6.0, 4.7.0	4.8.0	-
Boost	1.72.0	-	Boost is not pre-installed on Ubuntu 20.04 image
MySQL	5.7	8.0	See migration guide for more details about breaking changes
SVN	1.9.7	1.13.0	-
Swig	3.0.12	4.0.1	-
libcurl apt package	libcurl3	libcurl4	-
Clang	6
8
9 (default)	8
9
10(default)	-
Missing software
Known issues:

libcurl3 missing in the repo, replaced with libcurl4
Python2 is absent on Ubuntu 20, but required for some packages to install. Can be installed via apt-get install python-is-python2 or via toolcache
Python2 pip should be installed separately(curl https://bootstrap.pypa.io/get-pip.py  --output get-pip.py, python2 get-pip.py)
Ansible should be installed from the official Ubuntu repo, ppa:ansible/ansible isn't updated yet
Set condition in git-lfs installation (Ubuntu 18 & 20 can install git-lfs from Ubuntu repo)
Android SDK should be pointed to Java8 explicitly

Deprecated:
Haskell: https://launchpad.net/~hvr/+archive/ubuntu/ghc-eol

ghc-8.0.2
ghc-8.2.2
ghc-8.4.4
ghc-8.6.2
ghc-8.6.3
ghc-8.6.4
ghc-8.8.1
ghc-8.8.2
cabal-install-2.0
cabal-install-2.2
cabal-install-2.4
cabal-install-3.0

.Net Core
2.2 — EOL December 23, 2019:

2.2.402/dotnet-sdk-2.2.402-linux-x64.tar.gz
2.2.401/dotnet-sdk-2.2.401-linux-x64.tar.gz
2.2.301/dotnet-sdk-2.2.301-linux-x64.tar.gz
2.2.300/dotnet-sdk-2.2.300-linux-x64.tar.gz
2.2.207/dotnet-sdk-2.2.207-linux-x64.tar.gz
2.2.206/dotnet-sdk-2.2.206-linux-x64.tar.gz
2.2.205/dotnet-sdk-2.2.205-linux-x64.tar.gz
2.2.204/dotnet-sdk-2.2.204-linux-x64.tar.gz
2.2.203/dotnet-sdk-2.2.203-linux-x64.tar.gz
2.2.202/dotnet-sdk-2.2.202-linux-x64.tar.gz
2.2.110/dotnet-sdk-2.2.110-linux-x64.tar.gz
2.2.109/dotnet-sdk-2.2.109-linux-x64.tar.gz
2.2.108/dotnet-sdk-2.2.108-linux-x64.tar.gz
2.2.107/dotnet-sdk-2.2.107-linux-x64.tar.gz
2.2.106/dotnet-sdk-2.2.106-linux-x64.tar.gz
2.2.105/dotnet-sdk-2.2.105-linux-x64.tar.gz
2.2.104/dotnet-sdk-2.2.104-linux-x64.tar.gz
2.2.103/dotnet-sdk-2.2.103-linux-x64.tar.gz
2.2.102/dotnet-sdk-2.2.102-linux-x64.tar.gz
2.2.101/dotnet-sdk-2.2.101-linux-x64.tar.gz
2.2.100/dotnet-sdk-2.2.100-linux-x64.tar.gz

3.0 — EOL March 3, 2020:

3.0.103/dotnet-sdk-3.0.103-linux-x64.tar.gz
3.0.102/dotnet-sdk-3.0.102-linux-x64.tar.gz
3.0.101/dotnet-sdk-3.0.101-linux-x64.tar.gz
3.0.100/dotnet-sdk-3.0.100-linux-x64.tar.gz

Azure PowerShell

1.0.0
1.6.0
2.3.2
2.6.0
2.8.0
3.1.0
3.5.0

Each major Go release is supported until there are two newer major releases.  We fix critical problems, including critical security problems, in supported releases as needed by issuing minor revisions
GOLang

Go 1.11,1.12,1.13

Java:

Java 7
Default JDK set to 11

PHP

7.1
7.2
7.3

Android:

"platforms;android-26"
"platforms;android-25"
"platforms;android-24"
"platforms;android-23"
"platforms;android-22"
"platforms;android-21"
"platforms;android-19"
"platforms;android-17"
"build-tools;26.0.3"
"build-tools;26.0.2"
"build-tools;26.0.1"
"build-tools;26.0.0"
"build-tools;25.0.3"
"build-tools;25.0.2"
"build-tools;25.0.1"
"build-tools;25.0.0"
"build-tools;24.0.3"
"build-tools;24.0.2"
"build-tools;24.0.1"
"build-tools;24.0.0"
"build-tools;23.0.3"
"build-tools;23.0.2"
"build-tools;23.0.1"
"build-tools;22.0.1"
"build-tools;21.1.2"
"build-tools;20.0.0"
"build-tools;19.1.0"
"add-ons;addon-google_apis-google-24"
"add-ons;addon-google_apis-google-23"
"add-ons;addon-google_apis-google-22"
"add-ons;addon-google_apis-google-21"
"cmake;3.6.4111459"

Payment method

How do I get a post-deployment command to run on ubuntu-latest? The one in question is:
sudo ln -s /usr/bin/python3 /usr/bin/python
need python to run as many node libraries are using python instead of python3.
Can someone please assist here in updating the Github workflow? Thank you

How do I get a post-deployment command to run on ubuntu-latest? The one in question is:
sudo ln -s /usr/bin/python3 /usr/bin/python
need python to run as many node libraries are using python instead of python3.
Can someone please assist here in updating the Github workflow? Thank you

We already have this link - /usr/bin/python -> python3
lrwxrwxrwx 1 root root [7](https://github.com/roasted-eggplant/al-cheb-test/runs/5317095463?check_suite_focus=true#step:2:7) Apr 15  2020 /usr/bin/python -> python3
lrwxrwxrwx 1 root root 9 Mar 13  2020 /usr/bin/python3 -> python3.[8](https://github.com/roasted-eggplant/al-cheb-test/runs/5317095463?check_suite_focus=true#step:2:8)
Python 3.8.10

How do I get a post-deployment command to run on ubuntu-latest? The one in question is:
sudo ln -s /usr/bin/python3 /usr/bin/python
need python to run as many node libraries are using python instead of python3.
Can someone please assist here in updating the Github workflow? Thank you

We already have this link - /usr/bin/python -> python3
lrwxrwxrwx 1 root root [7]Apr 15  2020 /usr/bin/python -> python3
lrwxrwxrwx 1 root root 9 Mar 13  2020 /usr/bin/python3 -> python3.[8]
Python 3.8.10

Hi thank you for such a prompt reply but the following is what I am getting after deploying ubuntu-latest. After each deploy we are running the syslink command manually to have python
root@b2f9df891886:~# python
-bash: python: command not found

root@b2f9df891886:~# whereis python
python: /usr/bin/python3.7 /usr/bin/python3.7m /usr/lib/python3.7 /usr/lib/python2.7 /etc/python3.7 /usr/local/lib/python3.7

How do I get a post-deployment command to run on ubuntu-latest? The one in question is:
sudo ln -s /usr/bin/python3 /usr/bin/python
need python to run as many node libraries are using python instead of python3.
Can someone please assist here in updating the Github workflow? Thank you

We already have this link - /usr/bin/python -> python3
lrwxrwxrwx 1 root root [7]Apr 15  2020 /usr/bin/python -> python3
lrwxrwxrwx 1 root root 9 Mar 13  2020 /usr/bin/python3 -> python3.[8]
Python 3.8.10

Hi thank you for such a prompt reply but the following is what I am getting after deploying ubuntu-latest. After each deploy we are running the syslink command manually to have python
root@b2f9df891886:~# python
-bash: python: command not found

root@b2f9df891886:~# whereis python
python: /usr/bin/python3.7 /usr/bin/python3.7m /usr/lib/python3.7 /usr/lib/python2.7 /etc/python3.7 /usr/local/lib/python3.7

You should use the main branch to build your own images. This symlink is a part of python-is-python3 package which is installed during basic.sh:
~$ dpkg -S /usr/bin/python
python-is-python3: /usr/bin/python

https://github.visualstudio.com/virtual-environments/_build/results?buildId=123034&view=logs&j=011e1ec8-6569-5e69-4f06-baf193d1351e&t=5431112d-2b61-5a5f-7042-ef698f761043 (line 2908 -  azure-arm: Install python-is-python3)

@al-cheb, thanks you again for the prompt reply and shared links. I want to mention that we are not using Azure DevOps but Github actions. The folloiwng is my workflow code, pretty standard except I added python-is-python3 and update-alternatives to install syslink /usr/bin/python
name: Build and deploy Node.js project to Azure Function App

on:
  push:
    branches:
      - main
  workflow_dispatch:

env:
  AZURE_FUNCTIONAPP_PACKAGE_PATH: '.' # set this to the path to your web app project, defaults to the repository root
  NODE_VERSION: '14.x' # set this to the node version to use (supports 8.x, 10.x, 12.x)

jobs:
  build-and-deploy:
    runs-on: ubuntu-latest
    steps:
      - name: 'Checkout GitHub Action'
        uses: actions/checkout@v2

      - name: Setup Node ${{ env.NODE_VERSION }} Environment
        uses: actions/setup-node@v1
        with:
          node-version: ${{ env.NODE_VERSION }}

      - name: Set up Python
        uses: actions/setup-python@v2
        with:
          python-version: '3.x'

      - name: 'Install python syslink'
        shell: bash
        run: |
          sudo apt-get install python-is-python3
          sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 10

Even though the deployment is done successfully I am not having python available in /usr/bin
https://imgur.com/a/HY7LHbQ

@WiredEntrepreneur,
If you use setup-python task it adds a path where is python stored: /opt/hostedtoolcache/Python/3.10.2/x64/bin

@al-cheb I just checked, I have package python-is-python3 but /usr/bin/python is missing. I didn't totally get your previous post but please can you let me know what needs to be changed in the workflow file to get /usr/bin/python and also we need this pointed to python3
Thank you

@WiredEntrepreneur a few notes:

setup-python action changes the PATH so the python is used from the /opt/hostedtoolcache/Python/<version>/x64/bin directory
python-is-python3 is a package for the system python and not compatible with the Python from the setup-python action

You can use python and python3 directly after using the setup-python action:
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - name: Set up Python
        uses: actions/setup-python@v2
        with:
          python-version: '3.10'

      - name: 'Check Python'
        shell: bash
        run: |
          python --version
          python3 --version


shader

can you please share the shader on example video?

can you please share the shader on example video?
shure @muveso, here you go
ExplosionWithGradients.zip


pomoplus: increase size of fonts and buttons

for legibility and ease of use.
Changes made primarily for the Bangle.js 2. I haven't run them on an actual Bangle.js 1 watch - only the emulator. The update can be tried here (please report back if you try!): https://thyttan.github.io/BangleApps/?id=pomoplus
@bruceblore @notEvil thoughts?
Edit: After measuring ram use it think it still fits on the Bangle.js 1.

Unrelated to this, I noticed that I don't know what pomoplus is and what it should be doing. Adding README would be quite welcome.

I tried it on Bjs1 using the emulator and looks good to me, with const SCALING = W/g.getWidth().

I tried it on Bjs1 using the emulator and looks good to me, with const SCALING = W/g.getWidth().

That will undo the scaling though - it will evaluate to 1 and not do anything. Did it not look good with = W/176?

True, silly me. Didn't know what its supposed to look like and preferred a little more spacing between things. But thats just a matter of taste, don't feel obliged to change, especially because I'm bad at visual design in general :)

Thanks @pavelmachek and @notEvil for your feedback. I'll merge this now.


About the operation of coo_matrix

Hi,
I found there is an operation to build the symmetric adjacency matrix as adj = adj + adj.T.multiply(adj.T > adj) - adj.multiply(adj.T > adj)
I have no ideas about what adj.T>adj means. Would you mind having some words on it?
Thanks!

Besides, I don't know the reason of building the symmetric adjacency matrix. In Cora's cites file, (entity1, entity2) means that entity1 is cited by entity2, but entity2 may not be cited by entity1.

adj = adj + adj.T.multiply(adj.T > adj) - adj.multiply(adj.T > adj) is same to adj = adj.maximum(adj.T)


More gas giant icons/ fully customizable icons

What do you think is missing or what do you think can be done better
basically, I think there should be more colors of gas giant and/or fully customizable icons. my reasoning for the gas giant icons is that people might want to make a gas giant of a specific color that does not exist in the current pallet. say: green. I know green isn't realistic, but there is another option aside from ignoring me entirely.
fully customizable icons would allow players to fully customize their universe. as long as they can make pixel art, they can use a fully customizable icon system. or, you could allow for both AR icons and fully custom icons.

There's this magic thing called reading the wiki thoroughly, which would answer your proposition quite well were you to actually attempt it. Please make sure to do so before making issues such as this one again.

understandable. have a nice day.


Update developer docs

Document the new form of the state space, the backward induction and the simulation procedure. Introduce the changes due to numba and model extensions types and kids as version 0.2

I do not think this is needed, right? If not, please just close.


--skip-init-end-tasks doesn't seem to work

Describe The Bug
With tasks.init defined, even if we call cargo make --skip-init-end-tasks empty, the init task will be called.
I am not sure if I am understanding the --skip-init-end-tasks argument incorrectly, or there is a bug. If it's a misunderstanding, I believe we should change the documentation for the --skip-init-end-tasks argument: "If set, init and end tasks are skipped". If it's a bug, we need a fix.
To Reproduce
On Linux with bash:
cargo init hello-world && cd hello-world && echo "tasks.init.script = \"echo init\"" > Makefile.toml && cargo make empty --skip-init-end-tasks

The actual output is:
$ cargo init hello-world && cd hello-world && echo "tasks.init.script = \"echo init\"" > Makefile.toml && cargo make empty --skip-init-end-tasks
    Creating binary (application) package
note: see more `Cargo.toml` keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[cargo-make] INFO - cargo make 0.37.13
[cargo-make] INFO - Calling cargo metadata to extract project info
[cargo-make] INFO - Cargo metadata done
[cargo-make] INFO - Project: hello-world
[cargo-make] INFO - Build File: Makefile.toml
[cargo-make] INFO - Task: empty
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Running Task: init
init
[cargo-make] INFO - Build Done in 0.23 seconds.

I guess we are not supposed to see the "Running Task: init" log and the "init" echo?
Error Stack
N/A
Code Sample
tasks.init.script = "echo init"

This problem is important to me, as I plan to use the init task to add "-D warning" to the RUSTFLAGS environement variable for the CI environment. However, ff --skip-init-end-tasks doesn't work, the init task will be run another time when a new cargo-make process is forked due to tasks.<task_id>.run_task.fork being true. As a result, 2 duplicate "-D warnings" will be added to RUSTFLAGS, and cause recompilation.

instead of
cargo make empty --skip-init-end-tasks
do
cargo make --skip-init-end-tasks empty

instead of cargo make empty --skip-init-end-tasks do cargo make --skip-init-end-tasks empty

The same:
$ cargo init hello-world && cd hello-world && echo "tasks.init.script = \"echo init\"" > Makefile.toml && cargo make --skip-init-end-tasks empty
    Creating binary (application) package
note: see more `Cargo.toml` keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[cargo-make] INFO - cargo make 0.37.13
[cargo-make] INFO - Calling cargo metadata to extract project info
[cargo-make] INFO - Cargo metadata done
[cargo-make] INFO - Project: hello-world
[cargo-make] INFO - Build File: Makefile.toml
[cargo-make] INFO - Task: empty
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Running Task: init
init
[cargo-make] INFO - Build Done in 0.28 seconds.

A hacky patch works:
~/src/cargo-make$ git diff
diff --git a/src/lib/runner.rs b/src/lib/runner.rs
index c774314a..0f3d5d12 100755
--- a/src/lib/runner.rs
+++ b/src/lib/runner.rs
@@ -629,6 +629,14 @@ pub(crate) fn run(
         },
         None => None,
     };
+    let config = if cli_args.skip_init_end_tasks {
+        let mut config = config;
+        config.config.init_task = None;
+        config.config.end_task = None;
+        config
+    } else {
+        config
+    };

     let flow_info = FlowInfo {
         config,
~/src/cargo-make$ cargo run --bin makers -- --makefile /tmp/hello-world/Makefile.toml empty
   Compiling cargo-make v0.37.13 (/home/user/src/cargo-make)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 4.09s
     Running `target/debug/makers --makefile /tmp/hello-world/Makefile.toml empty`
[cargo-make] INFO - makers 0.37.13
[cargo-make] INFO - Calling cargo metadata to extract project info
[cargo-make] INFO - Cargo metadata done
[cargo-make] INFO - Project: cargo-make
[cargo-make] INFO - Build File: /tmp/hello-world/Makefile.toml
[cargo-make] INFO - Task: empty
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Running Task: init
init
[cargo-make] INFO - Build Done in 0.50 seconds.
~/src/cargo-make$ cargo run --bin makers -- --makefile /tmp/hello-world/Makefile.toml --skip-init-end-tasks empty
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.09s
     Running `target/debug/makers --makefile /tmp/hello-world/Makefile.toml --skip-init-end-tasks empty`
[cargo-make] INFO - makers 0.37.13
[cargo-make] INFO - Calling cargo metadata to extract project info
[cargo-make] INFO - Cargo metadata done
[cargo-make] INFO - Project: cargo-make
[cargo-make] INFO - Build File: /tmp/hello-world/Makefile.toml
[cargo-make] INFO - Task: empty
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Build Done in 0.57 seconds.

hmmm... seems like a bug. i'll check it out.

In case you miss it, I have uploaded a PR(#1109) to fix this issue. PTAL.

thanks and sorry for the delay


Hwang fails with "no CUDA-capable device is detected"

On a GCE box with P100 and 390.30 driver. Ran the face detection pipeline on both the cuda8 and cuda9 Scanner docker images with nvidia-docker2.


Quotes are displayed as HTML entities

Seen on https://ada-lang.io/docs/style-guide/s5/04
   function "=" (Left, Right : Object) return Boolean;  -- element-by-element comparison

I just noticed that the problem was in the Wikibooks source. I've fixed just now there, so it will be fixed here when running again the translator.


fix an error occurred in release mode

Coverage remained the same at 67.793% when pulling b0fc2bb1476582cb0764f926ce86f9e8a55d79b6 on yingjunwu:quick_fix into 48f515127d7458bf055b43d2441686273f65869a on cmu-db:master.


Add section collapse functionality

WIP #1686
screen_recording_livebook_collapse_section.webm
Is this heading in the right direction?
Not sure about the "Expand all" and "Collapse all" buttons..

@jannikbecher this looks like a great starting point. We can tackle the collapse and expand all in another pull request. Two things:

UI wise, the starting of each section needs to be aligned with the title. So we want to have the collapse button "outside". Something like this:

We can add a note with how many cells were hidden

@jonatanklosko do you think this should be fully handled client side? I guess we can add a class when collapsing and then remove it. We change the content accordingly based on the presence of said class?

@jonatanklosko do you think this should be fully handled client side?

Yeah, one option would be adding a class to section and some conditional rules (as we do in js_interop.css). Should also be doable with JS commands and I don't have a strong preference, but probably less brittle with conditional CSS than updating individual elements.

Ahh I see. I completely  misused LiveView functionality here. I will come up with a solution the next days using js_interop.css as @jonatanklosko described :)

Unfortunately I'm really struggling with the alignment. Is it even possible to align it probably when the expand/collapse buttons are defined in section_component.ex?
I removed the collapse/expand all functionality for now. Any preference on how the buttons should look like?

I made some progress regarding the alignment :)

@jannikbecher awesome! I moved the button closer to the title and made it hidden unless collapsed or hovered :)
https://user-images.githubusercontent.com/17034772/224697668-64cbea5a-7944-4bd0-9c7c-674b89d39553.mov


useMachine is not working in custom hook

Description: #1270
Reproduction: https://codesandbox.io/s/xstate-customhook-bug-8u7gc?file=/src/App.js

you are using your custom hook in the wrong way - you shouldn't use them within your return value, all of them should be statements near the top of your component declaration. In this particular situation, it would work, but it is not advised to do this in React. Also - hooks shouldn't usually return React elements.
each useMachine starts a new machine. So in your example, you actually have 2 separate live toggle machines but you only send events to one of them. That's why the second one's state doesn't get updated and it displays 0 all the time.

Thanks for your answer! @Andarist

If it is wrong way, how can I extract very complex/verbose logic made by useMachine? Is it impossible?
Great answer! I got it, this is very obvious explanation. 😄

If it is wrong way, how can I extract very complex/verbose logic made by useMachine? Is it impossible?

You would have to describe what exact problem do you have, I'm not sure what exactly is complex/verbose in your eyes so I can't answer this without learning more about your perspective.

I will close this as invalid - @baeharam Feel free to create a discussion if you want to talk about your use-case further.


Changing JUPYTER_SERVER_ROOT makes data inaccessible to users of other notebooks

Describe the bug
The OpenVINO image changes JUPYTER_SERVER_ROOT to point to the set of example notebooks as its root. However, if users are attempting to migrate work over onto OpenVINO, this effectively locks them out of the data on their volume in an unintuitive way.
Expected behavior
JUPYTER_SERVER_ROOT should point to the regular location
Screenshots
Screenshot of a standard setup:

Screenshot of the change in the OpenVINO image, note that the work the user may have had at /opt/app-root/src is now no longer accessible:

Installation instructions (Please mark the checkbox)
[X] I followed the installation guide at https://github.com/openvinotoolkit/openvino_notebooks#-installation-guide to install the notebooks.
Additional context

Thanks for the very clear report. We use this as a Docker image also for people who just want to try out OpenVINO Notebooks locally - and then having it start in the notebooks directory, so that it looks the same as with a local install, makes sense. I see the usecase though - we can change this.

Gotcha, maybe we can throw it behind some kind of flag

I think we were not overriding JUPYTER_SERVER_ROOT, but I edited start-notebooks.sh at some point to start Jupyter Lab in the notebooks directory. I just reverted that in the PR linked above.

Cool, looks like a good fix


[#30] Complete the script to generate the whole KMM project

Close #30

What happened 👀

Switch the android submodule to the develop-koin branch.
Fix: generate the Android app module with the entered bundle id, not always to co.nimblehq.kmm.template.
Create a script to generate the shared module.
Move make_android and make_ios scripts to the scripts folder.
Customize the output folder to the project_name.
Update README instructions.

Insight 📝

To generate the shared module with the coresponding package name & project name, clone & adjust the Android Templates's kscript to generate only the shared module.
To customize the output folder, replace all sample folder name with $project_name.

Proof Of Work 📹

I temporarily switched to generate the sample project with a custom package name as co.nimblehq.kmm.sample to demonstrate that the script can now generate the whole KMM project with entered inputs ✅

Please verify through this commit https://github.com/nimblehq/kmm-templates/pull/47/commits/16a34a6014c082252e3f7ceb7a6f25c9e0e3b4ff.

We will switch it back to co.nimblehq.kmm.template after having enough approvals.

The script now is able to generated the new project to a custom folder as project_name, not always to the sample folder 🎉  For example, running ./make.sh --bundle-id co.nimblehq.kmm.sample --bundle-id-staging co.nimblehq.kmm.sample.staging --project-name sample2 --ios-version 14.0 will generate a new project at sample2 folder.

TODO: missing buildKonfig.properties https://github.com/nimblehq/kmm-templates/tree/feature/30-complete-the-script-to-generate-new-kmm-project/sample

TODO: missing buildKonfig.properties feature/30-complete-the-script-to-generate-new-kmm-project/sample

Fixed in https://github.com/nimblehq/kmm-templates/pull/47/commits/f1191bfe814801908d134353e0c2d7420859b217


Replace classloader and jarloader with serviceloader

Refactor ActionRegister to ActionRegistry.
Add ServiceLoader support.
Add UDAction.jar to ClassPath.

Codecov Report

Merging #247 into trunk will decrease coverage by 0.06%.
The diff coverage is 73.33%.

@@            Coverage Diff             @@
##            trunk     #247      +/-   ##
==========================================
- Coverage   57.49%   57.43%   -0.07%
==========================================
  Files         102      102
  Lines        4423     4407      -16
  Branches      661      657       -4
==========================================
- Hits         2543     2531      -12
+ Misses       1632     1629       -3
+ Partials      248      247       -1

This is obsolete. Some codes were already consolidated into the existing codes.


[bug] Android built apk with Tauri is not installing on the device

Describe the bug
I created a sample project using by cargo create-tauri-app and the project successfully built to Desktop (Linux & Windows) and also Android.
But installation on the android device failed with the error below :
The APK failed to install.
Error: INSTALL_PARSE_FAILED_NO_CERTIFICATES: Failed collecting certificates for
/data/app/vmdl1377986156.tmp/base.apk: Failed to collect certificates from /data/app/vmdl1377986156.tmp/base.apk: Attempt to get length of null array

Reproduction
cargo create-tauri-app
cargo tauri android init
cargo tauri android build

adb install ./app-universal-release-unsigned.apk

Expected behavior
Thats right that our apk is not signed but we expect to be installed successfully in debug mode.
Full tauri info output
[✔] Environment
    - OS: openSUSE 20241007.0.0 x86_64 (X64)
    ✔ webkit2gtk-4.1: 2.44.4
    ✔ rsvg2: 2.59.1
    ✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
    ✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
    ✔ rustup: 1.27.1 (2024-09-04)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (environment override by RUSTUP_TOOLCHAIN)
    - node: 22.3.0
    - pnpm: 9.12.2
    - yarn: 1.22.22
    - npm: 10.9.0

[-] Packages
    - tauri 🦀: 2.0.6
    - tauri-build 🦀: 2.0.2
    - wry 🦀: 0.46.3
    - tao 🦀: 0.30.3
    - tauri-cli 🦀: 2.0.2
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli : 2.0.2

[-] Plugins
    - tauri-plugin-shell 🦀: 2.0.2
    - @tauri-apps/plugin-shell : not installed!

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../src

Stack trace
No response
Additional context
No response

cargo tauri android build

is not the command for debug mode, for a debug mode build use
cargo tauri android build --debug

@ahqsoftwares that's right, it should be cargo tauri android build --debug for debug builds.

@ahqsoftwares that's right, it should be cargo tauri android build --debug for debug builds.

You're right. I built with debug flag and installed successfully on my Android mobile.
But how should i build in release mode? when i built it with :
cargo tauri android build

it gives me the error i explained in the issue. I'm Back-End developer actually and I don't have deep knowledge about mobile development. so I don't understand what the problem is with the Tauri that does not installing on my mobile in release mode.
Help.🥲

Checkout https://tauri.app/distribute/sign/android/ on how to sign your apk so tauri android build would work correctly.


iOS build fail

I'm building for iOS 11 with Swift 5 and I'm receiving a build failure at SwiftFlutterSocialContentSharePlugin.swift:111. Basically the named argument says it should be viewController instead of fromViewController. If I change it in my cache it builds fine. I'm using your latest version available.

that because this lib is not update for the newest FBSDK yet

Same issue. Editing the cache file, like @chrisjasp, worked

Where is the cache file located?


Can there be a toggle for the old interface??

I hate the new interface. Can there be a toggle for the old flat interface. The new ones too weird looking .

I'd love to bring back the old interface too. But unfortunately, it's outside of the scope of this mode (portainer-ce-without-annoying).
I'll have a look when I have time...


Documentation on current file/folder limitations

So after uploading 150 000 files to a single folder, I started getting:

Bad Request
{
    "code" : "notAllowed",
    "message" : "Max limit on the number of children items is reached",
    "innererror" : {
        "code" : "childItemCountExceeded"
    }
}

Could you please document these limitations? I also remember there used to be a limit to how deep folders can be nested (was around 7 IIRC). I was able to experimentally confirm that this is no longer the case, but I wonder whether that means the depth limit has just been increased rather (to what value??) than completely removed. Also, is there something like MAX_PATH from win32 API? I just wonder what other "hidden" limitations there are.

I have noticed the error codes being documented, but I fail to find any actual limit values documented anywhere. I guess these limit values can only increase (to maintain compatibility). Could you please publish the current values? Thank you.


Allow alternative github API URL

This PR allows an alternative github API URL to be specified on the command line. This allows Github Enterprise users to use their private APIs to render markdown (e.g. for privacy reasons, as well as linking correctly with the --context option).
Testing
I haven't added any tests for this feature. I've tested manually with
pip install -e 'git+git@github.com:dandavison/grip.git@api-url#egg=grip'

checking that normal invocation works, and also invocation against a GHE instance with something like
grip --api-url https://github.counsyl.com/api/v3 --user dan --pass <access_token> --context owner/repo --gfm PR.md

Good addition!
There's just a few tweaks, then I'm willing to pull this in.

One last thing. Could you document the api_url additions to the rest of the API in the README? Namely, render_page, export, render_content, serve.
Thank you!

I've moved the new argument so that it's the last keyword argument everywhere (except in github_renderer.render_content() where it is a new required positional arg).
I've tested with a few different invocations like
pip install -e 'git+git@github.com:dandavison/grip.git@api-url#egg=grip'
echo 'Issue #118' | grip --api-url https://github.counsyl.com/api/v3 --user <user> --pass <token> --context <owner>/<repo> --gfm -
echo 'Issue #118' | grip --gfm -
echo 'Issue #118' | grip --gfm --context=joeyespo/grip -
echo 'Issue #118' | grip --export

And also completed the API documentation updates in the README.md. I haven't bumped the version or  edited the changelog; let me know if there's any more I can help with. It would be great to have the new functionality on pypi so that I can recommend grip for usage with our GHE instance.

@dandavison This looks good. Thank you! I'll take care of the changelog, etc. I'll try to get this released along with a few other changes this week.


Forge "Project URL" doesn't point to github

At the Puppet forge, the project URL for this project just points back to the puppet forge.  The project URL should point to github.

any update please?  This is a simple fix.


⚠ Samsung has degraded performance

In 7a32285, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2616 ms

Resolved: Samsung performance has improved in 5d8321b.


docs: create Cloud Shell tutorial for Garden

Use this button to demo:

With shortlink:

We have two types of quickstart tutorials: the Dashboard-driven experience and following the directions in the docs. Both require users to install tools on their local filesystem and clone the quickstart to get started, increasing friction. With Cloud Shell, a user gets an integrated experience, with a web editor (Eclipse Theia) on one side, and an interactive tutorial pane on the right. The tutorial pane is interactive using Markdown extensions that can do things like spotlight Editor elements and open files when clicked, creating a delightful, user-friendly experience.

Spotlighting UI elements:

Notes for reviewer:
I've chosen in this tutorial to use minikube inside a user's Cloud Shell. We can, at our option, also include instructions for provisioning and using a GKE cluster. The advantages to using Cloud Shell for this are that Cloud Shell is already authorized to the user so it's a muck quicker onboarding to the full remote experience. And Cloud Shell can present the GCP project picker inside the tutorial window.
Integrated project picker:

@twelvemo, @mkhq , @10ko it works! 🎉
The nodePort and linkUrl rewrite work!
One issue I encountered was the postgres deploy failing and not re-trying:

I just ran deploy again, which successfully deployed all services the second time:

We didn't need a Cloudflare Tunnel, Inlets, etc. because Cloud Shell rewrites localhost links:

Oh that's so nice that cloud shell rewrites the links!

@worldofgeese should we create a separate garden environment for cloud shell or do you want it to be the local environment?

@worldofgeese should we create a separate garden environment for cloud shell or do you want it to be the local environment?

I think local env is fine unless you think it's a good idea to have a separate one?

@mkhq added button with shortlink to original post.


Fix Travis deprecation warning about objects = nil

DEPRECATION WARNING: objects = nil is deprecated and will be removed from ManageIQ D-release (use [] to get an empty result back. nil will return all records). (called from filtered at /home/travis/build/ManageIQ/manageiq/app/models/rbac.rb:329)

@kbrock I think you added the code to produce this deprecation warning.

All set


Create a system for pop-up.

You need to show popup to confirm user about their sign-in/ sign-out or whenever a user submits a query on Contact Us page.
Use any library such as flash/noty, etc.

I like to work on this. Can you please assign it to me?

@khushi935, go ahead and create the PR in 4-5 span. Remember to join the discord server provided in Readme.

@khushi935, go ahead and create the PR in 4-5 days. Remember to join the discord server provided in Readme.

Okay

Hi,
Is this issue still open? I would like to work on it. Please assign it to me.

@abhinav5481  you can work on it. I am not able to do it.☹


Update 03-write-your-first-query.mdx

Fixes https://github.com/apollographql/apollo-android-tutorial/issues/1

Thank you so much 🙏 !


4.26 version

Is it possible to compile this for 4.26? Epic's OSC plugin has bugs

Hi, Yes, it works with 4.26. Guillaume Envoyé depuis mon téléphone Huawei-------- Message original --------De : dpredie @.>Date : dim. 28 mars 2021 à 04:34À : monsieurgustav/UE4-OSC @.>Cc : Subscribed @.***>Objet : [monsieurgustav/UE4-OSC] 4.26 version (#87)
Is it possible to compile this for 4.26? Epic's OSC plugin has bugs
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.

hi @monsieurgustav
thanks for the reply, i tried making a C++ project in 4.26, create Plugins Folder and put the "OSC" folder in there and hit generate VS files, but when i open the VS .sln project in the VS explorer the plugins folder is nowhere to be found.

Hi, it actually compiled now. the issue is I was following the Youtube tutorial to put OSC folder in the Plugins, whereas you need to put the whole UE4-OSC folder to the Plugins folder.

I had to rename this plugin, originally named "OSC", to "UE4-OSC" to fix
conflicts with the now official OSC plugin.
Le 28/03/2021 à 22:52, dpredie a écrit :

Hi, it actually compiled now. the issue is I was following the Youtube
tutorial to put OSC folder in the Plugins, whereas you need to put the
whole UE4-OSC folder to the Plugins folder.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/monsieurgustav/UE4-OSC/issues/87#issuecomment-808957586,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBKOLIUNZCS4MH3SCS3UO3TF6JKNANCNFSM4Z5RJWVA.

using UE4-OSC folder instead works, thanks!