DEV Community: Jonas Samuelsson

git rebase on pull

Jonas Samuelsson — Wed, 06 Nov 2024 08:21:03 +0000

One way of getting a more linear history in git is to do rebase on pull.
Run git config --global pull.rebase true to set this globally.

Azure Data Studio account cache

Jonas Samuelsson — Tue, 10 Sep 2024 13:35:07 +0000

I prefer using Azure Data Studio when I need to interact with SQL Server databases.
Each time I want to connect to our production databases I need to elevate using Privileged Identity Management.
Azure Data Studio caches my token but isn't smart enough to handle when the token has expired, instead I get this modal.

The solution to this is to close Azure Data Studio and then delete the files located in %userprofile%\AppData\Roaming\azuredatastudio\Azure Accounts, either manually or by using this powershell script:

Get-ChildItem "$($env:userprofile)\AppData\Roaming\azuredatastudio\Azure Accounts" | Remove-Item

kusto trendlines

Jonas Samuelsson — Fri, 02 Feb 2024 06:45:49 +0000

I recently stumbled upon an example for how to include "trendlines" in kusto queries that might be handy.

exceptions
| where timestamp > ago(90d)
| summarize c = log(count()) by bin(timestamp, 1d)
| as hint.materialized=true T
| extend _perc_25 = toscalar(T | summarize percentile(c, 25)),
         _perc_50 = toscalar(T | summarize percentile(c, 50)),
         _perc_75 = toscalar(T | summarize percentile(c, 75))
| render timechart

Resend Azure Service Bus topic message

Jonas Samuelsson — Mon, 10 Jul 2023 17:11:03 +0000

In this post I'm going to take a look at one of the implications of resubmitting azure service bus subscription dead letter messages and how it can be solved.

Azure service bus has two kind of messaging entities, queues and topics. We wont go deep into the difference of the two here but basically a queue has a single logical consumer while a a topic can have multiple logical consumers (subscriptions). Microsoft docs available here.

A message sent to a topic is distributed to all configured subscriptions. And each subscription has its own dead letter queue where messages are placed if the can't be consumed within the specified retry count.

It would be nice to resend a dead letter message back to its subscription but that can't be done. No messages (new or dead letters) can be sent directly to a subscription, they have to be sent to the topic.

But this means that the message will be distributed to both subscriptions. If you have written your message handlers to be idempotent, meaning that they can handle the same message twice, there is no problem and you can stop reading now but if that isn't something you can guarantee you're in a bit of a problem. As we were.

Filters to the rescue.

Filters can be applied to a subscription to make sure that only messages that fulfills a given criteria is handled by the subscription (messages that don't fulfill the criteria are dropped).

We applied filters to all our subscriptions so that it only process messages where a header called TargetSubscription either doesn't exist or contains the name of the subscription.

Since we use bicep to deploy our azure infrastructure it was fairly easy to create a module for this.

resource r 'Microsoft.ServiceBus/namespaces/topics/subscriptions/rules@2021-11-01' = [for subscription in subscriptions: {
  name: '${namespace}/${subscription.topicName}/${subscription.name}/default'
  dependsOn: [
    s
  ]
  properties: {
    filterType: 'SqlFilter'
    sqlFilter: {
      sqlExpression: 'TargetSubscription is null or TargetSubscription = \'\' or TargetSubscription = \'${subscription.name}\''
    }
  }
}]

With this in place it now becomes fairly trivial to send messages to a specific subscription.

dotnet assembly binding redirects

Jonas Samuelsson — Wed, 14 Sep 2022 13:20:17 +0000

In order to add the correct assmbly binding redirects in full framework projects, add this project setting.

<PropertyGroup>
   <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
</PropertyGroup>

Then do a clean / rebuild with warnings enabled and double click the related warning.

kusto - filter by custom dimension keys

Jonas Samuelsson — Tue, 13 Sep 2022 10:11:23 +0000

I sometimes want to filter app insights entries based on whether a custom dimension exists or not.

mv-expand to the rescue 😃

The query below returns requests containing a custom dimension starting with the string toggle:.

requests
| extend dimension = bag_keys(customDimensions)
| mv-expand dimension
| where dimension startswith "toggle:"

kusto & concat string array

Jonas Samuelsson — Thu, 07 Jul 2022 10:34:31 +0000

From time to time I want to summarize a kusto query by a combination of multiple values.

One way to do that is to concat them all manually, like this

strcat(cloud_RoleName, "-", application_Version, "-", resultCode)

During investigations I often want to change which values I group by and writing the query like this simplifies that

strcat_array(pack_array(cloud_RoleName, application_Version, resultCode), "-")

dotnet restore --interactive not prompting

Jonas Samuelsson — Mon, 06 Sep 2021 11:22:17 +0000

I recently had a situation where doing dotnet restore from the command line resulted in 401 responses and adding the --interactive didn't work to prompt for credentials.

After some googling I found a github issue indicating that Microsofts Azure Artifacts Credential Provider should be installed / updated.

TLDR; run iex "& { $(irm https://aka.ms/install-artifacts-credprovider.ps1) } -Force".

git clone and long paths on windows

Jonas Samuelsson — Thu, 01 Jul 2021 14:11:16 +0000

If you ever run in to the issue that you can't clone a git repo because it contains paths longer than 260 characters on windows run

git config --global core.longpaths true

There is a registry entry for long paths as well but that doesn't help here.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"LongPathsEnabled"=dword:00000001

Restart multiple azure app services

Jonas Samuelsson — Fri, 09 Apr 2021 07:28:57 +0000

We sometimes need to restart all azure app services in a subscription or service plan. It's very time consuming to do manually in the portal as it has to be done per app service but using az cli it's really easy. =)

az webapp list | convertfrom-json | foreach { az webapp restart --ids $_.id }

azure devops pipeline predefined variables

Jonas Samuelsson — Tue, 02 Mar 2021 09:53:26 +0000

Azure DevOps provides a number of predefined variables.

Some of these are folders for your source files, artifacts, temp files, etc.
And some of these variables maps to the same value.

Here is a list of all the folder variables (on a window-2019 image):

Agent.BuildDirectory: D:\a\1
Agent.HomeDirectory: C:\agents\2.182.1
Agent.TempDirectory: D:\a\_temp
Agent.ToolsDirectory: C:\hostedtoolcache\windows
Agent.WorkFolder: D:\a
Build.ArtifactStagingDirectory: D:\a\1\a
Build.BinariesDirectory: D:\a\1\b
Build.Repository.LocalPath: D:\a\1\s
Build.SourcesDirectory: D:\a\1\s
Build.StagingDirectory: D:\a\1\a
Common.TestResultsDirectory: D:\a\1\TestResults
Pipeline.Workspace: D:\a\1
System.DefaultWorkingDirectory: D:\a\1\s

TF30063

Jonas Samuelsson — Thu, 14 Jan 2021 06:26:51 +0000

From time to time I have to work with projects using Azure DevOps TFVC.
It is fairly common that I get a TF30063 error in the Team Explorer, saying I'm unauthorized and need to reenter my credentials. But unfortunately that doesn't help.

I just found a visual studio developer community post containing the solution.

If Visual Studio is showing the Team Explorer tab/panel, select the Solution Explorer tab/panel.
If Visual Studio had already been showing the Solution Explorer tab, select the Team Explorer tab and then select the Solution Explorer tab again.
Make sure that the Solution Explorer tab is currently selected, and close this instance of Visual Studio (if I have other Visual Studio instances open that are connected to the on-premises TFS server, I leave those open).
Re-open the same project (connected to Azure DevOps) in Visual Studio, and now everything seems to be fine.