Open ssl.conf in a text editor.
Edit the domain(s) listed under the [alt_names] section so that they match the local domain name you want to use for your project, e.g.
DNS.1 = my-project.dev
Additional FQDNs can be added if required:
| // License: MIT | |
| package main | |
| import ( | |
| "crypto/rand" | |
| "fmt" | |
| "math/big" | |
| ) | |
| // GenerateRandomASCIIString returns a securely generated random ASCII string. |
this algorithm 10x faster than https://www.dotnetperls.com/duplicates-go and zero allocation
➜ api git:(master) ✗ go test -v -bench=. main_test.go
=== RUN TestSliceUniq
--- PASS: TestSliceUniq (0.00s)
BenchmarkSliceUniq-4 3000000 439 ns/op 0 B/op 0 allocs/op
BenchmarkRemoveDuplicates-4 500000 4599 ns/op 571 B/op 8 allocs/op
PASS
| public class Pager<I, O> { | |
| private static final Observable FINISH_SEQUENCE = Observable.never(); | |
| private PublishSubject<Observable<I>> pages; | |
| private Observable<I> nextPage = finish(); | |
| private Subscription subscription = Subscriptions.empty(); | |
| private final PagingFunction<I> pagingFunction; | |
| private final Func1<I, O> pageTransformer; |
Updated: Just use qutebrowser (and disable javascript). The web is done for.
Moved to GitHub due to requests, see
Branch A has commits (X,Y) that also need to be in Branch B. The cherry-pick operations should be done in the same chronological order that the commits appear in Branch A.
cherry-pick does support a range of commits, but if you have merge commits in that range, it gets really complicated
git checkout branch-B
git cherry-pick X
git cherry-pick Y
Commonly used scientific symbols in pandoc markdown
encoding is UTF-8, needs xelatex, like this:
---
output:
pdf_document:
latex_engine: xelatex
---