You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've set up the development environment as described in the documentation here.
I can sign in and create a new project.
When I create a new file, it gets listed under Files, but the editor doesn't open, with the following error message:
Error: ENOENT: no such file or directory, open '/home/user/latitude-llm/apps/web/.next/server/app/(private)/projects/[projectId]/versions/[commitUuid]/documents/[documentUuid]/page/app-build-manifest.json'
In the logs I see this:
@latitude-data/web:dev: GET /projects/1/versions/11e8e9ca-57ec-4d3c-9844-b129d8132ab5/documents/2b13a2dd-3567-453d-b80a-ac6c5d7e998f 500 in 64ms
@latitude-data/web:dev: ⨯ Error: ENOENT: no such file or directory, open '/home/user/latitude-llm/apps/web/.next/server/app/(private)/projects/[projectId]/versions/[commitUuid]/documents/[documentUuid]/page/app-build-manifest.json'
When checking on the file system, I can find the folder /home/user/latitude-llm/apps/web/.next/server/app/(private)/projects/[projectId]/versions/[commitUuid]/documents, but not the folder [documentUuid] in it.
The text was updated successfully, but these errors were encountered:
I've set up the development environment as described in the documentation here.
I can sign in and create a new project.
When I create a new file, it gets listed under
Files
, but the editor doesn't open, with the following error message:Error: ENOENT: no such file or directory, open '/home/user/latitude-llm/apps/web/.next/server/app/(private)/projects/[projectId]/versions/[commitUuid]/documents/[documentUuid]/page/app-build-manifest.json'
In the logs I see this:
When checking on the file system, I can find the folder
/home/user/latitude-llm/apps/web/.next/server/app/(private)/projects/[projectId]/versions/[commitUuid]/documents
, but not the folder[documentUuid]
in it.The text was updated successfully, but these errors were encountered: