No description
After two rounds of root-cause fixes (40 → 14 failures), the
residual 14 tests all fall into seven classes that are orthogonal
to v1.0.7 money-movement surface AND require investigations that
exceed the rc1 scope:
#57/v107-e2e-05 (5 tests) — upload backend submit hangs
27-upload:54, 43-upload-deep:663/713/747/781
#58/v107-e2e-06 (2 tests) — chat backend echo missing
29-chat-functional:70, :142
#59/v107-e2e-07 (2 tests) — workflow cascade under parallel load
13-workflows:17, :148
#60/v107-e2e-08 (1 test) — /feed page crash (browser-level)
11-accessibility-ethics:342
#61/v107-e2e-09 (2 tests) — chat DOM-detach race conditions
41-chat-deep:266, :604
#62/v107-e2e-10 (1 test) — playlist edit redirect
playlists-edit-audit:14
#63/v107-e2e-11 (1 test) — Playwright 50MB buffer limit (test bug)
43-upload-deep:364
Each test skipped with a test.skip + inline comment pointing at
its ticket, and SKIPPED_TESTS.md updated with the classification
table + unskip procedure.
Baseline trajectory over the rc1 sprint:
Pre-fixes: 122 pass / 40 fail / 9 skip
Round 1 (6 RC): 144 pass / 17 fail / 10 skip (-23 fail)
Round 2 (wide): 146 pass / 14 fail / 11 skip (-3 fail)
Post-skip: expected 146 pass / 0 fail / ~25 skip
Rationale vs "fix now":
* Each of the seven classes requires a backend-infra dive
(ClamAV, WebSocket, chat worker config) or test-infra refactor
(per-worker DB isolation, animation waits). Each 2-4h minimum,
with non-trivial regression risk on adjacent tests.
* 146/171 passing, 0 failing is a strictly more auditable release
state than SKIP_E2E=1 masking. The skips are explicit per-test
with documented root cause, not a blanket gate bypass.
* Satisfies the three conditions the user set yesterday for
formalising a scope reduction: each skip is documented, each
has an owner ticket, unskip procedure is traceable.
No v1.0.7 surface code touched.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .build/incus | ||
| .github | ||
| .husky | ||
| .playwright-mcp | ||
| apps/web | ||
| chat_exports | ||
| config | ||
| dev-environment | ||
| docker/haproxy | ||
| docs | ||
| docs-assets/mermaid | ||
| fixtures | ||
| frontend_screenshots | ||
| full_veza_audit_data | ||
| home/senke/git/talas/veza/apps/web/src | ||
| infra | ||
| k8s | ||
| loadtests | ||
| make | ||
| packages/design-system | ||
| prompts | ||
| proto | ||
| scripts | ||
| sub_task_agents | ||
| test-reports/20251226-132633 | ||
| tests | ||
| tmt | ||
| tools | ||
| veza-backend-api | ||
| veza-common | ||
| veza-docs | ||
| veza-stream-server | ||
| .cursorrules | ||
| .editorconfig | ||
| .env.example | ||
| .env.staging.example | ||
| .gitattributes | ||
| .gitignore | ||
| .gitleaks.toml | ||
| .lighthouserc.js | ||
| .lintstagedrc.json | ||
| .nvmrc | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| CONTRIBUTING.md | ||
| design-system-desktop-1280.png | ||
| design-system-fixed-desktop.png | ||
| design-system-mobile-375.png | ||
| design-system-tablet-768.png | ||
| docker-compose.dev.yml | ||
| docker-compose.env.example | ||
| docker-compose.override.yml.example | ||
| docker-compose.prod.yml | ||
| docker-compose.staging.yml | ||
| docker-compose.test.yml | ||
| docker-compose.yml | ||
| env.remote-r720.example | ||
| forgot-password-desktop-1280.png | ||
| forgot-password-fixed-desktop.png | ||
| forgot-password-mobile-375.png | ||
| forgot-password-success-state.png | ||
| forgot-password-tablet-768.png | ||
| generate_page_fix_prompts.sh | ||
| go.work | ||
| go.work.sum | ||
| Makefile | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| register-desktop-1280.png | ||
| register-mobile-375.png | ||
| RELEASE_NOTES_V1.md | ||
| reset-password-error-desktop.png | ||
| reset-password-fixed-desktop.png | ||
| run-audit.sh | ||
| rust-toolchain.toml | ||
| settings-dark-theme.png | ||
| settings-dual-theme-bug.png | ||
| settings-save-config-error.png | ||
| status.sh | ||
| storybook-button-a11y.png | ||
| storybook-button-docs.png | ||
| storybook-button-light-final.png | ||
| storybook-button-light-fixed.png | ||
| storybook-button-light.png | ||
| storybook-home.png | ||
| storybook-welcome.png | ||
| turbo.json | ||
| Untitled | ||
| VERSION | ||
| VEZA_VERSIONS_ROADMAP.md | ||
Veza Monorepo
Version courante : v1.0.4 (cleanup + consolidation post-audit). Voir CHANGELOG.md et docs/PROJECT_STATE.md.
Project Structure
apps/web— Frontend React 18 + Vite 5 + TypeScript strict (source of truth for the UI)veza-backend-api— Main Go 1.25 API service (Gin, GORM, Postgres, Redis, RabbitMQ, Elasticsearch). Handles REST, WebSocket, and chat (chat server was merged into this service in v0.502).veza-stream-server— Rust streaming server (Axum 0.8, Tokio 1.35, Symphonia) — HLS, HTTP Range, WebSocket, gRPCveza-common— Shared Rust types and loggingpackages/design-system— Shared design tokens
See CLAUDE.md for the full architecture map.
Development Setup
Prerequisites: Node 20 (see .nvmrc), Go, Rust, Docker. Configure .env from .env.example.
# Verify environment
make doctor
./scripts/validate-env.sh development
# Install dependencies
make install-deps
# Option A — Backend in Docker + Web local
make dev
# Option B — All apps local with hot reload (infra from docker-compose.dev.yml)
make dev-full
# Option C — Infra only, then run services manually
docker compose -f docker-compose.dev.yml up -d
make dev-web # or make dev-backend-api, make dev-stream-server
See docs/ENV_VARIABLES.md for required variables. make build builds all services.
Quick Start
Frontend only
cd apps/web
npm install
npm run dev
Docker Production
Canonical production compose file: docker-compose.prod.yml
docker compose -f docker-compose.prod.yml up -d
See make/config.mk for COMPOSE_PROD and deployment docs.
CI/CD
- Badge : CI status above. Set
SLACK_WEBHOOK_URL(Incoming Webhook) in repo secrets to receive Slack notifications on failure.
Disabled workflows
- Storybook (
chromatic.yml.disabled,storybook-audit.yml.disabled,visual-regression.yml.disabled): deferred until MSW is wired up for/api/v1/auth/meand/api/v1/logs/frontend, which currently causes ~1 400 network errors in the Storybook build. The npm scripts (storybook,build-storybook) still work locally for one-off component inspection. To reactivate in CI, fix the MSW handlers and rename the three files back to.yml.
Documentation
- Developer Onboarding — Setup, architecture, conventions, troubleshooting
- Documentation index — Index complet de la documentation
- See
docs/for detailed architecture and development guides. Older audits and reports are archived indocs/archive/.