Tags

Canon8

• BXM 0.1.0 Launches With Canon and Memo, Two Open Source Tools for Repeatable Results
• Why Signed JSON Breaks and How a Canonical Encoding Fixes It
• A Config Diff of 128 Lines Hid Two Real Changes, and Canon Named Both in Two Lines
• BXM Canon 0.2.0 Brings the Same Bytes to JavaScript With One Rust Core Compiled to WebAssembly
• BXM Canon 0.3.0 Adds Python, With Ints, Floats and Bytes Kept Apart and the Same Hash as Every Other Build
• Hashing 100,000 JSON Lines Found No Duplicates, Hashing Them With Canon Found 9,900
• How BXM Was Tested With Two Million Damaged Inputs, Sixteen Processes and a Killed Run
• One Order Built in Python, JavaScript and by Hand Gives Three JSON Hashes and One Canon Hash

Case Study6

• A Config Diff of 128 Lines Hid Two Real Changes, and Canon Named Both in Two Lines
• Hashing 100,000 JSON Lines Found No Duplicates, Hashing Them With Canon Found 9,900
• Memo in GitHub Actions Skipped a Rust Release Build and Caught Runners With Different Compilers
• One Order Built in Python, JavaScript and by Hand Gives Three JSON Hashes and One Canon Hash
• Replaying 13 Commits Through Memo Cut Test Time From 228 to 79 Seconds and Turned Up Two Flaky Tests
• Why Did My Build Step Run Again, Six Cache Misses and What Memo Said About Each

Ci3

• Memo in GitHub Actions Skipped a Rust Release Build and Caught Runners With Different Compilers
• Replaying 13 Commits Through Memo Cut Test Time From 228 to 79 Seconds and Turned Up Two Flaky Tests
• Why Did My Build Step Run Again, Six Cache Misses and What Memo Said About Each

Config1

• A Config Diff of 128 Lines Hid Two Real Changes, and Canon Named Both in Two Lines

Data1

• Hashing 100,000 JSON Lines Found No Duplicates, Hashing Them With Canon Found 9,900

Explainer2

• Why Signed JSON Breaks and How a Canonical Encoding Fixes It
• Why CI Pipelines Redo Work Nobody Changed and How a Command Memoizer Stops It

Github Actions1

• Memo in GitHub Actions Skipped a Rust Release Build and Caught Runners With Different Compilers

Javascript2

• BXM Canon 0.2.0 Brings the Same Bytes to JavaScript With One Rust Core Compiled to WebAssembly
• One Order Built in Python, JavaScript and by Hand Gives Three JSON Hashes and One Canon Hash

Memo6

• BXM 0.1.0 Launches With Canon and Memo, Two Open Source Tools for Repeatable Results
• Why CI Pipelines Redo Work Nobody Changed and How a Command Memoizer Stops It
• How BXM Was Tested With Two Million Damaged Inputs, Sixteen Processes and a Killed Run
• Memo in GitHub Actions Skipped a Rust Release Build and Caught Runners With Different Compilers
• Replaying 13 Commits Through Memo Cut Test Time From 228 to 79 Seconds and Turned Up Two Flaky Tests
• Why Did My Build Step Run Again, Six Cache Misses and What Memo Said About Each

Name1

• Why the Project Is Called BXM

Python3

• BXM Canon 0.3.0 Adds Python, With Ints, Floats and Bytes Kept Apart and the Same Hash as Every Other Build
• Hashing 100,000 JSON Lines Found No Duplicates, Hashing Them With Canon Found 9,900
• One Order Built in Python, JavaScript and by Hand Gives Three JSON Hashes and One Canon Hash

Release3

• BXM 0.1.0 Launches With Canon and Memo, Two Open Source Tools for Repeatable Results
• BXM Canon 0.2.0 Brings the Same Bytes to JavaScript With One Rust Core Compiled to WebAssembly
• BXM Canon 0.3.0 Adds Python, With Ints, Floats and Bytes Kept Apart and the Same Hash as Every Other Build

Testing2

• How BXM Was Tested With Two Million Damaged Inputs, Sixteen Processes and a Killed Run
• Replaying 13 Commits Through Memo Cut Test Time From 228 to 79 Seconds and Turned Up Two Flaky Tests