You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue tracks a slight inconsistency between the tx queue and overlay when it comes to validating transactions against max allowed size. Specifically, tx queue takes into account envelope size only (
I thought the idea was to use full tx size across codebase; the limit itself is bandwidth-related, and we never flood just the tx portion of the tx envelope, so it makes sense to count the whole transaction. If we don't, this is also problematic for overlay as it relies on txMaxSizeBytes for calculations that expect full tx size.
This issue tracks a slight inconsistency between the tx queue and overlay when it comes to validating transactions against max allowed size. Specifically, tx queue takes into account envelope size only (
stellar-core/src/transactions/TransactionFrame.cpp
Line 603 in 287fe4c
stellar-core/src/overlay/FlowControlCapacity.cpp
Line 76 in 287fe4c
We should ensure we validate size consistently to prevent any unnecessary drops at the overlay layer.
The text was updated successfully, but these errors were encountered: