issues Search Results · language:Dune language:JavaScript language:JavaScript linked:pr language:JavaScript linked:pr
Filter by
1.8M results
Description
The client-side API helper api.js is placed at the top-level of services. Grouping API communications into a subfolder
improves project cleanliness.
Proposed Changes
- Move api.js to client/src/services/api/apiClient.js. ...
Problem
Proof-standard output depends on the seat environment, but the current k6 proof substrate does not yet make seat
readiness/version drift explicit enough.
Observed during the 2026-06-27 proof-substrate ...
needs:owner
proofs:integration
proofs:k6
Description
Repeated generation of interview questions consumes unnecessary LLM tokens. Implementing a memory-cache layer helps
optimize API usage.
Proposed Changes
- Create server/services/cache/cacheManager.js. ...
Description
The application lacks a custom API error class and a centralized express error catcher, exposing internal stack traces
to the client when exceptions occur.
Proposed Changes
- Create a ...
Description
In VirtualBoothModal.jsx, all four sponsor social/website anchor tags (sponsorWebsite, sponsorLinkedin, sponsorTwitter,
sponsorGithub) render without target= _blank or rel= noopener noreferrer ...
Description
The application lacks a structured log management middleware. Moving logging logic to a dedicated module allows request
tracking and request-id injection for diagnostics.
Proposed Changes ...
Background
When #126 migrated the deploy workflows from FIREBASE_TOKEN to service-account auth (GOOGLE_APPLICATION_CREDENTIALS), a
spurious error appeared consistently at the end of every successful hosting ...
chore
When a CREATE action syncs, the server returns a real ID. Local state and remaining queued follow-up actions still
reference the temp ID, causing 404s on subsequent updates/deletes.
Fix required:
- ...
Describe the bug
In src/Pages/Projects/SubmitProject.js, the Remove image button inside the project image upload section has aria-label=
button — a meaningless value that provides no useful description ...
Problem
The current GitHub Actions workflow dispatch surface is stale against the checked-in k6 scenario tree, so the
documented/visible workflow choices are not reliable proof entrypoints.
Byte snapshot ...
needs:owner
proofs:integration
proofs:k6

Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.