Skip to content

Fix: make update-toc error in mac os #549

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
k8s-ci-robot merged 1 commit into from
Apr 14, 2026
Merged

Fix: make update-toc error in mac os #549

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions docs/keps/174-metadata-propagation/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,23 @@

---

<!-- toc -->
- [Summary](#summary)
- [Motivation](#motivation)
- [Proposal](#proposal)
- [User Stories (Optional)](#user-stories-optional)
- [Use Case 1: Custom Metadata Propagation (Identification)](#use-case-1-custom-metadata-propagation-identification)
- [Use Case 2: Stateful Session Management (Pod Snapshots)](#use-case-2-stateful-session-management-pod-snapshots)
- [High-Level Design](#high-level-design)
- [Safety Principle: No Overrides](#safety-principle-no-overrides)
- [API Changes](#api-changes)
- [Implementation Guidance](#implementation-guidance)
- [Scenario A: Cold Start (No Warmpool)](#scenario-a-cold-start-no-warmpool)
- [Scenario B: Warmpool](#scenario-b-warmpool)
- [Scalability](#scalability)
- [Alternatives (Optional)](#alternatives-optional)
<!-- /toc -->

## Summary

This KEP proposes a standardized mechanism to clarify how labels and annotations propagate from top-level user requests (`SandboxClaim`) down to the final compute resources (`Pod`). This ensures consistency for observability, billing, and workload management while maintaining the homogeneity and performance of `SandboxWarmPools`.
Expand Down
12 changes: 12 additions & 0 deletions docs/keps/359-refactor-python-sdk/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,15 @@
<!-- toc -->
- [1. Summary](#1-summary)
- [2. Motivation](#2-motivation)
- [3. API Specification](#3-api-specification)
- [3.1 The EntryPoint (<code>SandboxClient</code>)](#31-the-entrypoint-sandboxclient)
- [3.2 The Core Handle (Sandbox)](#32-the-core-handle-sandbox)
- [3.3 Specialized Engines](#33-specialized-engines)
- [3.4 Developer Experience (The &quot;Fluent&quot; API)](#34-developer-experience-the-fluent-api)
- [4. Proof Of Concept](#4-proof-of-concept)
- [5. Scalability](#5-scalability)
<!-- /toc -->

### 1. Summary

This KEP discusses the idea of a Unified Agent Sandbox SDK that provides AI Agent Orchestrators / Platform Admins with a Fluent API for managing remote execution environments. This design moves away from treating a sandbox as a transient Python script helper (via `ContextManager` i.e `with`/`__enter__`/`__exit__`) and instead treats it as a Persistent Resource Handle. By abstracting the sandbox into specialized engine (Execution, Filesystem etc), the SDK provides a robust interface for long-lived, stateful agentic workflows.
Expand Down