As usual, keep having to google this, so finally writing it down here…
git reset HEAD~ and make new commits as needed.
Commit further back
- Perform an interactive rebase (e.g.
git rebase -i main), and change the commit from
- Reset the commit with
git reset HEAD~.
- Make new commits as needed.
- Complete the rebase with
git rebase --continue
Sometimes curious about this, usually because I forgot to note what time I arrived at the office, and I keep forgetting how to check. So, here’s some commands I found on SuperUser which seem to do the trick:
> systeminfo | find /i "Boot Time"
System Boot Time: 15.10.2021, 08:37:29
> wmic os get lastbootuptime
> net statistics workstation | find /i "Statistics since"
Statistics since 15.10.2021 08:37:45
Also discovered this one, which will create a more thorough report, which can be interesting to look at:
> powercfg /sleepstudy /output report.html && start report.html
Testing your web projects with a screen reader is quite important and informative, but can also be quite annoying while jumping back and forth between developing and testing. Here are some shortcuts I keep forgetting to make NVDA a bit less annoying during development:
||Stops current reading
|Ins + S
||Switches between off-, sound-, and speech-mode (while stuff keeps being listed in log and braille view
|Ins + Q
Experienced getting fatal build errors on our build server during ESLint linting of our React project:
<--- Last few GCs --->
[10012:0000000001DA2080] 184320 ms: Mark-sweep 2035.1 (2051.8) -> 2034.3 (2051.8) MB, 2297.9 / 0.0 ms (average mu = 0.114, current mu = 0.001) allocation failure scavenge might not succeed
[10012:0000000001DA2080] 185393 ms: Mark-sweep 2035.3 (2051.8) -> 2033.6 (2051.8) MB, 1068.8 / 0.0 ms (average mu = 0.077, current mu = 0.003) allocation failure scavenge might not succeed
The MB values looked very suspicious in that they were on either side of 2048 MB (2 GB), so suspected our project had run into some sort of limit. And seems there is indeed a max limit of ~2 GB by default on the heap size.
To increase the node heap size limit, set the
--max-old-space-size to something more than 2048, e.g. like this on Windows:
setx NODE_OPTIONS "--max-old-space-size=4096" /m
To verify that it actually works (or check what it is by default), this command seems to do it:
node -e "console.log(require('v8').getHeapStatistics().total_available_size / 1024 / 1024)"
Note that the output for some reason always seem to be a bit more than what’s set as the limit. Not sure what that’s about, but anyways… ðŸ¤·â€â™‚ï¸
For debugging it’s often useful to do
console.log(someObjectOrArray). However, if the array is long or the object deep, a lot will be truncated. Apparently there’s a util one can use to get a bit more control over this though:
import util from 'util'