With the release of version 1.9.0 sbt is deprecating the IntegrationTest configuration. Read on to learn how to migrate to tagged tests instead.
While the recommended migration path is to create a subproject in which you pool all your integration tests, I respectfully disagree and suggest to use tagging to filter tests during test runs.
For quite a long time PostgreSQL supports authentication via SCRAM-SHA-256 now, so migrating is long overdue. This small guide will show you how to do this.
The support for SCRAM-SHA-256 was introduced in version 10 of the PostgreSQL database and it is the default for freshly installed systems since version 13.
Since it is not only used for internal storage of password hashes on the database side but also for clients which have to hash their connection password in the correct way there likely was some impact when databases were upgraded. However in some cases clients were not ready and so sometimes the DBMS was configured to stick with md5 and most likely forgotten. ;-)
Without further configuration you will not be able to put a widget from TeamCity onto a dashboard in Hub. Usually you can create a widget but it will not load any data complaining about “Cannot load project list” or something similar.
The reason for it is that some CORS configuration on the TeamCity side is needed.
VCS usually have hooks into which commands can be “plugged” to be executed automatically upon certain events and the great darcs is no exception.
Having your code checked for formatting guidelines before you record (commit) it is quite convenient and so let us implement a prerecord hook for darcs that instruments sbt to check you code style.
There are scenarios when you might want to automatically create snapshots via ZFS to have a backup ready if needed. The features of ZFS make this straightforward and easy. However this also means that you might run into trouble because of having too many snapshots.
It is nice if your CI/CD pipeline does also check for code format compliance but sometimes you may want to have feedback earlier or even prevent unformatted code to enter the repository.
In such a case the git DVCS offers hooks to the rescue. You can either dive into their documentation or simply use the script provided below. ;-)
Sometime you need or want to move a commit or several of them between different git branches. One possible scenario would involve a created feature branch which runs a bit longer and multiple important fixes have been made on it. Some might argue that this shouldn’t happen but guess what: this happens all the time. ;-)
For some time now the usage of metals for
Scala development is no longer a choice for the brave but could be
considered the “should be default” variant. However the installation for the
neovim plugins has changed from using coursier bootstrap to something
supposed to be easier. But at least under FreeBSD I ran into some issues.
So here is a workaround to get a clean installation.
Some days ago I ran my regular pkg upgrade command under FreeBSD and lost
my input devices under X11 (Xorg). :-(
However with help from several people we were able to find a fix for it.
My colleague Maali discovered an issue that raises its ugly head if you’re using the typesafe config library in combination with Cats effect and certain versions of SBT.