For the last few months, the iOS WordPress application had more and more problems connecting to my self-hosted blog. Deleting it and reinstalling the app helped only for a short time. As there was no change in the situation with the new Jetpack application, I had to figure out what was wrong.
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 "
One of the projects I have got "A" ratings though all metrics in SonarQube. The only problem: it showed a project size with 0 lines of code. How did this happen?
After checking the logs, I noticed a warning indicator on the project page of SonarQube:
In one old web application I had to add a redirect form one endpoint to the address of the new application. Everything compiled without a problem, but as soon as I accessed the old address, I got this exception:
NWebsec.Core.Exceptions.RedirectValidationException: A potentially dangerous redirect was detected. Add the destination to the whitelist in configuration if the redirect was intended. Offending redirect: https://my.url.whatever
After I updated SonarQube to version 9.7, I got this strange entry in the logs:
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Before you can assign work items to a sprint (or an iteration) in Azure DevOps, someone needs to create those sprints. That boring task is a great candidate for delegation. Unfortunately, the only role that can do this work by default is the project administrator. Before you turn everyone into a project administrator, let me show you a much more granular way to achieve the same goal.
After my series of 13 posts about Playwright spanning C# and Python, it is time to answer the two question I got asked a lot in the past few weeks:
Is Playwright ready for production?
Yes
Should we switch to Playwright?
It depends.
The second one is a boring answer, but if you want to have my honest opinion, then that is it. Let’s recapitulate what we covered in this blog series and add the context to the favorite answer of consultants.
After last week's success with BrowserStack, I tried to run Playwright on Selenium Grid. The user experience for this use case is at the opposite end of the scale. The documentation is not much help and Selenium Grid has its own incompatibilities. Let's look at how we can still make it work.
With only a few days left in 2022, it looks like this fading year was not too bad for me. I was able to travel again and visit places I have missed and others I have wanted to see for a long time.