add info about what can happen in darkwake here
- observed when a machine has the lid shit and AC power is plugged in
DarkWake from Normal Sleep [CDN] due to EC.ACAttach/Maintenance: Using AC (Charge:60%) 45 secs
λ pnpm store prune | |
Removed all cached metadata files | |
Removed 207979 files | |
Removed 4560 packages | |
λ pnpm i | |
Lockfile is up to date, resolution step is skipped | |
Already up to date | |
Done in 674ms | |
λ rm -rf node_modules | |
λ pnpm i |
<!DOCTYPE html> | |
<html> | |
<head> | |
<title>FXHASH project</title> | |
<meta charset="utf-8"> | |
<script id="fxhash-snippet"> | |
//---- do not edit the following code (you can indent as you wish) | |
let alphabet = "123456789abcdefghijkmnopqrstuvwxyzABCDEFGHJKLMNPQRSTUVWXYZ" | |
var fxhash = "oo" + Array(49).fill(0).map(_=>alphabet[(Math.random()*alphabet.length)|0]).join('') | |
let b58dec = str=>[...str].reduce((p,c)=>p*alphabet.length+alphabet.indexOf(c)|0, 0) |
I am attesting that this GitHub handle shuhblam is linked to the Tezos account tz1b37erGvRoFPXBuz1DKyZwdKsxMbyt8eq1 for tzprofiles | |
sig:edsigtrAsWAMYRbD9fgEu6wPcG8T9tJ4cWpvynLXid63TFja6FkagQDT4iAJJ8355RWhwgykqTR9shtnqez7NPYBYE8kFEiovXQ |
I am attesting that this GitHub handle shuhblam is linked to the Tezos account tz1b37erGvRoFPXBuz1DKyZwdKsxMbyt8eq1 for tzprofiles | |
sig:edsigtrAsWAMYRbD9fgEu6wPcG8T9tJ4cWpvynLXid63TFja6FkagQDT4iAJJ8355RWhwgykqTR9shtnqez7NPYBYE8kFEiovXQ |
# comments example for .dat or .ledger files | |
@smallexample | |
; This is a single line comment, | |
# and this, | |
% and this, | |
| and this, | |
* and this. | |
# If you have a deeply nested tree of accounts, | |
# it may be convenient to define an alias, for example: |
There are a few chrome extensions that will tell you the total count of your angular $$watchers
but in order to narrow down the problem areas I needed more insight into which elements were causing problems. This script helped me by giving me the ability to:
$$watchers
$$watchers
for any element including all of it's descendants$$watchers
for the current documentElementFor debugging I recommend using chrome snippets. Paste the watcher.js
script into a new snippet, save it and then run it. Once you load the snippet you can call any functions it loaded directly from the console as many times as you want.
Authored by Peter Rybin , Chrome DevTools team
In this short guide we'll review some new Chrome DevTools features for "function scope" and "internal properties" by exploring some base JavaScript language concepts.
Let's start with closures – one of the most famous things in JS. A closure is a function, that uses variables from outside. See an example:
driver.executeAsyncScript(function() { | |
var callback = arguments[arguments.length - 1]; | |
window.onload = function() { | |
callback() | |
}; | |
}).then(function() { | |
//do stuff here | |
}); |
var MongoClient = require('mongodb').MongoClient, | |
bunyan = require('bunyan'), | |
log = bunyan.createLogger({ | |
name: 'harvest' | |
}); | |
request = require('request') | |
var url = 'mongodb://localhost:27017/openNews'; | |
MongoClient.connect(url, function(err, db) { |