I use a GPG key to sign my git commits.
An error like this one might be a sign of an expired GPG key.
error: gpg failed to sign the data fatal: failed to write commit object
| #!/usr/bin/env python3 | |
| # Unicode characters are neatly categorized into different "scripts", as seen on | |
| # the character code chart <http://www.unicode.org/charts/#scripts> and defined | |
| # in Annex #24 <https://www.unicode.org/reports/tr24/>. | |
| # | |
| # Unfortunately, Python's unicodedata module doesn't provide access to this | |
| # information. However, the fontTools library does include this. | |
| # <https://github.com/fonttools/fonttools> | |
| # |
Europe
| n <- 200 | |
| m <- 40 | |
| set.seed(1) | |
| x <- runif(n, -1, 1) | |
| library(rafalib) | |
| bigpar(2,2,mar=c(3,3,3,1)) | |
| library(RColorBrewer) | |
| cols <- brewer.pal(11, "Spectral")[as.integer(cut(x, 11))] | |
| plot(x, rep(0,n), ylim=c(-1,1), yaxt="n", xlab="", ylab="", | |
| col=cols, pch=20, main="underlying data") |
| import sys, marshal, functools, subprocess | |
| child_script = """ | |
| import marshal, sys, types; | |
| fn, args, kwargs = marshal.load(sys.stdin) | |
| marshal.dump( | |
| types.FunctionType(fn, globals())(*args, **kwargs), | |
| sys.stdout) | |
| """ |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParentL1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns
Compress 1K bytes with Zippy ............. 3,000 ns = 3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns = 20 µs
SSD random read ........................ 150,000 ns = 150 µs
Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs