For educational reasons I've decided to create my own CA. Here is what I learned.
Lets get some context first.
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
It's a common confusion about terminal colours... Actually we have this:
printf "\x1b[${bg};2;${red};${green};${blue}m\n"
| diff --git a/Python/random.c b/Python/random.c | |
| index 93d300d..396041d 100644 | |
| --- a/Python/random.c | |
| +++ b/Python/random.c | |
| @@ -3,6 +3,9 @@ | |
| #include <windows.h> | |
| #else | |
| #include <fcntl.h> | |
| +#if defined(HAVE_GETRANDOM) || defined(HAVE_GETENTROPY) | |
| +#include <sys/random.h> |
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.await import(…) from CommonJS instead of require(…).| --- | |
| date: <% tp.file.creation_date() %> | |
| type: meeting | |
| company: | |
| summary: " " | |
| --- | |
| tags: [[🗣 Meetings MOC]] | |
| Date: [[<% tp.date.now("YYYY-MM-DD-dddd") %>]] | |
| <% await tp.file.rename(tp.date.now("YYYY-MM-DD") + " " + tp.file.title) %> | |
| # [[<% tp.date.now("YYYY-MM-DD") + " " + tp.file.title %>]] |
If you encounter a problem where you cannot commit changes in Git – neither through the terminal nor via the GitHub Desktop application – the issue might be a freeze during the Git commit process. This is often caused by GPG lock issues. Below is a concise and step-by-step guide to resolve this problem.
Open your terminal and try to perform a GPG operation (like signing a test message). If you see repeated messages like gpg: waiting for lock (held by [process_id]) ..., it indicates a lock issue.