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.

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

fix: Fix PayloadProcessor response payload race condition #120

Merged
merged 1 commit into from
Nov 24, 2023
Merged

fix: Fix PayloadProcessor response payload race condition #120

merged 1 commit into from
Nov 24, 2023

Commits on Nov 23, 2023

  1. fix: Fix PayloadProcessor response payload race condition 

    Motivation

An issue was reported in #111 where response payloads logged by a configured PayloadProcessor were sometimes incorrectly empty.

Modifications

Do not attempt to avoid slicing the response bytebuf in the case that a PayloadProcessor is configured, do not attempt to avoid some additional refcount updates in status != OK case.

Result

Hopefully no more incorrectly empty logged payloads

Resolves #111

Signed-off-by: Nick Hill <nickhill@us.ibm.com>
    @njhill @ckadner
    njhill authored and ckadner committed Nov 23, 2023
    Configuration menu
    Copy the full SHA
    9ad9bc6 View commit details
    Browse the repository at this point in the history