Skip to content

Document bounced fallback receivers do not get 0xFFFFFFFF in the input slice #1673

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
Open
anton-trunov opened this issue Feb 1, 2025 · 0 comments
Open

Document bounced fallback receivers do not get 0xFFFFFFFF in the input slice #1673

anton-trunov opened this issue Feb 1, 2025 · 0 comments
Assignees
@novusnota
Labels
feature: receivers Process internal, external, bounced incoming messages kind: docs Documentation for docs.tact-lang.org kept in docs folder
Milestone
Doc: 2025-04

Comments

@anton-trunov
Copy link
Member

We need to mention the prefix of a bounced message contains 0xFFFFFFFF which we cut off before processing the message slice in the bounced fallback receiver.
@anton-trunov anton-trunov added the kind: docs Documentation for docs.tact-lang.org kept in docs folder label Feb 1, 2025
@anton-trunov anton-trunov added this to the Doc: 2025-02 milestone Feb 1, 2025
@anton-trunov anton-trunov added the feature: receivers Process internal, external, bounced incoming messages label Feb 25, 2025
@novusnota novusnota modified the milestones: Doc: 2025-02, Doc: 2025-03 Mar 2, 2025
@novusnota novusnota modified the milestones: Doc: 2025-03, Doc: 2025-04 Mar 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@novusnota novusnota

Labels
feature: receivers Process internal, external, bounced incoming messages kind: docs Documentation for docs.tact-lang.org kept in docs folder
Projects
None yet
Milestone
Doc: 2025-04
Development

No branches or pull requests
2 participants
@anton-trunov @novusnota