Allow FreeBSD environment lookup to grow beyond its initial source buffer

Abierto
  • ¿Algo no está bien?
#1,008 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
operating-systems

Línea de trabajo

Start with std/env/environ.wave around line 40 and trace the portable environment providers and their sizing behavior. Coordinate with @LunaStev to agree on the bounded FreeBSD retry contract before implementation. Validate on native FreeBSD with an environment larger than 32 KiB, confirming that only genuine capacity errors are retried and that allocation, retry-limit, not-found, and destination-too-small outcomes remain distinct.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

discussion enhancement help wanted

Motivation

The portable environment reader starts at 32 KiB, but its FreeBSD needs-space predicate always returns false. The provider returns a short-buffer sysctl error without exposing the required length, so this target cannot use the growth path available to other providers.

Starting point: std/env/environ.wave:40.

Validation

Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Inspected portable/provider source and official sysctl sizing semantics; native large-environment reproduction remains required. Executed compiler probes use the matching checkout-built compiler and std on Linux amd64 (Rust 1.89.0 / LLVM 21.1.8). Source/header or mocked checks are not native execution on another OS.

FreeBSD sysctl documentation describes oldlenp sizing and short-buffer ENOMEM. The proposal does not claim current silent truncation.

Scope

Define a bounded FreeBSD sizing/retry contract for KERN_PROC_ENV. Distinguish insufficient capacity from unrelated ENOMEM failures and changing environment data.

Related: #938, #427. These links do not claim those broader or completed scopes are unfinished.

Design discussion required

This issue records a proposal or an unresolved contract; it is not approval to choose new semantics. Please mention @LunaStev to discuss the design before starting implementation.

Completion criteria

  • A controlled/native environment larger than the initial buffer can be queried within the agreed bound.
  • Ordinary provider errors are not retried as capacity failures.
  • Allocation, retry limits and not-found/destination-too-small results remain distinct.
Lenguaje dominante
Rust
Estrellas
56
Forks
21
Merge medio
23 h 20 min
PR fusionados (30 d)
45

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de wavefnd/Wave

Todos los issues de wavefnd/Wave

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.