-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Event Hubs] Use logger instead of debug package in test files #9209
Comments
I'll take a look and see if we even want to keep these. |
Did a little spot check of these - considering that occasionally errors lead to the tests hanging these seem like useful things to be able to selectively activate. So porting them to maybe use a single "test" logger should be enough and not horribly difficult. And for the most part all of these should probably just go to the .verbose() stream since it's in the live tests only. |
Hi @ramya-rao-a, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support. |
The
debug
package was used for logging in older versions of the Event Hubs library. In the latest version, we moved to using the common@azure/logger
package. Looks like we missed to do the same in the test files which continue to use thedebug
package.This issue is to track the work needed to update the test files to use
@azure/logger
instead ofdebug
for logging.The text was updated successfully, but these errors were encountered: