ID 576106 - A "duration must be at least 1" error will occur when importing AAFs if a Transition is followed by a Filler Effect with the same or shorter duration

Problem summary:
A "duration must be at least 1" error will occur when importing AAFs if a Transition is followed by a Filler Effect with the same or shorter duration
 
This is known to impact Dissolve Transitions and Fillers with a Color Effect or Paint Effect, but likely also occurs with other Transitions and Filler Effects.
 
Customer reported version:
Flix 6.6.2
 
Customer reported platform:
macOS 13 Ventura
 
Steps to reproduce:
1) Launch Flix and navigate to File > Preferences... > Third Party Apps > Editorial Tools, and set Avid Media Composer as the Editorial Tool.
2) Create a new Sequence Revision and Import 1 panel.
3) Publish this Revision to Editorial, and open the AAF in Avid.
4) Create a 2 frame gap by moving the Clip to the right, and add a Paint Effect to this gap.
5) Reposition the Timeline so the Filler Paint Effect is now after the Clip.
6) Place the Playhead near the end of the Clip, and press the \ key to open the Quick Transition menu.
7) Create a Dissolve Transition with a 2 frame duration:

 
8) Export this AAF and Import it into Flix, observing the error that occurs: Could not import sequence: Server error, client request is invalid: RevisionedPanel(2, 0 frames) invalid: duration must be at least 1

 
Expected behavior:
The AAF should import without issue, regardless of the relationship between the duration of a Transition and the duration of a Filler Effect on the same Track.
 
Actual behavior:
An AAF containing a Transition followed by a Filler Effect will not import successfully into Flix if the Transition is longer or the same duration as the Filler Effect. When the Transition is longer than the Filler Effect, a negative frame duration will appear in the error message, like so:

 
If a gap is introduced between the Transition and Filler, the following error occurs:

 
But if the Clip, gap, and Filler are located on a higher track than V1, the original error will appear instead:

 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
Flix Client 7.0.1 - Windows 10 | Flix Server 7.0.1 - CentOS 7
Flix Client 6.6.2 - Windows 10 | Flix Server 6.6.2 - CentOS 7
Flix Client 6.6.0 - Windows 10 | Flix Server 6.6.0 - CentOS 7
Flix Client 6.5.1 - Windows 10 | Flix Server 6.5.1 - CentOS 7
 
Earliest version tested:
Flix 6.5.1 - This issue appears to be in all tested versions of the product