-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Error when viewing TimeSeries label task #3094
Comments
@PaulSch01 Is it possible to share labeling config and csv sample data where you have this problem? |
Yes, of course. It doesn't always freeze using this example data and config, but I'd say 80% of the time it does for me.
|
Hey @PaulSch01 👋 . I'll take a look into it, this appears to be an issue with the quickview initializing the data graph twice, and in some circumstances its causing a runaway hydration. |
Just adding that I am seeing the same behaviour if it helps: the
I can load a file with 572664 samples within a second or two via the
|
I have this issue too which appeared only after I deleted annotations. |
I generated an internal ticket to get this looked into further. The issue across all reported cases comes down to the initialization methods used for the data between label stream (Label all tasks button) and quick view (selecting a task in the data manager table). As of right this moment I can't pinpoint the exact issue, but based on the logs seen here the data in the fast loading case (label stream) is doing so because the data is loaded directly into memory, where as the slow case it is getting caught in what looks like a data merge that is firing a handful of other calculations, when it should reasonably just be doing a strict replacement. |
Is there any new on this issue or a workaround? So label studio could be used for time serie annotation? |
Ok, I figured out by removing the timezone information after the datetime seems to solve the issue. |
Any update on this? |
Set up a new issue for this specific datetime format issue, which could be masking some of this behavior. #6589 |
Describe the bug
In the newest development Environment, when opening a TimeSeries task for labeling the tab freezes/gets stuck on loading. The console gets flooded with a mobx-state-tree error stating that It's trying to read or write to an object that is no longer part of a state tree. (See Screenshot).
This happens specifically when clicking on a single task, when "Label all tasks" is used the TimeSeries still doesn't load, and the console instead shows:
"[mobx.array] Attempt to read an array index (0) that is out of bounds (0). Please check length first. Out of bound indices will not be tracked by MobX instrument.js:109:45".
To Reproduce
Steps to reproduce the behavior:
Expected behavior
TimeSeries should render after a short time
Screenshots
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: