etcd-io/etcd

Find and classify all the exit codes returned by etcdserver

Open

#21,032 opened on 2025年12月17日

GitHub で見る
 (9 comments) (0 reactions) (0 assignees)Go (51,701 stars) (10,352 forks)batch import
area/robustness-testinghelp wantedtype/feature

説明

What would you like to be added?

Would be great to understand what are exit codes generated by etcd

Expectation: Table with linking to code paths that call os.Exit (or similar) and the exit code it returns. Possibly a explanation. Could send a PR to documentation.

Why is this needed?

find why we return code 1 here:

https://linuxfoundation.antithesis.com/report/tIS34e56zvz8EGo02cE4NaiW/oHVZIeQ_MCxANyR4-diuJdY5hL7hR4AiRfNN2BmFUS4.html?auth=v2.public.eyJuYmYiOiIyMDI1LTEyLTE3VDEyOjQ0OjMzLjM0NDA0OTQ5M1oiLCJzY29wZSI6eyJSZXBvcnRTY29wZVYxIjp7ImFzc2V0Ijoib0hWWkllUV9NQ3hBTnlSNC1kaXVKZFk1aEw3aFI0QWlSZk5OMkJtRlVTNC5odG1sIiwicmVwb3J0X2lkIjoidElTMzRlNTZ6dno4RUdvMDJjRTROYWlXIn19fXPuVD228qmdQXwuV-pSQCQqosYoQZAdtsyzTbcbBZ1vkRRFyoV8dGb-sepLluyd39_Qcy19G0GRmd7WAHi1pAw#/run/d88bbffe0d5c03a180e1ed7f085a7fd7-44-16/finding/606b95a49077f8782c4e4e9f00f1480e23232903

コントリビューターガイド

技術スタック
go
領域
backenddatabase
Issue 種別
documentation
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Go programmingbasic understanding of etcd architecture
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
80
調査方針
Start by searching the etcd codebase for all calls to os.Exit in the etcdserver package. Focus on the server/ directory, particularly files like server/etcdserver/server.go, server/etcdserver/bootstrap.go, and server/etcdserver/errors.go. Look for exit codes in the range 0-255 and note the context. The issue mentions a specific report where exit code 1 is returned; begin by tracing that path. After collection, compile a table mapping each exit code to its source location and reason. Consider also checking the main.go files in cmd/etcd and any wrapper scripts. The issue expects a PR to docs, so the final output should be a Markdown table ready for inclusion in the documentation.