Category Archives: Uncategorized

fried pumpkin cakes – a three ingredient dessert

i had a lot of pumpkin cakes when i went to china, 南瓜饼

around pumpkin season in the US (you know when the pumpkin spice starts appearing), I started having cravings

pics from 2 Oct 2021
the three ingredients

I followed recipe from

Chinese Pumpkin cakes 南瓜饼 (Nan Gua Bing)

basically, 400g puree, 300g glutinous rice flour (from market basket), 40g sugar, mix it all together, divide into patties and fry

note 1: fold flour in a bit at a time

note 2: though in my case I used more rice flour than 300g because it was too sticky (I think the canned puree is more watery than IRL puree?),

here’s some pictures of my process

note: you can see different variations of the recipe in chinese here

virtual environment python not found / can’t be selected on vs code

quick note to self:

for my environment I usually set it up in a random folder (most people seem to set it up in ~/.env) and vscode has difficulty finding it

(in which case it keeps saying “Running cell with Python xxxx 64-bit requires ipykernel package” since I only install my packages in my virtualenv)

Here is how I solved it:

Put in the User settings (in this case I’m working remotely (via remote ssh extension) but applies locally too)

And then put a defaultInterpreterPath into the settings

    // "python.pythonPath": "~/v3/bin/python",
    "python.terminal.activateEnvironment": true,
    "python.defaultInterpreterPath": "~/v3/bin/python",

And then it shows up when I change the kernel (see third option):


May require a .vscode folder (with empty settings.json) in the parent repository?

setting up ssh on different port, changes for ubuntu 22.10+ (connection refused error)

skip to “the new way” for how to do so

as it turns out… on ubuntu 22.10 and onward stops using the config file for ports…

so the old way was

vi /etc/ssh/sshd_config

and literally one line in there, “Port 2077”

(I also do PubkeyAuthentication yes, PasswordAuthentication no, UsePAM yes — I think the first and third settings are actually the default settings, so only need to disable password and add in port).

sudo service ssh restart

and just append your pubkeys to ~/.ssh/authorized_keys

so on reboot switched back to old port. I was using say 2077.

netstat | grep 2077

no services listed.

I got clued into this using sudo service ssh status and it said

$ sudo service ssh status

Oct 31 15:58:54 sffpc systemd[1]: Starting OpenBSD Secure Shell server…
Oct 31 15:58:54 sffpc sshd[6683]: Server listening on :: port 22.

And I went back to /etc/ssh/sshd_config and saw the lines

14 # Port and ListenAddress options are not used when sshd is socket-activated,
15 # which is now the default in Ubuntu. See sshd_config(5) and
16 # /usr/share/doc/openssh-server/README.Debian.gz for details.

you can also

the docs

vi /usr/share/doc/openssh-server/README.Debian.gz


The provided ssh.socket unit file sets ListenStream=22.  If you need to have
it listen on a different address or port, then you will need to do this as
follows (modifying ListenStream to match your requirements):

  mkdir -p /etc/systemd/system/ssh.socket.d
  cat >/etc/systemd/system/ssh.socket.d/listen.conf <<EOF
  systemctl daemon-reload

See systemd.socket(5) for details.

tl;dr the new way

Okay, so what I actually did was just edit the file with vi (you can use nano) since I was having issues with bash balking at creating the file etc.

$ sudo mkdir -p /etc/systemd/system/ssh.socket.d
$ sudo vi /etc/systemd/system/ssh.socket.d/listen.conf 
$ sudo service ssh reload
And now I can ssh from another computer yay!


I think in the future I will just use the default port. too much headache.


131 sudo ufw status
132 sudo ufw enable

130 sudo ufw allow ssh

160 sudo ufw default deny incoming
746 sudo ufw default allow outgoing

174 sudo ufw allow 2077

179 sudo ufw delete allow 22
180 sudo ufw status
181 sudo ufw delete allow 22/tcp

749 sudo ufw reload


journaltcl -u ssh


also have to set up port forwarding on router.

WAN -> virtual server /port forwarding. Add profile: Protocol TCP, external port 20whatever, internal port 2077, Internal IP (find your computer on the list of stuff connected to router)

get external ip


side note

on mac was getting

debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling

this was red herring; if it gets to “connection refused” that means we were able to make contact with the server, and it’s something on the server side.