You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a successful subscription, a debug print statement continuously prints the number '1' in the console. This behavior appears to be unintended and results in excessive logging, which can clutter the output and make it difficult to track other important logs.
Steps to Reproduce:
Subscribe to the service or feature.
Observe the console output after the subscription is successful.
#####Expected Behavior:
After a successful subscription, the console should not continuously print the number '1'.
#####Actual Behavior:
The console continuously prints the number '1' after a successful subscription.
Impact:
Clutters the console output.
Makes it harder to identify other important logs.
Potentially affects performance due to excessive logging.
Suggested Solution:
Identify and remove or comment out the debug print statement causing the continuous output.
Please address this issue to maintain clean and efficient logging in the application. Thank you!
The text was updated successfully, but these errors were encountered:
Issue Description
Context:
After a successful subscription, a debug print statement continuously prints the number '1' in the console. This behavior appears to be unintended and results in excessive logging, which can clutter the output and make it difficult to track other important logs.
Steps to Reproduce:
Subscribe to the service or feature.
Observe the console output after the subscription is successful.
#####Expected Behavior:
After a successful subscription, the console should not continuously print the number '1'.
#####Actual Behavior:
The console continuously prints the number '1' after a successful subscription.
Impact:
Clutters the console output.
Makes it harder to identify other important logs.
Potentially affects performance due to excessive logging.
Suggested Solution:
Identify and remove or comment out the debug print statement causing the continuous output.
Please address this issue to maintain clean and efficient logging in the application. Thank you!
The text was updated successfully, but these errors were encountered: