How to Update a Snap on Ubuntu
My Ubuntu machine nagged me with notifications like this one:
Pending update of chromium snap: Close the app to avoid disruption (5 days left)
My Ubuntu machine nagged me with notifications like this one:
Pending update of chromium snap: Close the app to avoid disruption (5 days left)
As the final post of the series on our .Net 6 migration, we look at our experience of running our new .Net 6 application in production. You can find the other parts of the mini-series here:
A side effect we noticed after the migration to .Net 6 was that the test task in Azure DevOps took a lot longer than before. The test execution itself did not change much, but the dotnet test task had much more overhead than vstest. As an example, the test task took 4m 48s, while the test execution only took 1m 34s – giving us an overhead of 3m 14s or roughly 75% of the total time:

We recently had a strange behaviour in Azure DevOps: When we run our tests there, the test runner found nearly 16'000 tests. If we run the tests for the same solution in Visual Studio, we only had about 2'000 tests. Where did those additional 14'000 tests come from?
A few days back I lost my admin credentials to the Seq server on my development machine. Luckily, there is an easy way to reset those credentials and keep all your data.
In the older versions of SonarQube you got a dedicated InstallNTService.bat file to install the Windows Service of SonarQube. This file is no longer shipped with a current SonarQube installation. Instead, we must run SonarService.bat with the install option to run SonarQube as a Windows Service:
The new LTS version 9.9 of SonarQube comes with a lot of changes. One of that changes is that OpenJDK 11 is no longer supported to run the SonarQube Server. Unfortunately, I could not find an OpenJDK 17 on openjdk.org. So, where can we find that specific version without licensing it from Oracle?
For many years we could use this post to restore the Azure *.bacpac file with the backup of our user group web site. As I tried it today, I ended up with a long wait time (nearly 20 minutes) and multiple errors:
After we figured out the problem with the AlwaysOn default setting between Terraform and a Linux environment in Azure, we run into the next Problem:
Error: expected site_config.0.application_stack.0.dotnet_version to be one of [3.1 5.0 6.0], got 7.0
As part of the release build of our user group site, we use Terraform to create a BDD environment from scratch, run the acceptance tests and then destroy the environment to keep the cost down. As we recently switched the BDD environment from Windows to Linux, we run into this error:
Error: creating Linux Web App: (Site Name "***" / Resource Group "***"): web.AppsClient#CreateOrUpdate: Failure sending request: StatusCode=409 -- Original Error: Code="Conflict" Message="There was a conflict. AlwaysOn cannot be set for this site as the plan does not allow it. For more information on pricing and features, please see: https://aka.ms/appservicepricingdetails "