Fix the SenderSendInterceptor in the nutz-plugin/http-1.x-plugin to avoid NPE caused by the Response status

[96loveslife]

• If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
• Update the CHANGES log.

[Copilot]

Pull request overview

Fixes a null-handling bug in the Nutz HTTP 1.x plugin’s SenderSendInterceptor that could trigger an NPE when the intercepted send() call returns null, and documents the fix in the changelog.

Changes:

• Correct the response null-check in SenderSendInterceptor#afterMethod to avoid dereferencing a null Response.
• Add a release note entry in CHANGES.md for the bug fix.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
CHANGES.md	Adds a release note for the Nutz HTTP 1.x interceptor NPE fix.
apm-sniffer/apm-sdk-plugin/nutz-plugins/http-1.x-plugin/src/main/java/org/apache/skywalking/apm/plugin/nutz/http/sync/SenderSendInterceptor.java	Fixes the null-check so status tagging/error marking only runs when Response is non-null.

Comments suppressed due to low confidence (1)

apm-sniffer/apm-sdk-plugin/nutz-plugins/http-1.x-plugin/src/main/java/org/apache/skywalking/apm/plugin/nutz/http/sync/SenderSendInterceptor.java:72

• This change fixes a null-handling bug, but the existing unit test (SenderInterceptorTest) only exercises the non-null response path. Add a regression test that calls afterMethod(..., ret=null) and asserts it does not throw, and (optionally) another case for status >= 400 to verify the span is marked as error.

        if (response != null) {
            Tags.HTTP_RESPONSE_STATUS_CODE.set(span, response.getStatus());
            if (response.getStatus() >= 400) {
                span.errorOccurred();
            }

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.