QA: Setup missing steps #36
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:open_issues
agents
agent:security_audit
agent:verify
area
timecurve
arena
arena-v2
audit
block:feature_review
block:security
bug
contracts
design
devops
docs
documentation
enhancement
epic
feature
frontend
indexer
low priority
megaeth
operations
ops
performance
QA
qa checklist
referrals
removal
security
smart-contracts
tech-debt
testing
time-arena
timecurve
visual-qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
code/yieldomega#36
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Missing Info for setup
Summary
Missing required environment configuration for TimeCurve integration, preventing proper setup and visibility of on-chain data and fee routing.
Context
The application depends on environment variables to fetch live on-chain sale state and display canonical fee sink information. Currently, required variables (
VITE_TIMECURVE_ADDRESS,VITE_FEE_ROUTER_ADDRESS) are not configured, which may lead to incomplete or non-functional UI states.TimeCurve
Set
VITE_TIMECURVE_ADDRESSin.env(see.env.example) to read live onchain sale state.Canonical fee sinks (read-only)
Fee router: set
VITE_FEE_ROUTER_ADDRESSto show sink destinations.changed title from
qa setup missing stepstoQA: Setup missing stepschanged the description
changed the description
Implemented documentation and tooling to close the gap behind missing `VITE_TIMECURVE_ADDRESS` / `VITE_FEE_ROUTER_ADDRESS` during QA onboarding (merged to `main`).
Docs
Automation
@anubhav.pundir7761 please pull latest `main`, run the local stack (or QA laptop flow), then `make check-frontend-env` before `npm run dev`. If that matches what you needed, please confirm here and close this issue.
@PlasticDigits the env vars
VITE_TIMECURVE_ADDRESSandVITE_FEE_ROUTER_ADDRESSare not missing — they're populated as part of the local-stack setup.The correct flow per
scripts/qa/README.mdand issue #35 onboarding:bash scripts/start-local-anvil-stack.shfrom repo root (starts anvil, deploys contracts, writes.deploy/local.envwith canonical addresses)bash scripts/qa/write-frontend-env-local.sh(populatesfrontend/.env.localincluding the two VITE_* vars from.deploy/local.env)cd frontend && npm run devRe-verified this flow today on
52b7f04for #5 Anvil E2E —e2e-anvil.shdrives the same path and passes 3/3 (see #5 note). Env population is automatic, not a missing setup step.If the contributor was on a fresh clone and only ran
npm run devwithout the stack, the .env.local file wouldn't exist yet — that's expected behavior, not a defect.Closing as not-a-bug / operator error.
@PlasticDigits onboarding addressed on
52b7f04via check-frontend-vite-env.sh + make check-frontend-env + docs updates (QA-onboarding, TimeCurve checklist, e2e-anvil, qa README, start script). This covers the env-confusion failure mode that prompted #36. Can be closed.