brew install Pillow

Don’t bother with pip, it won’t work. It looks like it’s worked, and it installs something, somewhere, but it hasn’t worked.

I’ve been battling with MacOS writing all sorts of crap onto external drives, and having difficulties ejecting them because some unknown process has files open on the drive.

This seems to be a difinitive way of getting MacOS to ignore external drives in it’s never ending quest to create as many files as possible:

touch /Volumes/<volume>/.metadata_never_index

Once you’ve done this you may also want to delete the .Spotlight-V100 directory from the volume.

• Get the Vice C64 emulator - https://vice-emu.sourceforge.io
• Unpack the archive
• Locate the bin/c1541 executable, this is a C64 disk image maintenance utility
• Use the following command, adjusted for your own case:

  ./c1541 -format disk1,id d64 "somefilename.d64" -attach disk1.d64 -write somefilename.prg "Some File Name"
  

Useful link:

• https://vice-emu.sourceforge.io/vice_14.html

Error:

YN0001: │ RequestError: self-signed certificate in certificate chain

Fix:

In ~/.yarnrc.yaml or equivaqlent:

enableStrictSsl: false

Caveat - Be aware that this will prevent errors/warnings about unsafe TLS certificates, blah blah. If you’re already at this point you take full responsibility for what you’re doing.

function pwdcc() {
    pwd | tr -d "\n" | xclip -selection clipboard
}

filecc - Copy the full path of to the clipboard:

function filecc() {
    if [ -z $1 ] || [ ! -f $1 ]
    then
        echo Give me a file you dummy
        return 1
    fi
    readlink -f $1 | tr -d "\n" | xclip -selection clipboard
}

These should easily be convertable to other shells.

A properly constructed secret for container registry authentication looks like this:

apiVersion: v1
kind: Secret
metadata:
  name: mygreatapp-registry-credentials
  namespace: mygreatapp
data:
  .dockerconfigjson: UmVhbGx5IHJlYWxseSByZWVlZWVlZWVlZWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWxsbGxsbGxsbGxsbGxsbGxsbGxsbGxsbGxsbGxsbGx5eXl5eXl5eXl5eXl5eXl5eXl5eSBsbGxsbGxsbGxsbGxsbG9vb29vb29vb29vb29vb29vb29vb29vb29vb25ubm5ubm5ubm5ubm5ubm5ubm5ubm5ubmdnZ2dnZ2dnZ2dnZ2dnZ2dnZ2cgYXV0aCBrZXlzCg==
type: kubernetes.io/dockerconfigjson

Note the secret type. If you forget to define the correct type Kubernetes will not use the secret as authentication for the image pull.

This small function will strip all carriage return characters out of the file on save:

" Remove any carriage return (^M) characters that may have crept in
" Inspiration - https://stackoverflow.com/q/7495932/4046442
function TrimCarriageReturns()
  let l:save = winsaveview()
  keeppatterns %s/\r\+$//e
  call winrestview(l:save)
endfun
autocmd BufWritePre * call TrimCarriageReturns()

Just add it to your .vimrc.

I came across a weird issue with it recently, the following error at startup : “Plugins load failed!”. It turns out this message is rather misleading, at least in my case.

The problem was actually nothing to do with plugins, but instead stale cached information in ~/.local/share/k9s/clusters after some changes to the remote clusters. Removing everything under this directory fixed the issue.

The k9s logs helped debug this. Find your log location:

k9s info

I’ve been experiementing with Groovy/Jenkins pipeline linters, but they are scant and don’t seem to be that useful.

I found out that Jenkins itself has a couple of development related APIs, one of which will validate a Jenkinsfile and report any issues. So I wrote a vim macro to do this with the current buffer. Saves a lot of time.

let @j = ":w ! curl --silent --insecure --request POST --user '<Jenkins username>:<api token>' --form 'jenkinsfile=<-' 'https://<Jenkins url>/jenkins/pipeline-model-converter/validate'"

Typically you put this macro in your .vimrc.

Replace <Jenkins username>, <api token> and <Jenkins url> with your own values. You may need to remove /jenkins/ from the URL depending on how you’re exposing the app on HTTP.

The Jenkinsfile is read from stdin, see the - in the --form parameter. You can change this to a file in the filesystem if that suits you better.

My Jenkins server runs on a self generated TLS cert, hence the curl --insecure, remove this as necessary.

This has been written and tested for vim running on Linux, but it should work with little modification under Windows/Powershell.