dohertj2/ScadaBridge
1
0
Fork 0
Code Issues 42 Pull Requests Actions Packages Projects Releases Wiki Activity

Plan a replacement for deprecated Akka AutoDowning before an Akka.NET upgrade removes it #51

New Issue
Open
opened 2026-11-06 15:24:38 -05:00 by dohertj2 · 0 comments
dohertj2 commented 2026-11-06 15:24:38 -05:00
Owner
Copy Link
Copy Source

Register row 70 (deferred-work register).

Akka.NET 1.5.62 warns on every boot that auto-down-unreachable-after is deprecated ("keep-majority will be used instead"). Drill-verified that the substitution does NOT happen while downing-provider-class = Akka.Cluster.AutoDowning is explicit (BuildHocon sets it), so the 2026-07-21 availability-first decision holds today. The risk is a future Akka.NET bump deleting AutoDowning.

Revisit trigger (from register): Any Akka.NET version bump — re-run DRILL_MODE=active bash docker/failover-drill.sh and read the release notes before accepting it.

Current state: Standing risk; no replacement downing provider designed.
Related: docs/plans/2026-07-21-auto-down-availability-decision.md.

Source: docs/plans/2026-07-08-deferred-work-register.md row 70

Register row 70 (deferred-work register). Akka.NET 1.5.62 warns on every boot that `auto-down-unreachable-after` is deprecated ("keep-majority will be used instead"). Drill-verified that the substitution does NOT happen while `downing-provider-class = Akka.Cluster.AutoDowning` is explicit (BuildHocon sets it), so the 2026-07-21 availability-first decision holds today. The risk is a future Akka.NET bump deleting `AutoDowning`. **Revisit trigger (from register):** Any Akka.NET version bump — re-run `DRILL_MODE=active bash docker/failover-drill.sh` and read the release notes before accepting it. **Current state:** Standing risk; no replacement downing provider designed. Related: `docs/plans/2026-07-21-auto-down-availability-decision.md`. Source: `docs/plans/2026-07-08-deferred-work-register.md` row 70
dohertj2 added the type:debtpriority:p2migrated labels 2026-11-06 15:24:38 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked
Blocked by dependency or external hold
 cross-repo
Needs coordinated change in another family repo (wire contract etc.)
 migrated
Migrated from a markdown backlog (2026-11 standardization)
 priority:p0
Must-have / blocking
 priority:p1
High priority
 priority:p2
Normal priority
 priority:p3
Low priority / nice to have
 type:bug
Defect in shipped behaviour
 type:debt
Technical debt / hygiene
 type:deploy-gate
Rollout/deploy/migration step not yet done on an environment
 type:docs
Documentation work
 type:feature
Feature implementation
 type:followup
Follow-up deferred from a plan, PR or gate
 type:infra
Infrastructure and scaffolding
 type:review-finding
Unfixed finding from an architecture/code review
 type:test
Test work
No Label migrated priority:p2 type:debt
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/ScadaBridge#51
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?