Error: Effect resolved to promise in the synchronous context, check that you marked the asynchronous calculations accordingly

[minderm]

Guys, hello!

In our project, we encountered a serious bug with the Gantt scheduler when manual scheduling was enabled for dependent tasks.

We were able to reproduce the bug in the examples on the site.

To reproduce the bug, you need to go to the example https://bryntum.com/products/gantt/examples/criticalpaths/

Further:

1. Turn off the checkbox for highlighting critical paths
2. Open the Run tests task, enable its Manually Scheduled checkbox
3. For the Configure ports task, set the start date to 01/14/2019
4. We get an error in the developer console Uncaught (in promise) Error: Effect resolved to promise in the synchronous context, check that you marked the asynchronous calculations accordingly at EngineTransaction.calculateTransitionsStackSync (gantt.module.js?474872:63:1348298)

https://github.com/bryntum/support/assets/4593213/5c8cbcf3-938c-472b-b3bc-acec7ab18fa4

[matsbryntse]

Thanks for reporting, we'll take a look!

[canonic-epicure]

Targets "master" (6.0.0 if I'm correct)

[minderm]

Targets "master" (6.0.0 if I'm correct)

Guys, is it possible to make a patch for version 5? We do not plan to update to version 6 in the near future.

[canonic-epicure]

Probably it is possible, will duplicate some effort, because of 6.0.0 refactoring, but not much, @matsbryntse?

[isglass]

Hi @minderm,

The PR with the fix for this issue contains significant changes that are not suitable to include in a patch release. We would not usually port it to older patches, but if it is a blocker for you we are open to discussing doing it as part of our Professional Services (https://bryntum.com/services)