Segment not propgated when subsegment metadata is sufficiently long
- Dominant language
- Python
- Stars
- 338
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
The xray-daemon does not propagate a segment to AWS, where metadata is set using `query`, where `query` is both defined and used below:
```python
query="******************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************"
xray_recorder.begin_segment("segment")
c=xray_recorder.begin_subsegment("foo")
c.put_metadata("bar", query)
xray_recorder.end_subsegment()
xray_recorder.end_segment()
```
`query` is, above, a 882-character long string.
By contrast, if I set `query` to something trivial like `"bla"` then the `xray-daemon` forwards the segment. If I set `query` to a shorter 30-character string like `"******************************"`, then the daemon forwards the segment.
There should be no problem with `query` being very long.
Contributor guide
Assessment
This issue has not been assessed yet.