Skip to content

Conversation

@slyapustin
Copy link

… for 204 response

Description

Simplify success status check and add test for 204 response

Fixes #4338

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A

Does This PR Require a Contrib Repo Change?

  • Yes. - Link to PR:
  • No.

Checklist:

  • Followed the style guidelines of this project
  • Changelogs have been updated
  • Unit tests have been added
  • Documentation has been updated

@slyapustin slyapustin requested a review from a team as a code owner December 5, 2024 15:46
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Dec 5, 2024

CLA Signed


The committers listed above are authorized under a signed CLA.

@codefromthecrypt
Copy link
Contributor

made this comment on the originating issue as the zipkin api is stable, and doing something like this would end up a similar ask on all language repos maybe. It could be easier to identify which server is using the wrong status code and ask them to switch to 202 #4338 (comment)

@emdneto
Copy link
Member

emdneto commented Jan 15, 2025

based on the above comment and previous investigation, closing this then ✌🏻

@emdneto emdneto closed this Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Response success status validated incorrectly

3 participants