We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ilpv4-connector/connector-service-impl/src/main/java/org/interledger/connector/packetswitch/filters/MaxPacketAmountFilter.java
Lines 32 to 50 in f642e1b
Release v0.5 does appear to return any metadata in F08s; I imagine this could cause issues for legacy STREAM senders paying into it.
(My sender performs a binary search and was still able to precisely discover the max packet amount in this case 😉)
The text was updated successfully, but these errors were encountered:
Can you clarify what you mean by meta-data here?
Sorry, something went wrong.
Encoding the received amount and max packet amount into the data portion of the Reject packet: #260, hyperledger-archives/quilt#186
Oh nice - my bad. Good catch!
No branches or pull requests
ilpv4-connector/connector-service-impl/src/main/java/org/interledger/connector/packetswitch/filters/MaxPacketAmountFilter.java
Lines 32 to 50 in f642e1b
Release v0.5 does appear to return any metadata in F08s; I imagine this could cause issues for legacy STREAM senders paying into it.
(My sender performs a binary search and was still able to precisely discover the max packet amount in this case 😉)
The text was updated successfully, but these errors were encountered: