Given that this was only a 13 degree at highest elevation, the first of these decodes is pretty good:


Articles, notes and random thoughts on Software Development and Technology
Given that this was only a 13 degree at highest elevation, the first of these decodes is pretty good:
Here’s my decodes from the 12/27/21/ 09:51 ISS 60 degree highest elevation pass:
If you’ve committed a number of git commits using a wrong user.name or user.email value, you can re-write previous commits with:
git filter-branch --commit-filter ' if [ "$GIT_COMMITTER_NAME" = "Old Name" ]; then GIT_COMMITTER_NAME="new-name"; GIT_AUTHOR_NAME="new-name"; GIT_COMMITTER_EMAIL="new-email"; GIT_AUTHOR_EMAIL="new-email"; git commit-tree "$@"; else git commit-tree "$@"; fi' HEAD
Note that this will re-write all commits on the current branch matching the if condition which may or may not be what you’re looking for, so be careful. push the changes back to your remote origin as needed.
This is based on answers to this question here.
I just started getting this error starting up my React app locally with ‘npm run start’ :
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ], library: 'digital envelope routines', reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED'
I recently installed nvm on my Mac to avoid needing sudo for running a ‘npm i -g’, and also apparently picked up the latest stable node version and not lts.
Running ‘nvm ls’ to see what version I have and what’s available:
> nvm ls -> v17.3.0 system default -> node (-> v17.3.0)
According to https://nodejs.org/en/download/current/ 17.3.0 is the latest current and not lts. Answers to this related question suggested switching back to lts to avoid this change.
Following the nvm docs :
nvm install -lts nvm use --lts
Now I’ve back at version 16.13.1, and my React app with ‘npm run start’ now starts as expected.