Open hisprofile opened 1 month ago
So the log that you provided is produced all at once? I have never seen that type of behavior...
Is this add-on visible as duplicates in blender settings? Maybe check if there are multiple links in your add-on folder bpy.utils.user_resource("SCRIPTS", path="addons")
Does the add-on even works despite of this message spam?
Or even easier: try to ru your add-on in clean blender config. The easiest (and non destructive) way to do it is to set env car, see https://github.com/JacquesLucke/blender_vscode?tab=readme-ov-file#how-can-i-separate-development-environment-from-my-daily-work
This pretty new readme section.
I noticed that this issue occurs only in Debug window in VS code. If you take a look at Terminal window the it works fine. i with we could make terminal be focused by default, but I do not know how...
I am getting close: when blender fails to start, some operations are still scheduled to be performed; the are performed when new blender instance comes online. To be investigated further.
The "queue" is not cleared unless vs code is restarted, so it might be issue with RunningBlenders
, just a gues
I'm not sure if it's something about the addon I'm developing, I don't even know where to begin debugging.
Upon saving a file to reload the addon, it absolutely spams pings to reload the addon. I do not know what else I can say about that.