issues Search Results · language:Dune language:JavaScript language:JavaScript linked:pr language:HTML language:JavaScript
Filter by
2.2M results
Problem
Every search() calls getTags(), which always hits Modrinth /tag/*. If Modrinth is unreachable, getTags() throws and the
whole search returns 500 — even when the local DB is populated. This contradicts ...
alnyx-dev
Problem
The custom/ollama/opencode providers accept an arbitrary baseURL that the server then fetches server-side
(complete()/ping()). POST /api/providers/test lets a caller specify any URL and make the ...
Problem
server/index.js uses app.use(cors()) with no options, allowing any origin. All /api/providers* endpoints (create,
delete, test, set-active) and /api/search are unauthenticated. The server also ...
Problem
The client only ever receives masked keys (getSavedSafe → ***1234). When that masked value is submitted back (e.g.
editing a provider without changing the key), save() tries to restore the real ...
Problem
parseJsonFromAI uses a greedy /\{[\s\S]*\}/ match (first { to last }). When the model returns prose with multiple
objects or stray braces, JSON.parse fails, degrading ranking to the fallback path. ...
Several smaller correctness/hygiene items:
1. Missing engines — the code uses the global fetch (Node 18+) but package.json has no engines; on Node 18 it fails
with an opaque fetch is not defined. ...
Problem
In GET /api/search/stream (server/router.js), the 120s timeout sends an error event but does not end the response — the
socket stays open until orchestrator.search eventually settles. There is ...
Problem
In public/app.js, createResultCard escapes text fields (title, description, explanation) but interpolates several values
into the DOM without escaping/validation:
- img src= ${r.icon_url} ...
Problem
fillTemplate in server/orchestrator.js replaces tokens sequentially with reduce + replaceAll. Because {userQuery} is
substituted before {results}/{searchParams}, a user query containing the literal ...
Observation
A single cw-ship run that planned two feedback:new issues in parallel crossed their GitHub issue bodies: one issue s
full body content was written into the other issue, and the recipient issue ...
feedback:triaging
feedback
ALRubinger
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.
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.