After build problems with my PKM site, today I ran into another problem with this site.

What puzzled me was Deploy showed Build step failing but no useful error (other than exit code 2 - which does not help much)

But in the process of debugging, I learnt ¹ about the environment variable NETLIFY_BUILD_DEBUG (set to true when needed) It did not help 😞

I also upgraded hugo version (which is another environment variable) in the process.

In a multi-tenant rails application, usually we extract the tenant, before we process it further. Sometimes, the process requires us to process the data in background (via Sidekiq) and because the background job also needs to query the DB, it also needs to set tenant.

Turns out, we can pass “some” data from the controller to the sidekiq job via ActiveSupport::CurrentAttributes While, sidekiq may need to set the tenant again (for more DB queries) but one can save at least one query (to find out the account itself)

As mentioned here and later here I recently moved PKM from Dendron to obsidian-zola

The original code seems abadoned (No updates in little over a year). I understand this since it is likely built for personal use, and it works for them (FWIW, the demo site itself is not updated for exactly same duration)

Turns out people forked it and improved it.

At first I tried this fork, renamed as obsidian-zola-plus (as it made it better than the original) This one seemed active (updated little over 2 months ago. Yet 2 PRs are unmerged 🤷‍♂)

First impression people have is that Emacs is an editor. So in an editor one should just save as to different name/path. ¹

But save as is different from renaming a file. save as creates a copy of the file with a different name/path. So one has two files with old and new paths.

But rename leaves just one file at thenew path.

Older versions of Emacs (< Emacs 26) did not have this functionality built-in So either one had to use dired or people wrote their own functions.

As mentioned in the earlier post,

at work I was “strongly encouraged” to use Azure Service Bus, instead of RabbitMQ Unfortunately

SDK has FormatDeadLetterPath functionality but it is not available to HTTP REST API ¹

Append /$DeadLetterQueue to the queue name.²

Refer to this SO comment

Finally migrated my PKM from Dendron to Obsidian-Zola

Things I needed to do were :

1. Remove Dendron specific frontmatter
2. [In Progress] Restructure flat file names that were like Dev.DB.mysql.md to Development/Databases/mysql.md
3. Pushed this branch as main
4. Make main as default and protected branch
5. Unprotect master
6. Renamed old master as dendron (just in case)- without unprotecting old master I could not rename it.
7. Remove Dendron specific settings from netlify. Since this time there is netlify.toml so no additional settings needed.

I would say it was pretty smooth transition 😄

My PKM is currently based on Dendron

Main appeal of Dendron was local-first. At the same time, it indeed was loosely tied to VSCode editor.

Over the years, they had a command line tool to create new notes. Still, its strength always was as a VSCode plugin

Then today, I came across Obsidian-Zola

It splits the task of taking notes and publishing it.

• Obsidian for note taking
• Zola for publishing

What I liked about it is Search functionality (To be fair, my current PKM build on Dendron also has it)

Now that I’m working on .NET and C#, I enabled csharp-mode in Doom Emacs. While exploring minor modes related to csharp-mode, I came across Glasses minor mode.

Here is the EmacsWiki page.

TL;DR:

The default setting is to separate the Capped bits with an underscore, so EmacsIsStudly shows as Emacs_Is_Studly.

I too, prefer to see the code as-is, but it is good to know that Glasses mode exists. I can see it being useful.

I recently started writing C# code at work. While I can read and understand the sample code (and modify partially per my requirement) I still trip up by new-ness (to me) of the ecosystem.

So while I intuitively understand that using is equivalent of require in Ruby (or import in python), I didn’t know which ones are “standard library” and which ones are not.

The sample code worked with standard library, but writing to Azure Service bus requires external library. Just adding using Azure.Messaging.ServiceBus is not enough. One also needs to install the package.

At work, I’ve been using REST API to connect to Azure Service Bus because officially Microsoft does not support Ruby SDK (It is retired since 2015)

The documentation related to accessing Azure Service Bus via REST API is very limited, and at time difficult to use.

e.g. This documentation about How to unlock a message in the (Azure Service Bus) queue mentions this URL pattern to be used for the REST API call :