Closed mpldr closed 2 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Bump
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug
We have a partially working API. Currently 13/71 endpoints are working as intended (we have verified this manually). However, goss does not always report this correctly. Sometimes it just randomly has some
Client.Timeout exceeded while awaiting headers
while the server is chilling at 2% load. Most times it reports 13/71 as it should be but sometimes it's also any other number. The highest we've seen so far was 53. The server seems not to receive the requests (at least it does not log them)How To Reproduce
Expected Behavior
Actual Behavior
Environment:
Since this is a company project I am unfortunately not allowed to share binary or sourcecode. I can however provide the goss file if that helps.