Repository navigation
Vulture fails to read a trace if the write was not successful #5210
Description
Currently, vulture is stateless. It reads its own writes since application start and does not store which writes were successful, which failed. If a write fails, subsequent reads will also fail for that trace, this brings false-positive reports on read errors. We need to avoid reading failed writes.
One possible improvement would be storing failed traces in memory. Once the number of failed traces reaches a threshold N, the application could force a restart.
Activity
github-actions commentedon Aug 11, 2025
This issue has been automatically marked as stale because it has not had any activity in the past 60 days.
The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed after 15 days if there is no new activity.
Please apply keepalive label to exempt this Issue.