Error in Development Environment

[strobel1x]

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.

[geclos]

Hey @strobel1x did you manage to make it work? We can't reproduce this internally.

[Alex-Kopylov]

I got the very same error.

[geclos]

@Alex-Kopylov what OS are you on?

[strobel1x]

Hey @strobel1x did you manage to make it work? We can't reproduce this internally.

I'm still having the same issue.

OS: Ubuntu 20.04.6 LTS
Node.js: v20.18.0

[kimdg1105]

I got the very same error and it also appears when creating 'evaluations'

OS: osx(M1) 14.3.1
node: v20.13.1, v22.13.0

Error: ENOENT: no such file or directory, open '/home/user/latitude-llm/apps/web/.next/server/app/(private)/evaluations/(evaluation)/[evaluationUuid]/editor/page/app-build-manifest.json'

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'

[kehoej]

I encountered a similar issue after setting up a local Latitude environment. When attempting to create a prompt—either within a folder or at the project’s root level—I received the following server error:

Server Error

Error: ENOENT: no such file or directory, open '/Users/kehoe/Repositories/science/latitude-llm/apps/web/.next/server/app/(private)/projects/[projectId]/versions/[commitUuid]/documents/[documentUuid]/page/app-build-manifest.json'

This error happened while generating the page. Any console logs will be displayed in the terminal window.`

As a result, it was impossible to create a prompt at any level.

[geclos]

Hey,

I'm working on dockerizing the full development experience so hopefully this will fix this issue. Will keep you posted.

[sam-fakhreddine]

Same error here:

for data points

❯ node --version
v20.11.1

[andresgutgon]

@sam-fakhreddine I don't think this will solve your issue but just in case

cd apps/web
rm -rf .next
pnpm dev

☝ What's doing this is removing .next folder which is not tracked in git and after that is starting again NextJS server

[zye1996]

is this problem fixed? still having the same problem.

[tech-and-avinash]

@sam-fakhreddine I don't think this will solve your issue but just in case

cd apps/web
rm -rf .next
pnpm dev

☝ What's doing this is removing .next folder which is not tracked in git and after that is starting again NextJS server

if this doesn't help try

pnpm build

its fine if build failed.

and then try

pnpm dev

its working for me this way

[geclos]

Update on dockerizing dev environment. I have a branch with everything set up but NextJS's performance within docker is just not acceptable (30s+ to compile the login page), so I cannot recommend we continue this route.

Apparently Next's performance issues are known.

I will spend some time trying to reproduce our issue, I'll keep you posted.

[geclos]

Ok another update: I've fixed the issue. The next error was actually caused by an issue on our end: we weren't building web's workers. I've updated the tmuxinator configuration so that we start the workers build in watch mode together with the rest of processes.

Simply pull the latest changes from main branch, start tmuxinator, and everything should work.

If you don't want to use tmuxinator, you can also build the workers package once:

cd apps/web && pnpm workers:build

Keep in mind if you change the worker's code you will need to rebuild them though.

[yigitkonur]

looking forward to see fully dockerized deployment 👀