Skip to content

Instantly share code, notes, and snippets.

View christopher-francisco's full-sized avatar

Christopher Francisco christopher-francisco

  • United Kingdom
View GitHub Profile
<--- Last few GCs --->
[60:0x2d616e0] 513409 ms: Mark-sweep 1338.6 (1439.9) -> 1338.6 (1439.9) MB, 1572.6 / 0.2 ms allocation failure GC in old space requested
[60:0x2d616e0] 515008 ms: Mark-sweep 1338.6 (1439.9) -> 1338.6 (1436.9) MB, 1595.9 / 0.2 ms last resort GC in old space requested
[60:0x2d616e0] 516620 ms: Mark-sweep 1338.6 (1436.9) -> 1338.6 (1436.9) MB, 1611.9 / 0.2 ms last resort GC in old space requested
<--- JS stacktrace --->
==== JS stack trace =========================================
export default {
getCustomers(port) {
return fetch(`http://localhost:${port}`)
.then(response => response.json())
},
};
@christopher-francisco
christopher-francisco / resolve-lock-conflict.sh.example
Created March 21, 2018 16:09
Resolving conflicts on `.lock` files after rebase/merge
# Taken from https://github.com/yarnpkg/yarn/issues/1776#issuecomment-269539948
#
# 1. checkout the `.lock` file to the main branch’s one
# 2. run the install command on your package manager
# 3. it will update the `.lock` file, starting off the main branch’s one
# 4. commit the new `.lock` file
git checkout [branch with base yarn.lock] -- yarn.lock
yarn install
git add yarn.lock

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname