Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrating to 4.3 Causes Parser Error on Project Reload #95620

Closed
dev-mico opened this issue Aug 16, 2024 · 4 comments
Closed

Migrating to 4.3 Causes Parser Error on Project Reload #95620

dev-mico opened this issue Aug 16, 2024 · 4 comments

Comments

@dev-mico
Copy link

dev-mico commented Aug 16, 2024

Tested versions

v4.3.stable.steam [77dcf97]

System information

v4.3.stable.steam [77dcf97]

Issue description

Every time I relaunch my project, I get a parser error on one of my classes. This means that, every time I launch the project, I need to delete the .godot folder first, allow it to reimport, and then everything works. This was not an issue before migrating my project from 4.2 to 4.3.

Steps to reproduce

I'm honestly not sure what to put here. I'm open to suggestions. If anyone has any, please let me know below. If not, then I'll see if I can reproduce this on a smaller-scale project and attach it here later.

Minimal reproduction project (MRP)

See 'steps to reproduce' - not sure how I can reproduce this right now. Open to suggestions on what may be helpful.

@akien-mga
Copy link
Member

To debug further we'd indeed need a way to reproduce the issue.

Outside of outright sharing your project (which you may not want to do, and may also be cumbersome for contributors to test with due to unnecessary complexity), the usual way to make a minimal reproduction project (MRP) is to try to narrow down which part of your project causes the issue, and extract it to a separate new project you would be willing to share.

E.g. if you get a parser error in a specific GDScript file, you can copy it (and its dependencies) to a new project, and see if it still reproduces the error. If it's still too complex, you can start removing stuff and check each time whether the parser error is reproduced, until you have something reasonably minimal.

@Jordyfel
Copy link
Contributor

Do you use preload()? People are still having some issues with it #85081

@dev-mico
Copy link
Author

Yes, I am @Jordyfel.

@dev-mico
Copy link
Author

It's impossible for me to say definitively that preload is the cause, but our team does use it all around our project. It's quite the task for us to replace all of the preload() calls. I'll close this for the time being and monitor the preload issue. I'll reopen if it's not fixed after the preload cache issue you attached.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants