ID 509813 - Bake Points fire too many bakedStateChanged signals

Problem summary
Bake Points fire too many bakedStateChanged signals
 
Customer reported version
Mari 5.0v2
 
Customer reported platform
Windows 10
 
Steps to reproduce
 
1) Open an Example Project
 
2) Run the attached script in the Python Console 
 
3) Create a Wood node
 
4) Create a Bake Point node (256x256, 8-bit)
 
5) Connect the Wood node's output to the Bake Point's input
 
6) Clear the output in the Python console
 
7) In the Bake Point node properties, click Bake
 
8) Check the Python Console output
Notice that two 'BAKEPOINTSTATE_UP_TO_DATE' messages are returned instead of one
 
In Mari 5.0/4.8 only:
 
9) Clear the Python Console output
 
10) Click on 'Edit Filters'
 
11) Check the Python Console output
Notice that two more 'BAKEPOINTSTATE_UP_TO_DATE' messages are returned
 
12) Add a Invert Filter from the list. Click Apply
 
13) Check the Python Console output
Notice that 10 more 'BAKEPOINTSTATE_UP_TO_DATE' messages are returned - two per-UDIM
 
Expected behaviour
One bakedStateChanged signal should be emitted when when the bake state of the Bake Point node changes.
 
Actual behaviour
Two bakedStateChanged signals are emitted when the Bake Point is baked.
In 4.8 and 5.0:
Two bakedStateChanged signals are emitted when the Edit Filters dialog is opened
Two bakedStateChanged signals are emitted per-UDIM when Filters are applied i.e. 10 signals in the Example Project (5 UDIMs)
 
Workaround
Unknown.
 
Reproduced by support
This bug has been reproduced in:
Mari 5.0v2 - Windows 10 - CentOS 7.9
Mari 4.8v2 - Windows 10
Mari 5.0v1 - Windows 10
Mari 4.7v1 - Windows 10
Mari 4.6v1 - Windows 10 - CentOS 7.9 - regression
Note: In Mari 4.6v1, one of the two messages returned after baking is 'BAKEPOINTSTATE_NOT_AVAILABLE' instead of 'BAKEPOINTSTATE_UP_TO_DATE'
 
Unable to reproduce bug in:
Mari 4.5v2 - Windows 10 - CentOS 7.9
 
Earliest version tested
Mari 4.5v2 - This issue doesn't appear in this version and has regressed