etcd-io/etcd

Add server information to robustness response information

Open

#20.932 aberto em 16 de nov. de 2025

Ver no GitHub
 (15 comments) (0 reactions) (2 assignees)Go (51.701 stars) (10.352 forks)batch import
area/robustness-testinghelp wantedtype/feature

Description

What would you like to be added?

Add MemberId to from response header to the model.EtcdResponse. Ensure it's added to json response and visualized in the porcupine linearization.

Edit: Would be great to have this information showing in tooltip, for that we need https://github.com/anishathalye/porcupine/pull/39

Tasks:

/cc @sneaky-potato @henrybear327 @nwnt

Why is this needed?

Makes it easier to debug linearization failure

Guia do colaborador

Pilha de tecnologia
go
Domain
backenddatabaseobservability
Tipo Issue
feature
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
3
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-2 days
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
active
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
mostly clear
Prerequisites
Go programmingUnderstanding of etcdFamiliarity with linearizability testing
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
35
Direção de pesquisa
This issue requires adding MemberId from the response header to the etcd robustness response. The work involves two tasks: modifying etcd (PR #21016) and updating the porcupine library (PR 39). Start by reviewing the existing robustness code in the etcd repository, particularly the `model.EtcdResponse` struct and how response headers are processed. Then, collaborate on the porcupine PR to ensure the tooltip displays the MemberId. The issue is actively discussed with assignees, so coordinate with them to avoid duplication.