fix(ui): isolar painéis para um coletor não derrubar o status - #7
Merged
Merged
Conversation
Se battery/system/disk/network/health explodir, o painel vira um fallback e o resto do mm / mm watch continua. KeyboardInterrupt e SystemExit seguem subindo.
8 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resumo
Se um coletor explode (timeout, MarkupError, psutil), o
mmstatus e omm watchmorriam inteiros. Cada painel agora passa porsafe_panel: a exceção vira um fallback ("Não foi possível coletar estes dados") e os outros painéis seguem.KeyboardInterrupteSystemExitcontinuam subindo.Tipo de mudança
Issues relacionadas
—
Saída
Antes: um
TimeoutExpiredna rede abortava o status depois dos painéis que já tinham saído, ou derrubava o dashboard.Depois: o painel falho mostra a mensagem de fallback; battery/system/disk (ou o que tiver funcionado) continuam visíveis.
Checklist
mainmais recente (já inclui o fix(network): degradar em vez de crashar no timeout do profiler #6).pytestpassou localmente (215 testes).CHANGELOG.mdem[Unreleased].Notas para revisão
Próximos PRs da mesma varredura: escape de markup do Rich, pular alerta de bateria sem bateria, realocar
LOGS_DIR, validação da CLI, interface ativa + não cachear IP públicoNone.