openpilot is a full-stack autonomous driver assistance system that runs on embedded Linux hardware (comma four/three) and controls 300+ car models. It is a safety-critical, real-time system written primarily in Python and C/C++, with a custom messaging layer (cereal/msgq) and a Cap'n Proto-based schema for all inter-process communication. The architecture is a collection of independent processes (controlsd, plannerd, radard, modeld, locationd, calibrationd, dmonitoringd, etc.) communicating via a pub/sub message queue, managed by a central process manager. The system ingests CAN bus data, camera streams (road, wide-road, driver), IMU/GPS sensor data, and runs neural network models (ONNX/tinygrad) for perception and planning. The codebase demonstrates strong engineering discipline: a comprehensive process replay regression testing framework that replays logged routes through individual processes and compares outputs bit-for-bit; a safety model implemented in the panda firmware (separate submodule) with ISO 26262 guidelines; real-time scheduling and CPU affinity management across processes; and a sophisticated build system using SCons with Cython compilation. The UI is built on raylib (with a Qt-based Cabana tool for CAN analysis), and there's a MetaDrive simulator bridge for development. Key architectural patterns include: a generic car interface abstraction (opendbc) that allows supporting 300+ car models through fingerprinting and parameter configuration; a model-driven control pipeline where neural network outputs (desired curvature, lead vehicle trajectories) feed into lateral controllers (PID, torque-based, curvature-based, angle-based) and longitudinal MPC planners; an EKF-based sensor fusion system (locationd) combining GPS, IMU, and vehicle odometry; and a driver monitoring system using a separate neural network for distraction detection. The system uses a parameter store (params) backed by a filesystem for persistent configuration. The repository includes extensive tooling: replay infrastructure for regression testing, PlotJuggler/Cabana integration for data visualization, automated car porting tools with fuzzy fingerprinting, release automation with stripped builds, and a comprehensive CI/CD pipeline with GitHub Actions. The codebase is actively maintained with daily commits, a structured release process (release-mici/release-tizi branches), and active community contribution through Discord and GitHub issues.
Pretext is a high-performance JavaScript/TypeScript library for text measurement and layout that operates entirely without DOM reflow. It accurately predicts line breaks, widths, and heights for any text, matching the behavior of Chrome (Blink), Firefox (Gecko), and Safari (WebKit) by porting each engine's line-breaking rules and embedding their ICU break tables. The library uses a two-phase architecture: a preparation phase that measures each character segment using Canvas `measureText()` and caches the results, followed by a pure-arithmetic layout phase that computes line breaks and positions with sub-millisecond performance. It supports plain text, rich inline spans (styled runs, atomic chips), and advanced features like letter spacing, soft hyphens, emoji handling, and CJK punctuation kerning. A comprehensive test harness records actual browser layouts of thousands of cases and scores predictions against them, with automated gates that block regressions. The repository also includes demos showing virtualized chat, editorial layouts with obstacles, justification comparison, and shrink-wrapping. While primarily an application/library, it contains significant data/research components—generated break tables from browser engines, multilingual corpora for testing, and offline invariants—making it a hybrid project with a strong research character in cross-browser text rendering.
This is the top-level Boost C++ Libraries superproject, an aggregator and distribution harness for roughly 150 library submodules rather than a standalone application. Its production role is to let users clone the full Boost ecosystem, bootstrap the B2 engine, and build/install all libraries through either the classic Boost.Build system or the CMake superproject. The actual library source code lives in sibling submodules; this repository contributes the central build entry points, release packaging workflows, CI matrices, and regression-status infrastructure that make the ecosystem consumable. Architecturally it is a build orchestration and QA hub. Key entry points are Jamroot and boostcpp.jam for B2, CMakeLists.txt for CMake, and bootstrap.sh/batch for engine setup. The data flows are primarily build-directed: a user selects libraries (--with/--without), the build system expands multi-variant targets (debug/release, static/shared, various address models), compiles and installs artifacts, and CI scripts validate headers, CMake configs, and test results. The status/ directory contains the expected-failure registry and conformance checking used to gate regressions across a large compiler/platform matrix. Maintenance is genuinely active, with GitHub Actions, CircleCI, AppVeyor, and automated submodule pointer updates. However, the codebase carries notable legacy weight: parallel B2 and CMake build systems must stay in sync, some CI entries reference very old compilers and toolsets, CMake compatibility floors are old, and the expected-failure XML contains decades of accumulated entries. This is best treated as a high-quality but complex build/distribution infrastructure repository, not as a source of end-user application logic.
This repository serves as the customer test registry for the Flutter framework. It contains .test configuration files in the `registry/` directory that define how to fetch, update, and run tests from external Flutter packages (e.g., flame, provider, devtools) in CI. These tests are executed with every Flutter commit to detect regressions. The repository also includes a separate `skp_generator` Flutter application that generates SKP files of Flutter scenes for Skia's use in regression and performance testing. The codebase is implemented primarily as shell scripts (bash/batch), GitHub Actions workflows, and a small Dart program. It is not a reusable library but rather an operational glue repository for integrating third-party Flutter tests into the Flutter CI pipeline. The architecture is simple: test definitions (key-value format) are parsed by a Dart runner (`dev/customer_testing/run_tests.dart` in the Flutter repo) which fetches, updates, and runs the tests as per the directives. The SKP generator is a separate utility with its own build script and Dart code for scene rendering.