Skip to content
This repository has been archived by the owner on Oct 3, 2023. It is now read-only.

Add B3 multiple headers propagation #224

Closed
wants to merge 3 commits into from

Conversation

duxet
Copy link

@duxet duxet commented Feb 6, 2019

Solves #216.

I had to do some refactoring, as current setup was prepared only for single header propagation.

@duxet duxet changed the title Add B3 multiple headers propagation #17 Add B3 multiple headers propagation #216 Feb 6, 2019
@duxet duxet changed the title Add B3 multiple headers propagation #216 Add B3 multiple headers propagation Feb 6, 2019
$value = $this->formatter->serialize($context);
if (!headers_sent()) {
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i am not sure if i should keep it, it shouldn't cause any side effects IMHO

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems like a backwards incompatible change if you remove this code. If someone was relying on having the headers written with this library, we'd remove that functionality. However, since the package is in 0.x version, I suppose this is allowed.

$enabled = null;

if ($sampled !== null) {
$enabled = $sampled === '1';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is possible some propagators pass true aswell according to https://github.com/openzipkin/b3-propagation#sampling-state-1

Copy link

@nenad nenad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than this comment, it looks good.

$value = $this->formatter->serialize($context);
if (!headers_sent()) {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems like a backwards incompatible change if you remove this code. If someone was relying on having the headers written with this library, we'd remove that functionality. However, since the package is in 0.x version, I suppose this is allowed.

@nenad
Copy link

nenad commented Mar 4, 2019

@chingor13 @basvanbeek Could you please review this PR?

@sergiught
Copy link

+1 looks 🆗 let's get this merged?

@vgarvardt
Copy link

Seems good.
Can this be merged?

@nhatthm
Copy link

nhatthm commented Nov 7, 2019

@chingor13 @basvanbeek Could you please review this PR?

@duxet duxet closed this Jun 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants