When it comes to testing, we usually hear that the tests are too slow. While that is a problem, we can also run into unexpected problems if the tests run too fast.
We had this line in one of our tests that checks with Fluent Assertions that the newest entry for our order history was written in the last minute:
Hangfire is a great tool to for background processing in .Net. We use it for all our projects, and it works without any problems.
There is only one bit of nitpicking we found: If you use Hangfire with multiple projects, it is a bit hard to keep the dashboards apart. By default, the tile reads "Hangfire Dashboard" in all of them:
When we start a new project, we best create a Git repository right away. The only problem when we do that from the command line is that we do not get a .gitignore file. Without such a file, Git will track all files in our repository – including *.exe, *.dll, *.pdp and many more that we do not want. We could go and find a .gitignore from a different project. But there is a better way for our .Net projects:
On a regular Linux, we would use this command to restart the computer:
On my newly upgraded Ubuntu 24.04 LTS I got this error when I started a Java application:
Exception in thread "main" java.awt.HeadlessException: No X11 DISPLAY variable was set, or no headful library support was found, but this program performed an operation which requires it,
at java.desktop/sun.java2d.HeadlessGraphicsEnvironment.getDefaultScreenDevice(HeadlessGraphicsEnvironment.java:58) at foo.lj.a(Unknown Source) at foo.lj.(Unknown Source)
The upgrade from Ubuntu 22.04 to 24.04 took a lot more effort than I am used to. The option to install to the current LTS version did not show up in the graphical update application and the command line tool ended with this error:
There is a simple trick to find out if a certain website uses the CDN Cloudflare or not. All we need to do is to add /cdn-cgi/trace at the end of the (sub)domain name:
One would assume that renaming a default constraint should work the same way as renaming a primary key. For some unknown reason that was not the case as I had to fix the (dynamically generated) names of default constraints. The format that worked at last was this one:
Unlike most other tools, PowerShell does not offer us a -version flag to tell us its version number. There is a -Version flag (with a capital V), but that we need to use a specific version of PowerShell. What can we do to find out what version we run?
There is not much more annoying that fixing a bug in a JavaScript file and then find problems in production because the browsers of your users cached the old file. While the first reaction is to disable all caching, there is a better way in ASP.NET: append the file version to the JavaScript file name.