Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Engine exception when reapply data on filtered dataset #7859

Closed
chuckn0rris opened this issue Nov 13, 2023 · 3 comments
Closed

Engine exception when reapply data on filtered dataset #7859

chuckn0rris opened this issue Nov 13, 2023 · 3 comments
Assignees
Labels
angular Angular framework integration bug Something isn't working forum Issues from forum high-priority Urgent to have fixed large-account Reported by large customer OEM OEM customer resolved Fixed but not yet released (available in the nightly builds)
Milestone

Comments

@chuckn0rris
Copy link

Forum post

Launch the app, click Refresh button on tbar, it will just re-apply data into project.
Tried to replicate in Vanilla, no luck.
If comment resourceStore filtering, no expception will be triggered.
If set all stores data with empty array before set real data - it will also fix an exception.

issue_bryntum_with_histogram.zip

@chuckn0rris chuckn0rris added bug Something isn't working forum Issues from forum large-account Reported by large customer OEM OEM customer labels Nov 13, 2023
@CArnaboldi
Copy link

any update on this?

@chuckn0rris chuckn0rris added the angular Angular framework integration label Jan 25, 2024
@isglass isglass added the high-priority Urgent to have fixed label Jan 25, 2024
@chuckn0rris
Copy link
Author

Hi, no progress yet, but we flagged this as high-prio. So, things should go faster from now!

@canonic-epicure
Copy link

After brief investigation, it seems what happens is:

  • The resource store is filtered.
  • When data is loaded into the filtered store, the commitAsync is called immediately (synchronously) after
  • This breaks the optimization we have for loading data into several stores, which "holds" the commit until changes to all stores are written, so commit starts in the middle of data loading
  • This somehow rejects the ongoing transaction (from the previous ongoing commit - this part is not clear) and triggers those errors

Probably will need to coordinate the filtering after data load with the data load optimizations. Investigating further.

@canonic-epicure canonic-epicure added ready for review Issue is fixed, the pull request is being reviewed and removed in progress labels Feb 13, 2024
@isglass isglass added resolved Fixed but not yet released (available in the nightly builds) and removed ready for review Issue is fixed, the pull request is being reviewed labels Feb 15, 2024
@isglass isglass added this to the 5.6.7 milestone Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
angular Angular framework integration bug Something isn't working forum Issues from forum high-priority Urgent to have fixed large-account Reported by large customer OEM OEM customer resolved Fixed but not yet released (available in the nightly builds)
Projects
None yet
Development

No branches or pull requests

4 participants