Project does not compile after any change is done

latitude-dev / latitude

Developer-first embedded analytics

https://latitude.so

GNU Lesser General Public License v3.0

626 stars 21 forks source link

Project does not compile after any change is done #320

Closed abgonzalez93 closed 3 weeks ago

abgonzalez93 commented 3 weeks ago

Steps To Reproduce

I have my project running on Ubuntu. I do a change on my code (View, queries, whatever). After saving the file, the project does not detect the new changes. You have to stop and re-run it again.

Environment

Node version (node -v): 18.20.2
npm version (npm -v): 10.5.2
OS: Ubuntu 22.04.3**

Expected Behavior

Is not it supposed to be reactive? (Every change is compiled in real-time)

geclos commented 3 weeks ago

hey @abgonzalez93 it is indeed supposed to be reactive.

What Latitude CLI version and Latitude project version are you on?

latitude cli version: latitude --version
latitude project version: check latitude.json at the root of your project you'll see the version there

abgonzalez93 commented 3 weeks ago

latitude cli version: latitude --version

imagen

latitude project version: check latitude.json at the root of your project you'll see the version there

imagen

geclos commented 3 weeks ago

@abgonzalez93 I'm not able to reproduce. Could you share a repo with the reproducible bug? Also try updating to latest CLI version, there's a bugfix related to CLI syncing that might be affecting you. npm update -g @latitude-data/cli

abgonzalez93 commented 3 weeks ago

CLI is up to date.

Whenever I save a file after a change is done, I get those errors on console (but it's supposed to be a favicon missing error) imagen

I've uploaded Netflix test project to my GitHub repo. (.latitude folder is missing. Github doesnt upload it. I suppose doing latitude setup command you download it) https://github.com/abgonzalez93/latitude-syncing-error.git

In either case, tell me whatever you need

geclos commented 3 weeks ago

yeah don't worry about the favicon issue, is just a warning that we need to take care but it does not cause any issue. Also it's normal that .latitude is not included in github 👌🏼

I will test it in a similar environment and come back to you.

geclos commented 3 weeks ago

hey @abgonzalez93 I'm not able to reproduce your issue with the repo you shared. My settings just so we are in sync:

ubuntu 22.04
latitude project v 0.11.0
latitude CLI version 0.8.2
node version 18

Some general recommendations that I've seen solving issues in other projects running in ubuntu:

run apt install -y build-essential xdg-utils. Usually these come preinstalled with ubuntu but might not be your case
increase the inotify watch limit. Guide here.
If you are using wsl, it has some known issues with file watching that might be interfering with latitude's watchers. But this is just an hypothesis, since I don't have a windows machine to test with.

Let me know if any of this helps

abgonzalez93 commented 3 weeks ago

I'm actually using WSL, so that might be a possible cause. Anyway, I'm gonna try to reinstall build-essentials and search for information about WSL issues. Ill let you know as soon as I know what's happening

abgonzalez93 commented 3 weeks ago

I got to solve it. I'm currently using WSL on my Windows 11. I was connecting to WSL files vía VS Code (but using a plain directory URL) and somehow, as you said, that interfered with latitude's watchers. I downloaded and configured WSL extension. Accessed to the project and now, running Ubuntu on VS Code terminal, changes are syncing perfectly.

https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl

Hope this helps to others.

geclos commented 3 weeks ago

updated the docs accordingly 👌🏼