echarts-bot[bot] commented on issue #19369:
URL: https://github.com/apache/echarts/issues/19369#issuecomment-1844730455

   @ysswebdev It seems you are not using English, I've helped translate the 
content automatically. To make your issue understood by more people and get 
helped, we'd like to suggest using English next time. 🤗
   <details><summary><b>TRANSLATED</b></summary><br>
   
   **TITLE**
   
   [Bug] When the type of the line chart is set to time, the rendered data is 
probabilistically lost and cannot be rendered on the chart.
   
   **BODY**
   
   ### Version
   
   5.4.3
   
   ### Link to Minimal Reproduction
   
   
https://test-console.milesight.com/device/detail/1731498458636455938?tab=properties
   
   ### Steps to Reproduce
   
   To enter the link, you need to enter the account password and 
[email protected]/Yeastar202
   
   ### Current Behavior
   
   The last node of the chart is worse than the actual latest data, different 
computers and different browsers perform inconsistently, at present, I have 
tested the chorme and edge browser of three people's computers, one chorme has 
no problem, the last chart of the two chome is 10 minutes different from the 
reality, that is, 10 pieces of data, 1 one-minute interval, three edges have 
problems, two are also 10 minutes, one 5 minutes
   
   ### Expected Behavior
   
   Expect the data on the chart to be complete,
   
   ### Environment
   
   ```markdown
   - OS:window 11
   - Browser: chrome latest version/edge
   - Framework:
   ```
   
   ### Any additional comments?
   
   _No response_
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to