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

Check why we might emit a .dead for "current" node when "previous" was dead #91

Open
ktoso opened this issue Nov 1, 2022 · 0 comments
Open

Check why we might emit a .dead for "current" node when "previous" was dead #91

ktoso opened this issue Nov 1, 2022 · 0 comments
Assignees
@ktoso
Labels
0 - new Not sure yet if task is valid / going to be worked on

Comments

@ktoso
Copy link
Member

ktoso commented Nov 1, 2022

More details in: apple/swift-distributed-actors#1083

and I wonder if this is a bug in SWIM itself how we handle an incoming dead + alive of the same endpoint, but different node.
Might be missing a nid check somewhere.
@ktoso ktoso added the 0 - new Not sure yet if task is valid / going to be worked on label Nov 1, 2022
@ktoso ktoso self-assigned this Nov 1, 2022
@ktoso ktoso mentioned this issue Nov 1, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ktoso ktoso

Labels
0 - new Not sure yet if task is valid / going to be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ktoso