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

Godot reports error that does not exist #56482

Open
Torguen opened this issue Jan 4, 2022 · 4 comments
Open

Godot reports error that does not exist #56482

Torguen opened this issue Jan 4, 2022 · 4 comments

Comments

@Torguen
Copy link

Torguen commented Jan 4, 2022

Godot version

v3.4.2.stable.official [45eaa2d]

System information

w10 64

Issue description

With autosave after 1 second option activated
When the code is changed while the editor is running an instance, when it is run again godot reports an error that does not exist.

Watch this video (I use two monitors, in the video you will only see godot).
The first run reports an error.
I change the code.
The next run reports an error that does not exist.

2022-01-04.10-45-55.mp4

Steps to reproduce

See the video

Minimal reproduction project

...

@KoBeWi
Copy link
Member

KoBeWi commented Jan 4, 2022

Seems like the script didn't refresh in time and the game ran with part of the text that you deleted.

@Calinou
Copy link
Member

Calinou commented Jan 4, 2022

Seems like the script didn't refresh in time and the game ran with part of the text that you deleted.

Maybe this is related to #55145?

@Torguen
Copy link
Author

Torguen commented Jan 7, 2022

This may be related to the autosave option, I have it set to 1 second and it behaves strangely.

It seems that what happened is that the file was saved automatically (option autosave) when "len" was still written and not deleted, so the code was executed and then the file was automatically saved again (saved automatically when execution), but the code that was used for execution had the "len" error.

In other words, the editor confused the "autosave" of the "autosave" option with the save that the editor does when executing ?. this is only an assumption.

@Torguen
Copy link
Author

Torguen commented Feb 1, 2022

There is definitely a bug with autosave (I have it activated every 3 seconds), many times it autosaves in the middle of writing code, then runs and reports errors that don't exist.
This happens because the autosave was done in the middle of writing a code and when executing the scene (F6) it was executed with the incomplete code, this reports an error that does not exist.

The autosave should not be activated until 1 (for example) second after the last keyboard entry.
If a new pulse occurs in that period, then the timer will be restarted.

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