| import asyncpg | |
| import dlt | |
| import asyncio | |
| from typing import Any, Dict, Optional | |
| from dlt.common.schema.typing import TColumnSchema | |
| """Convert an asyncpg type to a dlt column schema type. | |
| This maps asyncpg types to dlt types based on PostgreSQL to Python type mapping | |
| provided by asyncpg and the dlt data types. |
| /* Fonts */ | |
| /* Family */ | |
| h1 { | |
| font-family: 'Julius Sans One', sans-serif; | |
| } | |
| h2 { /* Contact, Skills, Education, About me, Work Experience */ | |
| font-family: 'Archivo Narrow', sans-serif; | |
| } |
| use futures::StreamExt; | |
| use std::error::Error; | |
| use tokio; | |
| use tokio::macros::support::Pin; | |
| use tokio::prelude::*; | |
| use tokio::time::{Duration, Instant}; | |
| pub fn main() -> Result<(), Box<dyn std::error::Error>> { | |
| let mut multi_threaded_runtime = tokio::runtime::Builder::new() | |
| .threaded_scheduler() |
| /* UTILS AND CONSTANTS*/ | |
| const SPEED_MULTIPLIER = 1.852; | |
| const DISTANCE_MULTIPLIER = 111.045; | |
| const SETTINGS = { | |
| "default_object_online_timeout": 5 | |
| ,"valid_by_avg_speed": false | |
| ,"min_moving_speed": 6 | |
| ,"addon.device_tracker_app_login": false |
The first step is to turn off the Raspberry so you can remove the memory card without worry.
If the Raspberry Pi is not connected to a screen, the only way to turn it off is to unplug it. Otherwise, you can go through the GUI to turn it off properly, via the menu, before unplugging it.
Once the Raspberry Pi is turned off, you can insert the card into your computer and go to the next step.
It happens that there are many standards for storing cryptography materials (key, certificate, ...) and it isn't always obvious to know which standard is used by just looking at file name extension or file content. There are bunch of questions on stackoverflow asking about how to convert from PEM to PKCS#8 or PKCS#12, while many tried to answer the questions, those answers may not help because the correct answer depends on the content inside the PEM file. That is, a PEM file can contain many different things, such as an X509 certificate, a PKCS#1 or PKCS#8 private key. The worst-case scenario is that someone just store a non-PEM content in "something.pem" file.
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
| #!/bin/sh | |
| # | |
| # sort a "du" listing by directory size | |
| # usage: du | dusort | |
| FILES= | |
| TFORM=0 | |
| while test $# -ge 1; do | |
| case $1 in | |
| -t) TFORM=1; ;; |
| import time | |
| import socket | |
| import threading | |
| import hashlib | |
| import itertools | |
| import sys | |
| from Crypto import Random | |
| from Crypto.PublicKey import RSA | |
| from CryptoPlus.Cipher import IDEA |
