Atender pedidos de membro sem derrubar a sincronização contínua
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- backend, documentation
Research direction
Start with packages/core/lib/session.js:367-372 and docs/rpc.md:217-219, then read docs/protocol.md:15. Trace how member operations open the store and take the lock while continuous sync is running; preserve the lock and quarantine guarantees when sharing the open store. Done means publishing during continuous sync emits no sync.stopped preempted, session and lock tests pass, and rpc.md §6.1 and protocol.md §9 are updated.
Written by the indexing model from the issue text.
Description
Contexto
Toda operação de membro abre o store e toma o lock, então o nó aborta a sincronização contínua, atende e reinicia o swarm. Com sync automática e avisos, isso custa segundos a cada publicação; o nó deveria atender sem derrubar o sync.
Escopo
- Compartilhar o store aberto entre sync e operações na sessão
- Manter as garantias de lock e de quarentena
- Atualizar rpc.md §6.1 e protocol.md §9
Critérios de aceite
- Publicar durante a sync contínua não emite sync.stopped preempted
- Os testes de sessão e de lock continuam passando
Fontes
Fase: Fase 2 — Ondas do canal · Dificuldade: grande
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 12m
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Varanda-org/varanda
-
área:app área:produto sem-fase tipo:decisão
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Varanda-org/varanda#91 ·
-
área:identidade área:produto sem-fase tipo:verificação
Difficulty 5/5 Over a week Newbie friendliness 25/100
Varanda-org/varanda#93 ·
-
área:identidade área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 25/100
Varanda-org/varanda#92 ·
-
área:moderação área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 35/100
Varanda-org/varanda#90 ·
-
área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 35/100
Varanda-org/varanda#89 ·
All issues in Varanda-org/varanda
Similar issues
-
bug needs triage P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pbakaus/impeccable#1143 ·
Maintainers usually reply within 1 day
-
status: waiting for maintainer
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
mui/material-ui#49547 ·
Maintainers usually reply within 1 day
-
next() is called twice when the request closes after busboy fails to startPossibly taken @NgoQuocViet2001 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[2.x] extension-manager: translation keys that changed meaning keep their old namesPossibly taken A pull request linked to this issue is open or already merged. Opentype/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day