We merged your local files with your environment's files 10 times, but your local and environment's
Hi, I ran into this issue and Ihave narrowed the problem the problem down to permissions on Windows. Is there a way I can very quickly skip/fix this locally? The sync works but the server won't start due to the issue mentioned, so hot reloading is not working for me during development phase.
https://github.com/gadget-inc/ggt/issues/1707
14 Replies
Hello,
Sorry for the late reply, I wanted to bring this forward to the person with the best knowledge of ggt. I'll pass this on as soon as possinble. I just wanted to make sure you knew we didn't forget about you
Thanks Antoine. Appreciate your response. Meanwhile if there is anything I can do temporarily to get past this, I'd love to keep moving.
For instance, I was wondering if I always return true for
isEqualHash method, would it be okay temporarily
https://github.com/gadget-inc/ggt/blob/96ff9ac4d30072aaf95e6f36f1f63338479b4918/src/services/filesync/hashes.ts#L149Would you be able to see if downgrading to a previous ggt version might fix the issue?
I'm having someone else jump on this as I realize that the other person is on vacation this week
Thanks, Antoine. I did try v1.6 but same problem.
Hey @The Protagonist sorry you're running into this.
I don't believe the file permissions mismatch is the issue given that you’re on Windows. We only consider/set Unix permissions on Linux or macOS (supportsPermissions: https://github.com/gadget-inc/ggt/blob/main/src/services/filesync/directory.ts#L282).
From the screenshot you posted in the GitHub issue, the SHA‑1s match, so isEqualHash would already be returning true (we compare only the SHA‑1).
Other developers have reported resoling this by removing and reinstalling their dependencies . If you haven’t tried that yet, would you mind giving it a shot.
If you’re still seeing the issue, please run
ggt dev --verbose and sharing the logs with us.
Another thing that may potentially work is running ggt dev --prefer local to force conflicts to resolve in favour of your local files. This may help you get past the issue you are seeing. Though, only use it only if you’re okay overwriting remote changes to what you have locally.Thanks @Mitch . I tried deleting whole node_modules (both global and local, and I also deleted the entire project and tried a different path as well). I also tried the local command.
Would you like me to send whole logs or is error id sufficient?
Also, is there a way I could run the unminified/dev release to debug this better?
npm install -g github:gadget-inc/ggt wont give me access to ggt in cliCould you send over all logs if possible. The trace ID doesn't seem to return anything on my end unfortunately.
@Mitch can I Inbox you the logs?
yes, the CONTRIBUTING.md file will contains everything needed to run the ggt project locally
https://github.com/gadget-inc/ggt/blob/main/CONTRIBUTING.md
Oh Thanks. I'll give it a shot myself and update you in case I find anything
Sounds great!
Ya definitely feel free to send that to me directly
Hey @[Gadget] Mitch , good morning! I have realized that the error shows up in every app I create. It's all good until I work in dev, but as soon as I make the first deploy into production the bug is triggered. I will share the logs with you
hmmm that sounds very strange!
Do you like this answer?