Keybase push -update error when trying to sign our own key. Or is this a bug?

Screenshot 1: http://pub.robinmathewrajan.com/keybase/keybase_error_1.png

When researched for similar issues, at one thread, @maxtaco suggested revoking the key. I did that and tried to push the local key with 'keybase push' command. But it didn't work either. The pinentry dialogue box doesn't appear.

Failing all those methods, I generated a new key pair in the browser using keybase.io. Later, I removed the newly generated key pair to upload my already established public key.

It's still failing when I gave the 'keybase -push' command with error code 2.

Screenshot 2: http://pub.robinmathewrajan.com/keybase/keybase_error_2.png

Why is this happening and the solution?

My computer configuration:
Windows 7 SP1 x64,
Gpg4win 2.2.4,
Node v0.12.2 x64,

My gpg.conf file: https://gist.github.com/RobinMathewRajan/d9b57baac62262d9e035

Thanks,
Robin Mathew Rajan
Keybase.io: https://keybase.io/robinmathewrajan
Blog: https://www.robinmathewrajan.com/ramblings/
Portfolio: https://www.robinmathewrajan.com/

Start by reviewing the two linked screenshots, the supplied gpg.conf, and the reported keybase -push and keybase push behavior on the listed Windows 7, Gpg4win, and Node versions. Reproduce the missing pinentry dialog and error code 2; done means identifying the cause and documenting a working solution.