berkus

Physical layer

The dongle itself is sending out data using 802.11a (5 GHz WiFi) with OFDM and 6 Mbit/s data rate:

Radiotap Header v0, Length 38
    Header revision: 0
    Header pad: 0
    Header length: 38
    Present flags

berkus

   - name: Disable Windows Defender on build dirs
     if: runner.os == 'Windows'
     run: |
       Add-MpPreference -ExclusionPath "$env:GITHUB_WORKSPACE"
       Add-MpPreference -ExclusionPath "$env:USERPROFILE\.cargo"

berkus

From http://www.somethingorothersoft.com/2012/05/22/pulling-github-pull-requests-with-git/

Fetch all Pull Requests (even closed ones)

Just execute the following commands and you'll be able to fetch all pull requests by simply executing git fetch pr. Pull requests will be stored in a remote as individual remote branches. So a pull request 123 will be accessible as 'pr/123':

git remote add pr https://github.com/upstream/repo.git
git config --local --unset remote.pr.fetch
git config --local --add remote.pr.fetch "+refs/pull/*/head:refs/remotes/pr/*"

berkus

Sun, may you shine down on us 
let us rejoice in your warmth 
in delight, 
in delight 

Come, sit by me on the ground 
we'll chase away the demons 
fly, over the hills, 
of memories 

berkus

1. rg -a "text match", note the database file to use
2. sqlite3 Database.db
3. .tables
4. .schema <table>
5. select... until you find the ZBLOB's table primary key Z_PK
6. Save it to file with SELECT writefile('out.plist', ZBYTES) FROM ZBLOB WHERE Z_PK=298; <-- use your pk
7. Convert plist to text format with plutil -convert xml1 out.plist
8. Open it with an editor and find your contents among shitloads of metadata

berkus

// From https://jack.wrenn.fyi/blog/undroppable/

use std::mem;

/// A type that cannot be dropped.
pub struct Undroppable<T: ?Sized>(mem::ManuallyDrop<T>);

impl<T> Undroppable<T> {
    // Makes `val` undroppable.
    //

berkus

Conventional Commits with Emoji

Based on https://github.com/ellerbrock/conventional-commit-types-emoji for preview and on https://github.com/pvdlg/conventional-commit-types for the actial emoji images

🚨 There is a commit-emoji hook now to insert emoji automatically based on prefix, so you can just install it and use regular conventional commits (even using a tool like koji). 🚨

---

feat(xxx): ✨ Features your commit message

berkus

#!/bin/sh
set -e
set -x

reponame=`basename $(pwd)`

echo "#######################################################################################"
echo "#  Script to import all local branches from current repository (${reponame}) into pijul"
echo "#  Will create a bunch of temp repos for import, so have sufficient disk space"
echo "#######################################################################################"

berkus

1. Separation of immutable and mutable logic

Quite a lot of different people have been on the same trail of thought. Gary Bernhardt's formulation of a "functional core, imperative shell" seems to be the most voiced.

"Boundaries" - Gary Bernhardt

"Imperative shell" that wraps and uses your "functional core".. The result of this is that the shell has fewer paths, but more dependencies. The core contains no dependencies, but encapsulates the different logic paths. So we’re encapsulating dependencies on one side, and business logic on the other side. Or put another way, the way to figure out the separation is by doing as much as you can without mutation, and then encapsulating the mutation separately. Functional core — Many fast unit tests. Imperative shell — Few integration tests

https://www.youtube.com/watch?v=yTkzNHF6rMs

berkus

def filtered = ['class', 'active']

println theObject.properties
            .sort{it.key}
            .collect{it}
            .findAll{!filtered.contains(it.key)}
            .join('\n')