SPDT/sapl - sapl - Gitea: Git with a cup of tea

5884 Commits

65 Branches

270 Tags

246 MiB

Tree: 6e53b72e95

Commit Graph

Author	SHA1	Message	Date
Edward Ribeiro	6e53b72e95	style(painel): corrige erros de ESLint nos cronômetros continuous-integration/drone/push Build is passing Details Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	6 days ago
RogerKoala	ad00d7a6ab	fix: corrige sincronização e exibição dos cronômetros no painel	6 days ago
Edward Ribeiro	705d6e16eb	Painel de votação em tempo real: Django Channels/WebSockets + Vue 2/Pinia Substitui o polling HTTP do painel legislativo por push via WebSockets (um PainelConsumer por sessão, broadcast de snapshot completo a partir de build_dados_painel()) e cobre com páginas Vue 2 + Pinia as telas de exibição pública do painel, votação nominal, voto individual, votação simbólica e leitura de matéria — todas consumindo o mesmo broadcast via normalizePainelData()/painelStore, sem componentes Vuex remanescentes. - Backend: PainelConsumer/ASGI (Channels + Redis), views Postgres (SessaoPresencasView/SessaoMateriasVotacoesView) para eliminar N+1, cronômetro com estado compartilhado em cache, migrations 0070-0073 como cadeia única. - Máscara de voto preservada: o broadcast público continua sempre mascarado por mostrar_voto; estado por-operador e por-eleitor vem de endpoints HTTP dedicados (votante_status, _status_json), nunca do broadcast compartilhado. - Infra: docker-compose e nginx atualizados para /ws/, requirements (channels/daphne/channels-redis) e vue.config.js com as novas entries de webpack. - Testes: test_broadcasts.py, test_consumers.py, test_votacao_nominal.py e test_sessao_view.py cobrindo o novo backend. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H85beqPY6uKTmSdCEovbPa Painel: remove polling fallback, WS-only with connection error UI Documents local-dev setup requirements in sapl/sessao/README.md and finishes the polling->push migration by removing the HTTP polling that was still running as a fallback everywhere: the three legacy templates (painel/index.html, voto_individual.html, sessao/votacao/nominal.html) and voto-individual/main.js. Every painel/votação screen — legacy and Vue — is now WebSocket-only. - Reconnect: exponential backoff with jitter (was flat 500ms in Vue), and connections now distinguish PainelConsumer's permanent close codes (4401/4403/4404 — auth/permission/no-such-sessão) from transient drops instead of retrying forever. New frontend/src/__apps/painel/ws/ painelSocket.js + WsStatusBanner.vue share this across the five Vue apps; the three legacy templates get an equivalent vanilla-JS banner. - Broadcast coverage: without polling to mask it, every write path that changes the painel payload now has to call broadcast_dados_painel() itself. Added it to PresencaView/PresencaOrdemDiaView, the three Orador*Crud create/update/delete views (via a new BroadcastPainelOnSaveMixin — covered by a new end-to-end test, since self.kwargs['pk'] means the parent sessão in CreateView but the Orador's own pk in Update/DeleteView), LeituraEmBloco, and VotacaoEmBlocoSimbolicaView/VotacaoEmBlocoNominalView. - voto_individual.html now opens its WebSocket whenever a sessão is open (not just when a matéria is), gated on sessao_id being present rather than on materia — otherwise a page with no votação aberta at all had no sessao_id to build a WS URL from. - Dead code removed: painel_mensagem/painel_parlamentar/painel_votacao (views, urls, templates) had no references anywhere and predate this work. dados_painel/get_dados_painel (the HTTP polling endpoint) and its ETag helper are also removed now that nothing polls them, along with the tests pinning their HTTP-specific behavior — build_dados_painel() itself is untouched and still backs every WS broadcast. - scripts/verify_painel_websockets.sh now runs a single Daphne process instead of Daphne+runserver on separate ports: WS-only clients need HTTP and WS on the same origin, which the old split-port setup never actually provided (it only appeared to work via the polling fallback that's now gone). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H85beqPY6uKTmSdCEovbPa	4 weeks ago

Author

SHA1

Message

Date

Edward Ribeiro

6e53b72e95

style(painel): corrige erros de ESLint nos cronômetros

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

6 days ago

RogerKoala

ad00d7a6ab

fix: corrige sincronização e exibição dos cronômetros no painel

6 days ago

Edward Ribeiro

705d6e16eb

Painel de votação em tempo real: Django Channels/WebSockets + Vue 2/Pinia

Substitui o polling HTTP do painel legislativo por push via WebSockets
(um PainelConsumer por sessão, broadcast de snapshot completo a partir
de build_dados_painel()) e cobre com páginas Vue 2 + Pinia as telas de
exibição pública do painel, votação nominal, voto individual, votação
simbólica e leitura de matéria — todas consumindo o mesmo broadcast via
normalizePainelData()/painelStore, sem componentes Vuex remanescentes.

- Backend: PainelConsumer/ASGI (Channels + Redis), views Postgres
  (SessaoPresencasView/SessaoMateriasVotacoesView) para eliminar N+1,
  cronômetro com estado compartilhado em cache, migrations 0070-0073
  como cadeia única.
- Máscara de voto preservada: o broadcast público continua sempre
  mascarado por mostrar_voto; estado por-operador e por-eleitor vem de
  endpoints HTTP dedicados (votante_status, _status_json), nunca do
  broadcast compartilhado.
- Infra: docker-compose e nginx atualizados para /ws/, requirements
  (channels/daphne/channels-redis) e vue.config.js com as novas entries
  de webpack.
- Testes: test_broadcasts.py, test_consumers.py, test_votacao_nominal.py
  e test_sessao_view.py cobrindo o novo backend.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01H85beqPY6uKTmSdCEovbPa

Painel: remove polling fallback, WS-only with connection error UI

Documents local-dev setup requirements in sapl/sessao/README.md and
finishes the polling->push migration by removing the HTTP polling that
was still running as a fallback everywhere: the three legacy templates
(painel/index.html, voto_individual.html, sessao/votacao/nominal.html)
and voto-individual/main.js. Every painel/votação screen — legacy and
Vue — is now WebSocket-only.

- Reconnect: exponential backoff with jitter (was flat 500ms in Vue),
  and connections now distinguish PainelConsumer's permanent close codes
  (4401/4403/4404 — auth/permission/no-such-sessão) from transient drops
  instead of retrying forever. New frontend/src/__apps/painel/ws/
  painelSocket.js + WsStatusBanner.vue share this across the five Vue
  apps; the three legacy templates get an equivalent vanilla-JS banner.
- Broadcast coverage: without polling to mask it, every write path that
  changes the painel payload now has to call broadcast_dados_painel()
  itself. Added it to PresencaView/PresencaOrdemDiaView, the three
  Orador*Crud create/update/delete views (via a new
  BroadcastPainelOnSaveMixin — covered by a new end-to-end test, since
  self.kwargs['pk'] means the parent sessão in CreateView but the
  Orador's own pk in Update/DeleteView), LeituraEmBloco, and
  VotacaoEmBlocoSimbolicaView/VotacaoEmBlocoNominalView.
- voto_individual.html now opens its WebSocket whenever a sessão is
  open (not just when a matéria is), gated on sessao_id being present
  rather than on materia — otherwise a page with no votação aberta at
  all had no sessao_id to build a WS URL from.
- Dead code removed: painel_mensagem/painel_parlamentar/painel_votacao
  (views, urls, templates) had no references anywhere and predate this
  work. dados_painel/get_dados_painel (the HTTP polling endpoint) and
  its ETag helper are also removed now that nothing polls them, along
  with the tests pinning their HTTP-specific behavior — build_dados_painel()
  itself is untouched and still backs every WS broadcast.
- scripts/verify_painel_websockets.sh now runs a single Daphne process
  instead of Daphne+runserver on separate ports: WS-only clients need
  HTTP and WS on the same origin, which the old split-port setup never
  actually provided (it only appeared to work via the polling fallback
  that's now gone).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01H85beqPY6uKTmSdCEovbPa

4 weeks ago

3 Commits (6e53b72e9548a69faa64e24df1d1c3de01e9192e)