[X] I've searched for any related issues and avoided creating a duplicate issue.
Component
Simulator
Description
The charging stations statuses are cached in the main thread in a map. The map is populated from workers via a dedicated message channel. The event emission sending the CS status is happening after promise resolutions that are not chronologically ordered. Though the cache can be populated by content not up to date.
Version
1.3.3
Node.js version
22.2.0
System
OS: Linux 6.8 Fedora Linux 40 (Workstation Edition)
CPU: (20) x64 13th Gen Intel(R) Core(TM) i7-13700H
Memory: 35.86 GB / 62.52 GB
Container: Yes
Shell: 5.9 - /usr/bin/zsh
Duplicate issue
Component
Simulator
Description
The charging stations statuses are cached in the main thread in a map. The map is populated from workers via a dedicated message channel. The event emission sending the CS status is happening after promise resolutions that are not chronologically ordered. Though the cache can be populated by content not up to date.
Version
1.3.3
Node.js version
22.2.0
System
OS: Linux 6.8 Fedora Linux 40 (Workstation Edition) CPU: (20) x64 13th Gen Intel(R) Core(TM) i7-13700H Memory: 35.86 GB / 62.52 GB Container: Yes Shell: 5.9 - /usr/bin/zsh
Expected result
No response
Actual result
No response
Steps to reproduce
No response
Attachments
No response