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.

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

feat: [MR-607] Ignore non-matching best-effort responses #1517

Merged

Conversation

alin-at-dfinity
Copy link
Contributor

A best-effort response may be inducted after the matching call context has already expired; the reject response has been executed; and the call context was dropped. Because of this (and as opposed to guaranteed responses, where a duplicate or non-matching callback implies malicious behavior or a bug) best-effort responses that are either duplicates or don't match an existing callback should be silently dropped.

A best-effort response may be inducted after the matching call context has already expired; the reject response has been executed; and the call context was dropped. Because of this (and as opposed to guaranteed responses, where a duplicate or non-matching callback implies malicious behavior or a bug) best-effort responses that are either duplicates or don't match an exosting callback should be silently dropped.
@github-actions github-actions bot added the feat label Sep 16, 2024
@alin-at-dfinity alin-at-dfinity changed the title feat: [MR-607] Ignore mismatching best-effort responses feat: [MR-607] Ignore non-matching best-effort responses Sep 17, 2024
Copy link
Contributor

@derlerd-dfinity derlerd-dfinity left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you. LGTM.

@alin-at-dfinity alin-at-dfinity added this pull request to the merge queue Sep 18, 2024
Merged via the queue into master with commit 70dc1a7 Sep 18, 2024
30 checks passed
@alin-at-dfinity alin-at-dfinity deleted the alin/MR-607-mismatching-best-effort-responses branch September 18, 2024 17:36
levifeldman pushed a commit to levifeldman/ic that referenced this pull request Oct 1, 2024
A best-effort response may be inducted after the matching call context
has already expired; the reject response has been executed; and the call
context was dropped. Because of this (and as opposed to guaranteed
responses, where a duplicate or non-matching callback implies malicious
behavior or a bug) best-effort responses that are either duplicates or
don't match an existing callback should be silently dropped.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants