CollectionProperty declarations throwing errors randomly #61159
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#61159
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Win 10
Graphics card: NVIDIA GTX 1060
Blender Version
Broken: 2.80, 2019-01-22
Short description of error
CollectionProperty randomly throwing registration error.
Exact steps for others to reproduce the error
Declarations are as follows:
Full error is as follows
Added subscriber: @DharmaTejaReddyK
Added subscriber: @JacquesLucke
Did you register
RenderLayersToInclude
before you registeredConfigCreatorOperator
?Yes... I registered RenderLayersToInclude before ConfigCreatorOperator
Error is not consistant... It'll error out very randomly / unpredictable. There are no preferences or any initialization lines before registering.
Here is registration code (snapshot)
Can you share a small complete example that we can use to reproduce the issue?
BlenderBug_T61159.mp4
Find bug behavior in above video attachment. It errors out very randomly. No specific pattern.
Find source code below (video is recorded with following source code only)
BlenderBug_T61159.py
Changed status from 'Open' to: 'Archived'
I found two problems in the code.
dtrClasses
object is aset
instead oftuple
orlist
. In Python sets have no ordering guarantees (yet?). That is probably the reason why the problem only appears sometimes.register_class
in theunregister
function.You're correct. I changed it to tuple and no there's no error after that. Thanks for correction. I didn't know ordering issue with sets. New learning today :)
It's my bad. While trimming code base to provide example for you, I made that mistake.
We can close this ticket.