Object.keys(request)
- ashley/ceej
BLUEBIRD_LONG_STACK_TRACES=1
- chris
(ooh, just remembered another tip: kill -s USR1 <node pid>
will turn the debugger on any node process and you can point node-inspector
at it) -chris
ooh another fun debugging tip: dbg = vm.runInDebugContext('Debug'); mirror = dbg.MakeMirror(objectValue); console.log(mirror.referencedBy())
- chris it lists all referencing objects to the object you pass to MakeMirror
turn on browser styles in computed properties in the browser - jeff
git token search aria
maciej when in doubt strace
tcpdump
dtruss
git bisect
+ use magic strings and/or really unique tokens "wacky symbols" ryan
ben docker container, just sh into it to debug it
andrew - if you're running enterprise and your ldap is not working making sure replicated has the right ip
ceej
- start at the wall socket and follow the cables all the way through. methodically start where something starts and follow it all the way through meticulously and pedanticly. don't make the assumption!
- log, log profusely, log often, log in a grepable way. you write logs now to save yourself debuging time later. current self needs to guess what might go wrong in the future
- name your functions! your stack traces are WAY better.
tl;dr BE DESCRIPTIVE. have pity on yourself.
process._rawDebug
— blocking write to stderr that skips all stream machinery