Day going normally while working on converting our Python projects to use uv (Just awesome!) instead of the usual pip and while converting one of the Azure Functions Python project, I encountered the following weird error while running uv sync -

PS D:\dev\RE> uv sync
  × Failed to build `fusepy==3.0.1`
  ├─▶ The build backend returned an error
  ╰─▶ Call to `setuptools.build_meta:__legacy__.build_wheel` failed (exit code: 101)

      [stderr]
      Unable to create process using '"D:\Python-3.10.15\PCbuild\amd64\python.exe" -c "import sys

      if sys.path[0] == \"\":
          sys.path.pop(0)

      sys.path = [] + sys.path

      from setuptools.build_meta import __legacy__ as backend

      import json

      get_requires_for_build = getattr(backend, \"get_requires_for_build_wheel\", None)
      if get_requires_for_build:
          requires = get_requires_for_build({})
      else:
          requires = []

      with
      open(\"C:\\Users\\PJ\\AppData\\Local\\uv\\cache\\builds-v0\\.tmp0KnOHv\\get_requires_for_build_wheel.txt\",
      \"w\") as fp:
          json.dump(requires, fp)
      "'

      hint: This usually indicates a problem with the package or the build environment.
  help: `fusepy` (v3.0.1) was included because `RE` (v2.2.0) depends on
        `REOE==2.2.0a3` (v2.2.0a3) which depends on `azureml-sdk==1.58.0`        
        (v1.58.0) which depends on `azureml-dataset-runtime[fuse]>=1.58.0, <1.59.dev0` (v1.58.0) which       
        depends on `fusepy>=3.0.1, <4.0.0`

This was strange because this same command (uv sync) was working fine in another project I just converted. I just ran python --version on PowerShell and was greeted with the following -

PS D:\dev\RE> python --version
ResourceUnavailable: Program 'python.exe' failed to run: An error occurred trying to start process 'D:\Python-3.10.15\PCbuild\amd64\python.exe' with working directory 'D:\dev\RE'. This program is blocked by group policy. For more information, contact your system administrator.At line:1 char:1
+ python --version
+ ~~~~~~~~~~~~~~~~.

Aah! Turns out, our organization recently rolled out policies geared towards security and disabled a lot of the programs. What they have done is that in order to run anything like python, I need to escalate myself with Administrator privileges by entering the security details and then also provide justification before I could do anything.

I did the same and then ran python --version followed by uv sync which worked without any issues. The above issue happened because there were some dependencies which had to be built from source and that required Python to work.

This post is to help me in the future! Here is the list of links which provide the list of tags which are available for all the Azure App Service Docker Images.

While building the images for Azure Web App for Containers, I have had best results by building on top of the images which Microsoft uses.

Python - https://mcr.microsoft.com/v2/appsvc/python/tags/list
PHP - https://mcr.microsoft.com/v2/appsvc/php/tags/list
NodeJS - https://mcr.microsoft.com/v2/appsvc/node/tags/list

I will add more as I find them. You will have to search for the latest tag to ensure security updates are applied.

After almost 9 years of service, my NVIDIA GTX 970 finally died. I think it knew that I am planning to build a new PC this year and now that the RTX 5000 series is available, it just gave up. Thank you my trusted GPU for so many good memories!

After removing the GPU, I plugged my display to the onboard display (Intel HD 530) and assumed that everything would be working as expected which it did for a while.

After a while, there was a flicker on the screen and it came back and I thought that it was maybe a glitch and everything was fine.

But, not everything was fine. I started observing 2 issues -

1. Night Light was not working. Tried turning it on and off and nothing. Windows just refused to change the display color to a warm light.
2. The Sleep button was missing from the Power options. I usually have quite some workloads open and so I usually make my PC sleep to save some time.

This was very surprising so I tried reboots, some hacks mentioned on Google but nothing worked until one which suggested to check the Graphics Driver in Device Manager.

Here is what I did to fix the issue -

1. Open Device Manager
2. Expand Display Adapters
3. Under Display Adapters, I saw that it is showing as Microsoft Basic Display Adapter.
4. This was strange considering I had rebooted my machine and earlier it was working fine.
5. Right clicked on Microsoft Basic Display Adapter, clicked on Update Driver -> Search Automatically for Drivers.
6. After a few minutes, it said that it installed the Graphics Driver for Intel(R) HD Graphics 530.
7. Reboot the computer.

And voila! Everything was back to normal. Sleep button is visible again and night light also started working without any issue!

Till next time!

Typing this up because I would like this to be a reminder to myself that do not press Ctrl+C when running npm install. I just ran into a very weird issue where few files were missing out of a package but when I tried npm install again, NPM just thought that the package has already been installed and didn't check the integrity of the files.

Here is the weird error -

PS D:\dev\packages\components> npm run build:css

> @components/components@0.1.0 build:css
> postcss src/stylesSrc/main.css -o src/index.css

node:internal/modules/run_main:129
    triggerUncaughtException(
    ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find module 'D:\dev\node_modules\escalade\sync\index.mjs' imported from D:\dev\node_modules\yargs\lib\platform-shims\esm.mjs
Did you mean to import "escalade/sync/index.js"?
    at finalizeResolution (node:internal/modules/esm/resolve:265:11)
    at moduleResolve (node:internal/modules/esm/resolve:933:10)
    at defaultResolve (node:internal/modules/esm/resolve:1157:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39)
    at link (node:internal/modules/esm/module_job:86:36) {
  code: 'ERR_MODULE_NOT_FOUND',
  url: 'file:///D:/dev/node_modules/escalade/sync/index.mjs'
}

Node.js v20.15.0
npm error Lifecycle script `build:css` failed with error:
npm error Error: command failed
npm error   in workspace: @components/components@0.1.0
npm error   at location: D:\dev\packages\components

After checking the folder structure, I could see that the file was indeed missing but when I checked Escalade's code, the package did have those files. Silly me!

I was working on a PR for Google's CDAP Firebase Plugin to add support for Named Databases and some other fixes.

After completing the development, testing and addressing review comments, I was happy that finally the PR was LGTM but with a caveat. I was required to squash all the commits into a single commit which totally made sense since there were a number of small commits and some upstream changes had been merged as well.
Here is a look at the commit history -

You see the 4 commits on 27th Feb 2024? They were not supposed to be there but somehow ended there. My guess would be when pulling upstream changes, I ran a wrong command which caused all these merge commits and also the other commits. I wanted to preserve all my changes, the upstream changes and then compress my commits in a single commit.

I rarely see situations like this and thought that this requires documenting because I am sure I would forget this soon. Something which required me to re-arrange commits, preserve changes in my branch, make sure upstream changes are in sync in my branch is something I had to do first time.

Let's get started with git rebase.

I executed git rebase HEAD~10 to make sure I am seeing all the history for my branch. It opened the following text file in Notepad for git-rebase-todo -

pick 9e4c312 Create separate plugin repository for Cloud Firestore plugins. (#1)
pick ea11389 Remote snaphsot
pick f2f179b Revert "Remote snaphsot"
pick e0bb69c Update pom.xml
pick 54db280 bump dependency to 2.5.0 instead of 2.5.0-SNAPSHOT
pick c3d8a87 [PLUGIN-1465] Bump Hadoop dependency version to fix log4j vulnerabilities
pick 9e1a825 [CDAP-20182] Create SECURITY.md
pick 33079a1 Update Github Actions and checkstyle
pick 44f1b0a Added databaseName & fixed UI with several other fixes
pick 38af05c [CDAP-20182] Create SECURITY.md
pick ae8cae7 Update Github Actions and checkstyle
pick 4373af9 Added databaseName & fixed UI with several other fixes
pick 8550f0c Removed vs code files and added to gitignore
pick ea0c0bd Fixed as per review comments and fixed bug with widget and blank databasename
pick 80a0c21 Updated tests and fixed typos
pick 4328415 Addressed review comments and added more tests
pick 629cd5d Fixed database name comparison
pick b2a3bcf Reverted change to getting service account
pick 4ba67aa fix checkstyle configurtion
pick c18e86b Fixed checkstyle warnings
pick e9fd442 Addressed review comments
pick 8510826 Separated java imports
pick 5a5bed6 Addressed review comments

# Rebase 6ec1d64..809cd9c onto 6ec1d64 (23 commands)
#
# Commands:
# p, pick <commit> = use commit
# r, reword <commit> = use commit, but edit the commit message
# e, edit <commit> = use commit, but stop for amending
# s, squash <commit> = use commit, but meld into previous commit
# f, fixup [-C | -c] <commit> = like "squash" but keep only the previous
#                    commit's log message, unless -C is used, in which case
#                    keep only this commit's message; -c is same as -C but
#                    opens the editor
# x, exec <command> = run command (the rest of the line) using shell
# b, break = stop here (continue rebase later with 'git rebase --continue')
# d, drop <commit> = remove commit
# l, label <label> = label current HEAD with a name
# t, reset <label> = reset HEAD to a label
# m, merge [-C <commit> | -c <commit>] <label> [# <oneline>]
# .       create a merge commit using the original merge commit's
# .       message (or the oneline, if no original merge commit was
# .       specified); use -c <commit> to reword the commit message
#
# These lines can be re-ordered; they are executed from top to bottom.
#
# If you remove a line here THAT COMMIT WILL BE LOST.
#
# However, if you remove everything, the rebase will be aborted.
#

As you can see, the following commits are twice (albeit with different commit hash) -

pick 9e1a825 [CDAP-20182] Create SECURITY.md
pick 33079a1 Update Github Actions and checkstyle
pick 44f1b0a Added databaseName & fixed UI with several other fixes
pick 38af05c [CDAP-20182] Create SECURITY.md
pick ae8cae7 Update Github Actions and checkstyle
pick 4373af9 Added databaseName & fixed UI with several other fixes

Now, after comparing the hashes with the upstream branch and my branch, I identified that the following commits had to be removed -

pick 9e4c312 Create separate plugin repository for Cloud Firestore plugins. (#1)
pick ea11389 Remote snaphsot
pick f2f179b Revert "Remote snaphsot"
pick e0bb69c Update pom.xml
pick 54db280 bump dependency to 2.5.0 instead of 2.5.0-SNAPSHOT
pick c3d8a87 [PLUGIN-1465] Bump Hadoop dependency version to fix log4j vulnerabilities
pick 9e1a825 [CDAP-20182] Create SECURITY.md
pick 33079a1 Update Github Actions and checkstyle

I also had to remove this commit -

pick 44f1b0a Added databaseName & fixed UI with several other fixes

and then squash the others on 4373af9 Added databaseName & fixed UI with several other fixes

After being confused and searching around on how to do this, I did the squashing but that resulted in a lot of merge conflicts so had to abort the rebase using git rebase --abort.

Then... I saw the following lines in the git-rebase-todo -

# These lines can be re-ordered; they are executed from top to bottom.
#
# If you remove a line here THAT COMMIT WILL BE LOST.

This is exactly what I needed! I wanted to remove some commits and then rearrange the order a bit to ensure there are no merge conflicts. After re-arranging, my git-rebase-todo looked like below -

pick 4373af9 Added databaseName & fixed UI with several other fixes
squash 8550f0c Removed vs code files and added to gitignore
squash ea0c0bd Fixed as per review comments and fixed bug with widget and blank databasename
squash 80a0c21 Updated tests and fixed typos
squash 4328415 Addressed review comments and added more tests
squash 629cd5d Fixed database name comparison
squash b2a3bcf Reverted change to getting service account
squash c18e86b Fixed checkstyle warnings
squash e9fd442 Addressed review comments
squash 8510826 Separated java imports
squash 5a5bed6 Addressed review comments


# Rebase 6ec1d64..809cd9c onto 6ec1d64 (23 commands)
#
# Commands:
# p, pick <commit> = use commit
# r, reword <commit> = use commit, but edit the commit message
# e, edit <commit> = use commit, but stop for amending
# s, squash <commit> = use commit, but meld into previous commit
# f, fixup [-C | -c] <commit> = like "squash" but keep only the previous
#                    commit's log message, unless -C is used, in which case
#                    keep only this commit's message; -c is same as -C but
#                    opens the editor
# x, exec <command> = run command (the rest of the line) using shell
# b, break = stop here (continue rebase later with 'git rebase --continue')
# d, drop <commit> = remove commit
# l, label <label> = label current HEAD with a name
# t, reset <label> = reset HEAD to a label
# m, merge [-C <commit> | -c <commit>] <label> [# <oneline>]
# .       create a merge commit using the original merge commit's
# .       message (or the oneline, if no original merge commit was
# .       specified); use -c <commit> to reword the commit message
#
# These lines can be re-ordered; they are executed from top to bottom.
#
# If you remove a line here THAT COMMIT WILL BE LOST.
#
# However, if you remove everything, the rebase will be aborted.
#

Saved the file and then git asked me to enter the commit message, did that and voila! I could see a single commit in the git log which was mine. After that, did a rebase with upstream - git rebase upstream/develop and did a force push using git push --force.

That removed all the duplicated commits and cleaned the commits. Here is the updated view of all the commits -

This answer from SO helped a lot in understanding as well - https://stackoverflow.com/a/2740812/2758198

Till next time!

Tried running -

mvn clean test -fae -T 2 -B -V -DcloudBuild -Dmaven.wagon.http.retryHandler.count=3 -Dmaven.wagon.httpconnectionManager.ttlSeconds=25

Got -

PS F:\dev\firestore-plugins> mvn clean test -fae -T 2 -B -V -DcloudBuild -Dmaven.wagon.http.retryHandler.count=3 -Dmaven.wagon.httpconnectionManager.ttlSeconds=25
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: C:\ProgramData\chocolatey\lib\maven\apache-maven-3.9.6
Java version: 21.0.1, vendor: Microsoft, runtime: C:\Program Files\Microsoft\jdk-21.0.1.12-hotspot
Default locale: en_IN, platform encoding: UTF-8
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-classworlds/1.2-alpha-9/plexus-classworlds-1.2-alpha-9.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-classworlds/1.2-alpha-9/plexus-classworlds-1.2-alpha-9.pom (3.2 kB at 2.9 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-settings/2.2.1/maven-settings-2.2.1.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-settings/2.2.1/maven-settings-2.2.1.pom (2.2 kB at 54 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-parameter-documenter/2.2.1/maven-plugin-parameter-documenter-2.2.1.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-parameter-documenter/2.2.1/maven-plugin-parameter-documenter-2.2.1.pom (2.0 kB at 115 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-api/2.2.1/maven-reporting-api-2.2.1.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting-api/2.2.1/maven-reporting-api-2.2.1.pom (1.9 kB at 37 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting/2.2.1/maven-reporting-2.2.1.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/reporting/maven-reporting/2.2.1/maven-reporting-2.2.1.pom (1.4 kB at 30 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-profile/2.2.1/maven-profile-2.2.1.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-profile/2.2.1/maven-profile-2.2.1.pom (2.2 kB at 62 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-repository-metadata/2.2.1/maven-repository-metadata-2.2.1.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-repository-metadata/2.2.1/maven-repository-metadata-2.2.1.pom (1.9 kB at 110 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-error-diagnostics/2.2.1/maven-error-diagnostics-2.2.1.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-error-diagnostics/2.2.1/maven-error-diagnostics-2.2.1.pom (1.7 kB at 90 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-project/2.2.1/maven-project-2.2.1.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-project/2.2.1/maven-project-2.2.1.pom (2.8 kB at 111 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-artifact-manager/2.2.1/maven-artifact-manager-2.2.1.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-artifact-manager/2.2.1/maven-artifact-manager-2.2.1.pom (3.1 kB at 94 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-registry/2.2.1/maven-plugin-registry-2.2.1.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-registry/2.2.1/maven-plugin-registry-2.2.1.pom (1.9 kB at 74 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-descriptor/2.2.1/maven-plugin-descriptor-2.2.1.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-plugin-descriptor/2.2.1/maven-plugin-descriptor-2.2.1.pom (2.1 kB at 69 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-monitor/2.2.1/maven-monitor-2.2.1.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/apache/maven/maven-monitor/2.2.1/maven-monitor-2.2.1.pom (1.3 kB at 38 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/1.3/plexus-utils-1.3.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/1.3/plexus-utils-1.3.pom (1.0 kB at 49 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus/1.0.8/plexus-1.0.8.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus/1.0.8/plexus-1.0.8.pom (7.2 kB at 314 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-classworlds/1.2-alpha-7/plexus-classworlds-1.2-alpha-7.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-classworlds/1.2-alpha-7/plexus-classworlds-1.2-alpha-7.pom (2.4 kB at 125 kB/s)
[INFO] Downloading from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus/1.0.9/plexus-1.0.9.pom
[INFO] Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus/1.0.9/plexus-1.0.9.pom (7.7 kB at 404 kB/s)
[INFO] 
[INFO] Using the MultiThreadedBuilder implementation with a thread count of 2
[INFO] 
[INFO] ------------------< io.cdap.plugin:firestore-plugins >------------------
[INFO] Building Google Cloud Firestore Plugins 1.1.0-SNAPSHOT
[INFO]   from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  8.308 s (Wall Clock)
[INFO] Finished at: 2024-01-20T03:45:02+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Unknown lifecycle phase ".wagon.http.retryHandler.count=3". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: pe: pre-clean, clean, post-clean, validate, initialize, generate-sources, process-sources, generate-resources, process-resourccompes, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, tile,est-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-t insest, verify, install, deploy, pre-site, site, post-site, site-deploy. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException

Turns out Maven doesn't like PowerShell and when this same command was executed on Command Prompt (CMD), it worked without any issues.

Source - https://stackoverflow.com/questions/71731474/is-wagon-http-ssl-command-for-maven-deprecated

resource "aws_cloudformation_stack_set" "backup_vault" {
  name                    = "AWS-Backup-Vault"
  description             = "Deploys the AWS Backup Vaults across accounts and regions."
  permission_model = "SERVICE_MANAGED"

  auto_deployment {
    enabled = true
    retain_stacks_on_account_removal = false
  }
  capabilities = ["CAPABILITY_NAMED_IAM", "CAPABILITY_AUTO_EXPAND"]

  lifecycle {
    ignore_changes = [
      administration_role_arn
    ]
  }

  template_body = jsonencode({
    Resources = {
      BackupVault = {
        Type = "AWS::Backup::BackupVault"
        Properties = {
          BackupVaultName = local.backup_vault_name
          Notifications = {
            BackupVaultEvents = [
                "BACKUP_JOB_STARTED",
                "BACKUP_JOB_COMPLETED",
                "COPY_JOB_STARTED",
                "COPY_JOB_SUCCESSFUL",
                "COPY_JOB_FAILED",
                "RESTORE_JOB_STARTED",
                "RESTORE_JOB_COMPLETED",
                "RECOVERY_POINT_MODIFIED",
                "S3_BACKUP_OBJECT_FAILED",
                "S3_RESTORE_OBJECT_FAILED"
            ]
            SNSTopicArn = { "Fn::GetAtt" = ["EmailNotificationTopic","TopicArn"]}
          }
        }
      }
      EmailNotificationTopic = {
        Type = "AWS::SNS::Topic"
        Properties = {
            TopicName = "aws-backup-vault-notifier"
            DisplayName = "AWS Backup Notification Topic"
        }
      }
      EmailNotificationTopicPolicy = {
          Type = "AWS::SNS::TopicPolicy"
          Properties = {
              Topics = [
                  { Ref = "EmailNotificationTopic" }
              ]
              PolicyDocument = {
                  Statement = [{
                    Sid = "AWSBackupNotificationSNSPolicy"
                      Action = [
                          "sns:Publish"
                      ]
                      Effect = "Allow"
                      Resource = { Ref = "EmailNotificationTopic" }
                      Principal = {
                          Service = [
                              "backup.amazonaws.com"
                          ]
                      }
                  }]
              }
          }
      }
      EmailNotification = {
        Type = "AWS::SNS::Subscription"
        Properties = {
            Endpoint = "aaa@aaa.com"
            Protocol = "email"
            TopicArn = { "Fn::GetAtt" = ["EmailNotificationTopic","TopicArn"]}
        }
      }
    
  }
})
}

This was a really weird error coming from Terraform while doing a terraform plan. Good thing is this allows me to write a blog post because pretty sure I am going to forget about this...

The Terraform code which was causing this issue -

module "access_log_bucket" {
  source  = "cloudposse/lb-s3-bucket/aws"
  version = "~> 0.16.4"

  context = module.access_log_bucket_label.context
  tags    = module.access_log_bucket_label.tags

  versioning_enabled = true
  lifecycle_configuration_rules = [
    {
      id                                     = "abort-incomplete-multipart-upload-after-7days"
      enabled                                = true
      abort_incomplete_multipart_upload_days = 7
      filter_and = null
      expiration = null
      transition = []
      noncurrent_version_transition = []
      noncurrent_version_expiration = null
    },
    {
      id                                     = "delete-non-current-versions-after-30-days"
      enabled                                = true
      abort_incomplete_multipart_upload_days = null
      filter_and = null
      expiration = null
      transition = []
      noncurrent_version_transition = []
      noncurrent_version_expiration = {
        days = 30
      }
    }
  ]
}

The error I was seeing is as below -

Error: Invalid value for input variable

  on dev-network\access-log.tf line 17, in module "access_log_bucket":
  17:   lifecycle_configuration_rules = [
  18:     {
  19:       id                                     = "abort-incomplete-multipart-upload-after-7days"
  20:       enabled                                = true
  21:       abort_incomplete_multipart_upload_days = 7
  22:       filter_and = null
  23:       expiration = null
  24:       transition = []
  25:       noncurrent_version_transition = []
  26:       noncurrent_version_expiration = null
  27:     },
  28:     {
  29:       id                                     = "delete-non-current-versions-after-30-days"
  30:       enabled                                = true
  31:       abort_incomplete_multipart_upload_days = null
  32:       filter_and = null
  33:       expiration = null
  34:       transition = []
  35:       noncurrent_version_transition = []
  36:       noncurrent_version_expiration = {
  37:         days = 30
  38:       }
  39:     }
  40:   ]

The given value is not suitable for
module.dev-network.module.access_log_bucket.var.lifecycle_configuration_rules
declared at
.terraform\modules\dev-network.access_log_bucket\variables.tf:47,1-41:
element types must all match for conversion to list.

If we see the variable declaration for this module, it has the following type -

variable "lifecycle_configuration_rules" {
  type = list(object({
    enabled = bool
    id      = string

    abort_incomplete_multipart_upload_days = number

    # `filter_and` is the `and` configuration block inside the `filter` configuration.
    # This is the only place you should specify a prefix.
    filter_and = any
    expiration = any
    transition = list(any)

    noncurrent_version_expiration = any
    noncurrent_version_transition = list(any)
  }))
  default     = []
  description = <<-EOT
    A list of S3 bucket v2 lifecycle rules, as specified in [terraform-aws-s3-bucket](https://github.com/cloudposse/terraform-aws-s3-bucket)"
    These rules are not affected by the deprecated `lifecycle_rule_enabled` flag.
    **NOTE:** Unless you also set `lifecycle_rule_enabled = false` you will also get the default deprecated rules set on your bucket.
    EOT
}

Turns out that the problem is with the noncurrent_version_expiration property. As you can see, I have 2 rules and in rule, I have set this property but in the other, I have kept it as null.

This is exactly what Terraform is complaining about (really weird error!). As soon as I changed the noncurrent_version_expiration to {} instead of null, terraform plan worked.

Working piece -

module "access_log_bucket" {
  source  = "cloudposse/lb-s3-bucket/aws"
  version = "~> 0.16.4"

  context = module.access_log_bucket_label.context
  tags    = module.access_log_bucket_label.tags

  versioning_enabled = true
  lifecycle_configuration_rules = [
    {
      id                                     = "abort-incomplete-multipart-upload-after-7days"
      enabled                                = true
      abort_incomplete_multipart_upload_days = 7
      filter_and = null
      expiration = null
      transition = []
      noncurrent_version_transition = []
      noncurrent_version_expiration = {}
    },
    {
      id                                     = "delete-non-current-versions-after-30-days"
      enabled                                = true
      abort_incomplete_multipart_upload_days = null
      filter_and = null
      expiration = null
      transition = []
      noncurrent_version_transition = []
      noncurrent_version_expiration = {
        days = 30
      }
    }
  ]
}

For almost an year I have been working on a Trading bot which does all the shenanigans of placing orders, checking them, creating stop loss orders as per my strategies.
Since this was a personal project, I wanted to keep the costs as low as possible and hence decided to use Azure Functions (Azure has a very generous free tier for Azure Functions) along with Azure Storage Account File Shares to save persistent data. Because of the free tier, I run my code for free and I have to shell out few Rupees for data storage.

I also decided to use SQLite as my database because during the time of starting, I checked out few managed databases but they were not in my budget and hosting my own database meant too much operational overhead.

This database kept on working fine until I added more strategies which started delaying the execution of the Functions by several minutes which started causing irregularities as compared to the backtest. Also, the performance issue is because whenever the Function decides to read from this database, it has to query Azure Files which is not meant for very fast transactions.

This is when I decided to switch over to a self hosted Postgresql database hosted in a droplet from DigitalOcean. (Now, my bot is managing decent money so decided that it is worth the switch).

As I was using Entity Framework for all my database operations, I switched the following -

builder.Services.AddDbContext<BotDbContext>(options =>
                options
                .EnableDetailedErrors()
                .UseSqlite(dbConnectionString)
            );

to

builder.Services.AddDbContext<BotDbContext>(options =>
                options
                .EnableSensitiveDataLogging(true)
                .EnableDetailedErrors()
                .UseNpgsql(dbConnectionString)
            );

I was expecting this to work without any issues but as soon as my bot executed one strategy while testing, I got the following -

[2023-12-15T07:19:51.956Z] Host started (1287ms)
[2023-12-15T07:19:51.959Z] Job host started
[2023-12-15T07:19:55.326Z] Host lock lease acquired by instance ID '00000000000000000000000094310C57'.
[2023-12-15T07:20:28.563Z] Executing HTTP request: {
[2023-12-15T07:20:28.567Z]   requestId: "3cff1941-7ca2-4b8f-9cb4-68f05ef6ea19",
[2023-12-15T07:20:28.571Z]   method: "POST",
[2023-12-15T07:20:28.573Z]   userAgent: "PostmanRuntime/7.36.0",
[2023-12-15T07:20:28.574Z]   uri: "/admin/functions/Strangle"
[2023-12-15T07:20:28.576Z] }
[2023-12-15T07:20:29.184Z] Executed HTTP request: {
[2023-12-15T07:20:29.187Z]   requestId: "3cff1941-7ca2-4b8f-9cb4-68f05ef6ea19",
[2023-12-15T07:20:29.189Z]   identities: "(WebJobsAuthLevel:Admin, WebJobsAuthLevel:Admin)",
[2023-12-15T07:20:29.191Z]   status: "202",
[2023-12-15T07:20:29.193Z]   duration: "617"
[2023-12-15T07:20:29.195Z] }
[2023-12-15T07:20:29.756Z] Executing 'Strangle' (Reason='This function was programmatically called via the host APIs.', Id=fc03253f-50f3-4622-a840-df60c3f5b142)
[2023-12-15T07:20:34.307Z] Strangle function started at: 15-12-2023 12:50:34
[2023-12-15T07:20:46.610Z] Executed 'Strangle' (Failed, Id=fc03253f-50f3-4622-a840-df60c3f5b142, Duration=17396ms)
[2023-12-15T07:20:46.614Z] System.Private.CoreLib: Exception while executing function: Strangle. Microsoft.EntityFrameworkCore: A second operation was started on this context instance before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913.

That's strange.

I have seen this issue and if you also see here, it states that there are multiple operations running on the same DbContext before the previous ones are completed. This means that there is an await missing for an async function call.

You know what this calls for? Debugging step by step to see where it is missing. Within minutes, I found the offending code block -

var instrumentFromMasterList = _dbContext.Instruments
                    .Where(x => x.TradingSymbol.ToLower() == tradingSymbol.ToLower())
                    .Where(x => x.Exchange.ToLower() == exchange.ToLower())
                    .SingleOrDefaultAsync();

You see that I am calling the SingleOrDefaultAsync but the call is not awaited? After adding the await, the code started working as expected.

Now, onto why this was not happening with SQLite. Turns out, by default, SQLite is compiled with the Serialized mode where multiple calls are queued and executed one by one. Whereas for Postgresql, this is not the case and hence Entity Framework started complaining.

Till next time!

[2023-12-14T11:26:50.419Z] Executed 'LoginDumper' (Failed, Id=51a219ad-31f0-4477-9c36-cf06ad8efcbe, Duration=5100ms)
[2023-12-14T11:26:50.429Z] System.Private.CoreLib: Exception while executing function: LoginDumper. Npgsql: 42P01: relation "helloworld" does not exist
[2023-12-14T11:26:50.433Z]
[2023-12-14T11:26:50.436Z] POSITION: 13.

This is a post for myself because I know that I am going to forget this again. I started getting the above message for the following command even though I can see the table existing in pgAdmin with the exact same case -

await _dbContext.Database.ExecuteSqlRawAsync("DELETE FROM HelloWorld;");

Turns out, in PostgreSQL world, if you don't double quote the name of the table, or even the name of the columns, it will automatically change it to lowercase and since the database engine itself is case-sensitive, it results in the above error message.

This is pretty surprising for me since I come from the Microsoft SQL Server world where this won't be an issue.

Changing the above statement to the following fixed the issue -

await _dbContext.Database.ExecuteSqlRawAsync("DELETE FROM \"HelloWorld\";");

On the bright side, Entity Framework Core has introduced bulk deletions and updates (Source) so I only have to deal with this till I don't upgrade my project to use the latest EF Core.

Quick post as always!

I was having a lot of trouble with my Audeze Mobius device not working when connecting to a particular laptop as it was working fine over Bluetooth and USB when connected to other devices.

The problem was that the system was recognizing that the Mobius was connected and everything was showing as that was the default device for sound and communications but still no sound!

After opening the Sounds panel and clicking on Test button, I got the Unable to play test tone.

After trying various things like changing the Audio service's Log On account and all, it was still not working.

Finally, I decided to roll back the Audio driver since the last update I was seeing was back in 2022.

I went into

Sounds -> Right Click Audeze Mobius -> General -> Properties (Under Controller Information) -> Change Settings With UAC (If you see this) -> Driver Tab -> Rollback Driver.

As soon as I did this, the audio started working!

Link to the library - https://search.maven.org/artifact/com.microsoft.azure/azure-eventhubs-spark_2.12/2.3.21/jar

Whenever I was trying to install the library from Maven, it was giving me the following error -

Library resolution failed. Cause: java.lang.RuntimeException: javax.mail:mail download failed.
at com.databricks.libraries.server.MavenInstaller.$anonfun$resolveDependencyPaths$5(MavenLibraryResolver.scala:275)
at scala.collection.immutable.HashMap$HashTrieMap.getOrElse0(HashMap.scala:596)
at scala.collection.immutable.HashMap$HashTrieMap.getOrElse0(HashMap.scala:589)
at scala.collection.immutable.HashMap.getOrElse(HashMap.scala:73)
at com.databricks.libraries.server.MavenInstaller.$anonfun$resolveDependencyPaths$4(MavenLibraryResolver.scala:275)
at scala.collection.TraversableLike.$anonfun$map$1(TraversableLike.scala:286)
at scala.collection.mutable.ArraySeq.foreach(ArraySeq.scala:75)
at scala.collection.TraversableLike.map(TraversableLike.scala:286)
at scala.collection.TraversableLike.map$(TraversableLike.scala:279)
at scala.collection.AbstractTraversable.map(Traversable.scala:108)
at com.databricks.libraries.server.MavenInstaller.resolveDependencyPaths(MavenLibraryResolver.scala:271)
at com.databricks.libraries.server.MavenInstaller.doDownloadMavenPackages(MavenLibraryResolver.scala:481)
at com.databricks.libraries.server.MavenInstaller.$anonfun$downloadMavenPackages$3(MavenLibraryResolver.scala:400)
at com.databricks.backend.common.util.FileUtils$.withTemporaryDirectory(FileUtils.scala:468)
at com.databricks.libraries.server.MavenInstaller.$anonfun$downloadMavenPackages$2(MavenLibraryResolver.scala:399)
at com.databricks.logging.UsageLogging.$anonfun$recordOperation$1(UsageLogging.scala:366)
at com.databricks.logging.UsageLogging.executeThunkAndCaptureResultTags$1(UsageLogging.scala:460)
at com.databricks.logging.UsageLogging.$anonfun$recordOperationWithResultTags$4(UsageLogging.scala:480)
at com.databricks.logging.UsageLogging.$anonfun$withAttributionContext$2(UsageLogging.scala:232)
at scala.util.DynamicVariable.withValue(DynamicVariable.scala:62)
at com.databricks.logging.AttributionContext$.withValue(AttributionContext.scala:94)
at com.databricks.logging.UsageLogging.withAttributionContext(UsageLogging.scala:230)
at com.databricks.logging.UsageLogging.withAttributionContext$(UsageLogging.scala:212)
at com.databricks.libraries.server.MavenInstaller.withAttributionContext(MavenLibraryResolver.scala:61)
at com.databricks.logging.UsageLogging.withAttributionTags(UsageLogging.scala:276)
at com.databricks.logging.UsageLogging.withAttributionTags$(UsageLogging.scala:261)
at com.databricks.libraries.server.MavenInstaller.withAttributionTags(MavenLibraryResolver.scala:61)
at com.databricks.logging.UsageLogging.recordOperationWithResultTags(UsageLogging.scala:455)
at com.databricks.logging.UsageLogging.recordOperationWithResultTags$(UsageLogging.scala:375)
at com.databricks.libraries.server.MavenInstaller.recordOperationWithResultTags(MavenLibraryResolver.scala:61)
at com.databricks.logging.UsageLogging.recordOperation(UsageLogging.scala:366)
at com.databricks.logging.UsageLogging.recordOperation$(UsageLogging.scala:338)
at com.databricks.libraries.server.MavenInstaller.recordOperation(MavenLibraryResolver.scala:61)
at com.databricks.libraries.server.MavenInstaller.downloadMavenPackages(MavenLibraryResolver.scala:398)
at com.databricks.libraries.server.MavenInstaller.downloadMavenPackagesWithRetry(MavenLibraryResolver.scala:153)
at com.databricks.libraries.server.MavenInstaller.resolveMavenPackages(MavenLibraryResolver.scala:117)
at com.databricks.libraries.server.MavenLibraryResolver.resolve(MavenLibraryResolver.scala:48)
at com.databricks.libraries.server.ManagedLibraryManager$GenericManagedLibraryResolver.resolve(ManagedLibraryManager.scala:252)
at com.databricks.libraries.server.ManagedLibraryManagerImpl$.$anonfun$resolvePrimitives$1(ManagedLibraryManagerImpl.scala:1226)
at com.databricks.libraries.server.ManagedLibraryManagerImpl$.$anonfun$resolvePrimitives$1$adapted(ManagedLibraryManagerImpl.scala:1221)
at scala.collection.Iterator.foreach(Iterator.scala:943)
at scala.collection.Iterator.foreach$(Iterator.scala:943)
at scala.collection.AbstractIterator.foreach(Iterator.scala:1431)
at scala.collection.IterableLike.foreach(IterableLike.scala:74)
at scala.collection.IterableLike.foreach$(IterableLike.scala:73)
at scala.collection.AbstractIterable.foreach(Iterable.scala:56)
at com.databricks.libraries.server.ManagedLibraryManagerImpl$.resolvePrimitives(ManagedLibraryManagerImpl.scala:1221)
at com.databricks.libraries.server.ManagedLibraryManagerImpl$ClusterStatus.installLibsWithResolution(ManagedLibraryManagerImpl.scala:723)
at com.databricks.libraries.server.ManagedLibraryManagerImpl$ClusterStatus.installLibs(ManagedLibraryManagerImpl.scala:709)
at com.databricks.libraries.server.ManagedLibraryManagerImpl$InstallLibTask$1.run(ManagedLibraryManagerImpl.scala:390)
at com.databricks.threading.NamedExecutor$$anon$2.$anonfun$run$1(NamedExecutor.scala:359)
at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
at com.databricks.logging.UsageLogging.$anonfun$withAttributionContext$2(UsageLogging.scala:232)
at scala.util.DynamicVariable.withValue(DynamicVariable.scala:62)
at com.databricks.logging.AttributionContext$.withValue(AttributionContext.scala:94)
at com.databricks.logging.UsageLogging.withAttributionContext(UsageLogging.scala:230)
at com.databricks.logging.UsageLogging.withAttributionContext$(UsageLogging.scala:212)
at com.databricks.threading.NamedExecutor.withAttributionContext(NamedExecutor.scala:287)
at com.databricks.threading.NamedExecutor$$anon$2.run(NamedExecutor.scala:358)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)

After checking all the Firewall rules, the support rep from Microsoft said that it was working on his cluster.

So, in the end, the solution was to simply delete the cluster and recreate it. This is the first time I have seen the old adage "Reboot or Recreate" work.

Till next time!

Azure Storage Emulator is an important piece of my developer toolkit and I recently got a new laptop from work and while I was getting it setup, I installed the Azure Storage Emulator from the official download page over here.

You could argue why I am not using the latest Azurite which is now recommended by Microsoft. But, last time (2-3 months back) I tried it, I ran into issues while trying to run Azure Durable Functions against it since the Table API didn't support all the features. Additionally what I like the most with the Storage Emulator is that it comes as an MSI file so after installation, I know exactly where it is located.

As usual, I installed it and started it only to be greeted with the following -

C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>AzureStorageEmulator.exe start
Windows Azure Storage Emulator 5.10.0.0 command line tool
Autodetect requested. Autodetecting SQL Instance to use.
Looking for a LocalDB Installation.
Probing SQL Instance: '(localdb)\MSSQLLocalDB'.
Found a LocalDB Installation.
Probing SQL Instance: '(localdb)\MSSQLLocalDB'.
Found SQL Instance (localdb)\MSSQLLocalDB.
Creating database AzureStorageEmulatorDb510 on SQL instance '(localdb)\MSSQLLocalDB'.
Cannot create database 'AzureStorageEmulatorDb510' : The database 'AzureStorageEmulatorDb510' does not exist. Supply a valid database name. To see available databases, use sys.databases..
One or more initialization actions have failed. Resolve these errors before attempting to run the storage emulator again.
Error: The storage emulator needs to be initialized. Please run the 'init' command.

Ideally, it should be creating the database and then populating the schema but it wasn't doing that. I then tried running the init command manually like it said and got -

C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator> AzureStorageEmulator.exe init
Windows Azure Storage Emulator 5.10.0.0 command line tool
Found SQL Instance (localdb)\MSSQLLocalDB.
Creating database AzureStorageEmulatorDb510 on SQL instance '(localdb)\MSSQLLocalDB'.

Granting database access to user LOCAL\Pranav.Jituri.
Database access for user LOCAL\Pranav.Jituri was granted.

Initialization successful. The storage emulator is now ready for use.
The storage emulator was successfully initialized and is ready to use.

I then started it again and got the following -

C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator> AzureStorageEmulator.exe start /inprocess
Windows Azure Storage Emulator 5.10.0.0 command line tool
Invalid object name 'dbo.Account'.
Service Status: Blob http://127.0.0.1:10000/ True
Service Status: Queue http://127.0.0.1:10001/ True
Service Status: Table http://127.0.0.1:10002/ True

That gave me a clue to check the database and I didn't see any schema objects which it generally has.

After troubleshooting for quite some time, I gave up and just decided to get the DACPAC export of the database from a colleague and import the DACPAC. As soon as the DACPAC was restored, the Storage Emulator started working.

You can download the DACPAC directly from here.

It has been a really, really long time since I have written a blog post. This blog post talks about a recent problem which I encountered, forgot to write about on how I solved it and it bit me back again after some time! Reminder to all of you who are able to solve issues but don't document them!

The Problem

One fine day, I start debugging an Azure Functions project by starting the Azure Storage Emulator and I am greeted with this -

PS C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator> .\AzureStorageEmulator.exe start -inprocess
Windows Azure Storage Emulator 5.10.0.0 command line tool
Service Status: Blob http://127.0.0.1:10000/ False
Access is denied
Error: Unable to start the storage emulator.
PS C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>

This was pretty strange as I checked which process was trying to use this port using netstat and I didn't see any entries -

I then went ahead and tried starting the Azure Functions project and it also threw the same error that Port 7071 is blocked and access was denied to it. This was very weird because I didn't have any applications running on that port & I also tried running the application with Administrator privileges. I tried running the Azure Functions project using a different port as well but it was also blocked. I also tried running Apache using XAMPP on various ports. It worked on some and it failed with the same port access blocked message on the others.

The Troubleshooting

After running the usual netstat commands, I thought that maybe it could be the Windows Firewall which might have some issue and it decided to block those ports. I turned on Windows Firewall logging and I didn't see any blockings over there as well. I then turned towards Event Viewer to see if there is any exception which is being generated in the Administrative Logs.

To my surprise, I found the port blocking event being generated i.e. Event 15005 HttpEvent with the following message -

Unable to bind to the underlying transport for 127.0.0.1:10000. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.

After searching around for quite a bit, I came across this Github link. This talks about the Dynamic Port range reservations which can be used by other services to block ports. I ran netsh int ipv4 show dynamicport tcp and the following list popped -

PS D:\> netsh interface ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges

Start Port    End Port
----------    --------
      1542        1641
      1742        1841
      1842        1941
      2280        2379
      2557        2656
      2682        2781
      2782        2881
      2882        2981
      2982        3081
      3082        3181
      3182        3281
      3282        3381
      3390        3489
      3490        3589
      3590        3689
      3690        3789
      3790        3889
      3990        4089
      4090        4189
      4243        4342
      4343        4442
      4443        4542
      4843        4942
      5043        5142
      5143        5242
      5243        5342
      5443        5542
      5943        6042
      6143        6242
      6243        6342
      6343        6442
      6543        6642
      7143        7242
      7343        7442
      7443        7542
      7543        7642
      7743        7842
      8443        8542
      8643        8742
      8743        8842
      8843        8942
      9043        9142
      9143        9242
      9243        9342
      9343        9442
      9443        9542
      9543        9642
      9643        9742
      9743        9842
      9848        9947
      9948       10047
     10048       10147
     10148       10247
     10248       10347
     10348       10447
     10448       10547
     50000       50059     *

* - Administered port exclusions.

As you can see, the port 10000 was in the range of ports blocked. I confirmed this theory by running Apache on the various ports. As expected, it turned out that if I tried running Apache on the ports which are in the list (& range) above, it failed. On ports other than that, it worked without any issue.

The Solution

The solution which worked for me was to remove Hyper-V, reserve the port for Hyper-V and then re-enable it.

1. Disable hyper-v (which will required a couple of restarts).
   Do note that disabling and removing Hyper-V will mean that all your Virtual Machines & other objects part of Hyper-V will be removed.
   dism.exe /Online /Disable-Feature:Microsoft-Hyper-V

2. When you finish all the required restarts, reserve the port you want so hyper-v doesn't reserve it back
   netsh int ipv4 add excludedportrange protocol=tcp startport=50051 numberofports=1

3. Re-Enable hyper-V (which will require a couple of restart)
   dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All

Credit - https://github.com/docker/for-win/issues/3171#issuecomment-459205576

After rebooting after the 3rd step, my system was back to normal and the above problems were resolved.