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

Suspected 1-Wire deadlock in Reactive implementation #223

Open
climategadgets opened this issue Dec 10, 2021 · 1 comment
Open

Suspected 1-Wire deadlock in Reactive implementation #223

climategadgets opened this issue Dec 10, 2021 · 1 comment
Labels
1-wire $$$ bug FATAL reactive Pertinent to Reactive branches only reactive-straggler Regression from imperative to reactive code base
Milestone
Migrate to Reacti...

Comments

@climategadgets
Copy link
Member

Expected Behavior

The system works

Actual Behavior

The system stops responding at random following triggers. Known triggers at this point:

  • Manually changing the setpoint via ReactiveConsole
  • Setpoint change executed via Google calendar updater

Acceptance Criteria

  • The system keeps working normally when trigger actions are executed.
@climategadgets climategadgets added bug FATAL $$$ stable-not-affected Issues with this label affect only the development branches reactive Pertinent to Reactive branches only labels Dec 10, 2021
@climategadgets climategadgets modified the milestones: Migrate to Reactive Streams, Priority List Jan 2, 2022
@climategadgets climategadgets changed the title Suspected deadlock in Reactive implementation Suspected 1-Wire deadlock in Reactive implementation Aug 20, 2022
@climategadgets
Copy link
Member Author

[late update] It has been identified that this is only happening if 1-Wire actuators and/or complex 1-Wire networks are used, XBee and ESPHome based installations work as expected. Possible cause: #221

@climategadgets climategadgets mentioned this issue Feb 4, 2023
Closed
@climategadgets climategadgets removed the stable-not-affected Issues with this label affect only the development branches label Dec 1, 2023
@climategadgets climategadgets added the reactive-straggler Regression from imperative to reactive code base label Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1-wire $$$ bug FATAL reactive Pertinent to Reactive branches only reactive-straggler Regression from imperative to reactive code base
Projects
None yet
Milestone
Migrate to Reactive Streams
Development

No branches or pull requests
1 participant
@climategadgets