rkt/rkt

stage1 implementation/guide: missing and empty valued entrypoints should be handled

Open

#1897 opened on Dec 18, 2015

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (8,871 stars) (865 forks)batch import
component/stage1help wantedkind/documentationpriority/Pmaybe

Description

Capturing https://github.com/coreos/rkt/pull/1833/files#r48026752 (from rkt-fly):

The doc stage1-implementors-guide.md should say what's happening when the dictionary entries are missing:

  • run: error out
  • gc: silently skip the execution of stage1's GC
  • enter: error out with "not implemented"
  • Implementation
  • Docs

Contributor guide

Tech stack
go
Domain
backendinfrastructure
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingrkt stage1 conceptscontainer runtime basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
The issue requires adding error handling for missing or empty entrypoints in stage1, as referenced in PR #1833. The main file to modify is the stage1 implementors guide.md and the corresponding stage1 code (likely in stage1/init). The behavior should be: for 'run' entrypoint error out, for 'gc' silently skip, for 'enter' error with 'not implemented'. No current activity or blockers, but the issue is old and the project is archived, so contribution may be limited.