This repository is a comprehensive collection of examples for the **knitr** R package, demonstrating features such as chunk options, hooks, multiple language engines (Python, Bash, C++, etc.), caching, child documents, and output formats (Markdown, LaTeX, HTML, reST, etc.). It serves as both a tutorial for new users and an integration test suite for the knitr package itself. The examples are self-contained, using built-in R datasets (e.g., iris, mtcars, cars) and simple computational tasks. While not a production application or data pipeline, the repo provides a valuable reference for literate programming and reproducible research with R. It is actively maintained by the knitr author and community.
vkbind is a Vulkan API loader and code generator that creates a single header file containing all Vulkan API definitions and functions for dynamically loading Vulkan functions. It parses the official Vulkan XML specifications (vk.xml and video.xml) to generate a comprehensive C header that eliminates the need for the official Vulkan SDK. The generated header includes type definitions, enumerants, function prototypes, and loader functions like vkInit(), vkInitInstanceAPI(), and vkBindAPI() for accessing Vulkan functionality across different platforms.
This repository is an educational resource that accompanies the 'Understanding Gradle' video series. It contains a series of self-contained example Gradle projects, each demonstrating a specific concept of the Gradle build tool, from basic settings files to advanced topics like artifact transforms and Java module path. The examples are structured as independent projects with their own build configurations, often using composite builds and convention plugins to illustrate best practices. The code is well-crafted, following modern Gradle patterns (Kotlin DSL, lazy configuration, variant-aware dependency management). While not a production application, the repository serves as a reference implementation for Gradle best practices and provides reusable patterns for structuring real-world Gradle projects. The architecture is a collection of example projects, each with a my-build-logic directory containing reusable convention plugins, and a my-project directory demonstrating the concept. The examples cover the full spectrum of Gradle functionality, from settings files to CI integration.
This repository is the canonical source of tldr-pages, a community-maintained collection of simplified man pages for command-line tools. It contains tens of thousands of Markdown files organized by language and platform, each providing concise usage examples for a CLI command. The repository also includes a suite of validation scripts, a build system for generating indexes and archives, and a client specification for consuming the pages. While primarily a documentation project, the tooling (Node.js and Python scripts) constitutes a small application layer that ensures consistency, quality, and automated releases. The repo supports translations in over 30 languages, with strict formatting and linting enforced by CI/CD pipelines. It is not a standalone application but the authoritative dataset and tooling for the tldr ecosystem.
This repository is a cookbook of runnable examples for the OpenClaw SDK. It contains two layers: small one-concept recipes (e.g., run-an-agent, stream-events, cancel-a-run) and standalone starter apps (quickstart Node app, coding-agent CLI, agent-workbench React app, run-board React dashboard). The code demonstrates SDK workflows such as starting runs, streaming normalized events, cancelling work, reusing sessions, checking model status, and testing with an in-memory transport. The architecture is modular: recipes are self-contained TypeScript files with shared configuration helpers, and SDK examples are independent packages that can be copied out and adapted. The repository includes comprehensive tests, CI checks, and a workspace SDK shim for local validation without a live Gateway. It is actively maintained with modern dependencies (TypeScript 7, Node 22, pnpm 10.34.5) and follows strict formatting and linting rules.
This repository is a monorepo of self-contained demo applications showing how to build and deploy multi-agent AI systems using Docker Compose, Docker Model Runner, and the MCP Gateway. It contains 12+ independent examples spanning Google ADK, A2A, Agno, CrewAI, LangGraph, Langchaingo (Go), Spring AI, Akka, and a Next.js agent UI. Each subproject is a standalone composition with its own compose.yaml, Dockerfile, and README, designed to run with a single `docker compose up --build` after creating a `.mcp.env` file. The demos are reference architectures rather than a single product, emphasizing local LLM inference, MCP tool integration, and switching between local and cloud models via compose override files.
This repository is a collection of standalone example applications demonstrating features of the Gin web framework for Go. It includes over 30 examples covering routing, middleware, authentication, file uploads, WebSocket, server-sent events, gRPC integration, OpenTelemetry, and more. Each example is a self-contained Go program with its own main.go and dependencies. The codebase serves as a learning resource and reference for Gin patterns, but is not a cohesive production system. Many examples are simple and straightforward, though some demonstrate non-trivial patterns like rate limiting, struct-level validation, and concurrent room management.
The repository is a Rust CLI application for managing a todo list. It allows users to create and list todo items, with data persisted in a JSON file. The application is structured into modules: `core` (defining the data structure and command enum), `create` (handling item creation), `list` (handling listing and filtering), and `storage` (handling file I/O). It uses the `clap` crate for command-line argument parsing and `serde` for JSON serialization. The code demonstrates good Rust practices such as error handling with `Result`, modularity, and unit testing. However, it includes several unused dependencies, indicating some technical drift, and the last commit is over six months old, suggesting the project is not actively maintained.
The p4lang/p4-spec repository hosts the P4 language specification and related artifacts, including the Portable Switch Architecture (PSA) definition, example P4 programs, and documentation build tools. It contains versioned specifications for P4_14 (in maintenance mode) and P4_16 (active), along with PSA compliance requirements and illustrative examples such as mTag edge/aggregation switches and PSA-based programs for counters, registers, and telemetry. The repository includes a documentation pipeline composed of Makefiles, AsciiDoc/Latex sources, and custom scripts (e.g., pretext.py, trim-asciidoc-tag-comments.py) that generate PDF and HTML outputs, ensuring consistent specification publication. Additionally, it provides utility scripts for font license compliance and grammar validation, supporting the maintenance of the specification as a technical standard for programmable network data planes.
This is an Android application that serves as a learning resource for RxJava 2. It contains over 30 example activities demonstrating various RxJava operators (map, flatMap, zip, filter, take, skip, buffer, concat, merge, etc.), Subjects (Publish, Behavior, Replay, Async), and practical patterns like caching with multiple data sources, pagination with PublishProcessor, search with debounce/switchMap, an event bus (RxBus), and networking with AndroidNetworking. The code is written in Java and targets Android API 28 (Android 9). It uses old dependencies (Gradle 3.2.0, RxJava 2.2.2, AndroidX alpha versions) and the build system relies on the deprecated jcenter() repository. The architecture is straightforward: each example is a self-contained Activity that creates an Observable and logs results to a TextView. While the code is functional and educational, it is not production-grade and exhibits significant technical drift due to outdated libraries and practices.