-
Notifications
You must be signed in to change notification settings - Fork 71
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
network2 no longer processes successful add/drop responses correctly #1583
Milestone
Comments
@wwiv i've been wracking my brains out on this one, and i know it's hacky to reset the pointer to the start, then increment through the string until the null terminator, but it appears to be the only fix for this. |
Got a test case you can share again with me, I'll take a look
…On Tue, Feb 28, 2023 at 2:10 PM xenos ***@***.***> wrote:
@wwiv <https://github.com/wwiv> i've been wracking my brains out on this
one, and i know it's hacky to reset the pointer to the start, then
increment through the string until the null terminator, but it appears to
be the only fix for this.
—
Reply to this email directly, view it on GitHub
<#1583 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQVX5Q26FNRSML4FXIAOVTWZZZTXANCNFSM6AAAAAAU7DKNXU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Here's a response packet from node 1 to node 60. |
Do I put this in as local.net to process it? |
Yes.
…On Thu, Mar 2, 2023 at 4:25 AM Rushfan ***@***.***> wrote:
Do I put this in as local.net to process it?
—
Reply to this email directly, view it on GitHub
<#1583 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABN65MONUG5HPXIFH77GM3WZ6WDLANCNFSM6AAAAAAU7DKNXU>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
--
___ Eric Manuel Pareja ***@***.***)
\e/ PGP/GPG Key 0xB82E42D9
V "Even the smallest person can change the course of the future."
-Galadriel
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
given a sub_add_resp or sub_drop_resp packet (main type 18 and main type 19) packet, with a zero (success) response, network2 doesn't identify the successful result properly.
here's an older mail with the correct email report.
here's a recent mail with the Unknown response code 83 report.
i'll attach test packets and try to identify which commit caused this.
The text was updated successfully, but these errors were encountered: