Skip to content
This repository has been archived by the owner on Jun 20, 2022. It is now read-only.

Plugin crashes are not always properly detected #97

Open
jvanstraten opened this issue May 23, 2019 · 0 comments
Open

Plugin crashes are not always properly detected #97

jvanstraten opened this issue May 23, 2019 · 0 comments
Labels
bug Something isn't working lang:rust 🦀 Involves the Rust crate

Comments

@jvanstraten
Copy link
Collaborator

This is probably two issues, but I haven't investigated it fully yet. Ultimately what can happen is that DQCsim hangs when a plugin fatally crashes, specifically when an upstream plugin desyncs with a downstream plugin. So, two problems:

  • The crashing plugin should propagate its error message upstream.
  • Even if a plugin crashes so hard that it doesn't send this message, DQCsim should not wait indefinitely. It should periodically timeout its message fetching logic to check that all plugins are still alive, and propagate an error upstream if they aren't.
@jvanstraten jvanstraten added bug Something isn't working lang:rust 🦀 Involves the Rust crate labels May 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working lang:rust 🦀 Involves the Rust crate
Projects
None yet
Development

No branches or pull requests

1 participant