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

[BUG] Incorrect connector status after startup in UI server #1042

Open
1 task done
jerome-benoit opened this issue Jun 6, 2024 · 0 comments
Open
1 task done

[BUG] Incorrect connector status after startup in UI server #1042

jerome-benoit opened this issue Jun 6, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@jerome-benoit
Copy link
Contributor

Duplicate issue

  • 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

Expected result

No response

Actual result

No response

Steps to reproduce

No response

Attachments

No response

@jerome-benoit jerome-benoit added bug Something isn't working triage Needs triage and removed triage Needs triage labels Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant