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.

Sign up for GitHub

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

Jump to bottom

Don't send or respond to HTTP or MQTT requests while importing a database #987

Open
scottgonzalez opened this issue Jun 18, 2024 · 0 comments
Open

Don't send or respond to HTTP or MQTT requests while importing a database #987

scottgonzalez opened this issue Jun 18, 2024 · 0 comments
Labels
L3 annoyance Not easily used, hard to understand, slightly incorrect but workable

Comments

@scottgonzalez
Copy link
Collaborator

scottgonzalez commented Jun 18, 2024 •
edited
Loading

When importing a database, the server will respond to requests before all platforms have been loaded. This means that in a competition with platforms A, B, and C, any requests for platforms B or C may get a response for platform A as soon as owlcms has processed enough to load platform A. The server should not respond to requests until all platforms have been loaded.
@scottgonzalez scottgonzalez added the L3 annoyance Not easily used, hard to understand, slightly incorrect but workable label Jun 18, 2024
@scottgonzalez scottgonzalez changed the title owlcms responds to requests on start too early server responds to requests on start too early Jun 18, 2024
@scottgonzalez scottgonzalez changed the title server responds to requests on start too early Don't send or respond to HTTP or MQTT requests while importing a database Jun 20, 2024
@jflamy jflamy added this to owlcms Jun 20, 2024
@jflamy jflamy moved this to Backlog in owlcms Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
L3 annoyance Not easily used, hard to understand, slightly incorrect but workable
Projects
owlcms
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@scottgonzalez