[Bug]: trace not check valid in querynode using it. #26789
Labels
kind/bug
Issues or changes related a bug
stale
indicates no udpates for 30 days
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Is there an existing issue for this?
Environment
Current Behavior
when user not set trace exporter, querynode using this tracer and not check trace id valid or not. causing querynode coredump
core code:
not check valid and convert null value to uint8_t*.
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: