continuedev / continuedev/continue

After switching windows, link to file in other window causes error

Open
#3,665 4 comments 0 reactions 1 assignee View on GitHub

@RomneyDa is already working on this.

Since Jan 9, 2025.

ide:vscode kind:bug needs-triage os:mac
Dominant language
TypeScript
Stars
36k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Before submitting your bug report
Relevant environment info
- OS:*
- Continue version:0.8.66
- IDE version:VSC
Description

Either we're not gracefully handling files that aren't found in the workspace, OR it's a problem with the brackets in the path. I think the former

To reproduce

No response

Log output
Invalid uri: /Users/natesesti/Documents/continue-all/remote-config-server/app/app/onboarding/redirect/[ideScheme]/page.tsx
Error: Invalid uri: /Users/natesesti/Documents/continue-all/remote-config-server/app/app/onboarding/redirect/[ideScheme]/page.tsx
    at findUriInDirs (http://localhost:5173/@fs/Users/natesesti/Desktop/continue/core/util/uri.ts:21:15)
    at FilenameLink (http://localhost:5173/src/components/markdown/FilenameLink.tsx:28:40)
    at renderWithHooks (http://localhost:5173/node_modules/.vite/deps/chunk-V5LT2MCF.js?v=9d70d634:11568:26)
    at mountIndeterminateComponent (http://localhost:5173/node_modules/.vite/deps/chunk-V5LT2MCF.js?v=9d70d634:14946:21)
    at beginWork (http://localhost:5173/node_modules/.vite/deps/chunk-V5LT2MCF.js?v=9d70d634:15934:22)
    at beginWork$1 (http://localhost:5173/node_modules/.vite/deps/chunk-V5LT2MCF.js?v=9d70d634:19781:22)
    at performUnitOfWork (http://localhost:5173/node_modules/.vite/deps/chunk-V5LT2MCF.js?v=9d70d634:19226:20)
    at workLoopSync (http://localhost:5173/node_modules/.vite/deps/chunk-V5LT2MCF.js?v=9d70d634:19165:13)
    at renderRootSync (http://localhost:5173/node_modules/.vite/deps/chunk-V5LT2MCF.js?v=9d70d634:19144:15)
    at recoverFromConcurrentError (http://localhost:5173/node_modules/.vite/deps/chunk-V5LT2MCF.js?v=9d70d634:18764:28)
Restart

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.