-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add proper logging for retry mechanism #314
Comments
@Rajaneeshkumar please help raise a PR with the suggested changes. |
Hi @ASaiAnudeep , |
@Rajaneeshkumar depending on the retry count, the requested change might spam the console output. |
@leelaprasadv I have tried to set the log level to debug to gain more insight into the process. However, this action resulted in a spamming of debug logs from various sources being printed to the console. I want to apply retry logic to all requests in the project globally, not for specific requests. |
@ASaiAnudeep / @leelaprasadv Could you please provide an update on the status of the above request? |
closed in #315 |
Is your feature request related to a problem? Please describe.
I employed a retry mechanism for my tests, but determining whether the tests were actually retried upon failure was challenging because no related messages were printed in the console/terminal. After going through tosser.js and conducting some debugging, I discovered that retries were indeed occurring.
Describe the solution you'd like
In the setResponse() method located in tosser.js, it would be beneficial to include log statements indicating the number of retry attempts within the specified block.
Additional context
As a user, having detailed logging output to the terminal would greatly facilitate debugging issues. I would appreciate a prompt response from you on this matter.
@ASaiAnudeep
The text was updated successfully, but these errors were encountered: