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

Crash after destroying scheduler and setting timeZoneon the project when using TimeRanges features #7992

Closed
matsbryntse opened this issue Dec 5, 2023 · 0 comments
Assignees
Labels
bug Something isn't working forum Issues from forum large-account Reported by large customer resolved Fixed but not yet released (available in the nightly builds)
Milestone

Comments

@matsbryntse
Copy link
Member

Forum post

Hi,

I'm also using time zones (vue3) and sometimes run into this issue when loading the scheduler.
I can't provide a test case since it is a rare occurrence but I have error reports from multiple users unable to load due to this bug.

When reloading the page after the bug it does load so it isn't something consistent.

errorlog.png

Gerts
errorlog.png

@matsbryntse matsbryntse added bug Something isn't working forum Issues from forum large-account Reported by large customer labels Dec 5, 2023
@matsbryntse matsbryntse changed the title Bryntum scheduler crash after destroying scheduler and setting timeZoneon the project Crash after destroying scheduler and setting timeZoneon the project when using TimeRanges features Dec 5, 2023
@matsbryntse matsbryntse self-assigned this Dec 5, 2023
@matsbryntse matsbryntse added ready for review Issue is fixed, the pull request is being reviewed 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 Dec 5, 2023
@matsbryntse matsbryntse added this to the 5.6.3 milestone Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working forum Issues from forum large-account Reported by large customer resolved Fixed but not yet released (available in the nightly builds)
Projects
None yet
Development

No branches or pull requests

1 participant