Skip to content
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

bugfix: Remove potentially problematic println #1850

Merged
merged 1 commit into from
Nov 14, 2022

Conversation

tgodzik
Copy link
Contributor

@tgodzik tgodzik commented Nov 14, 2022

It seems that #1847 is hanging on trying to lock the out object and since the println here is not really useful I think it's fine to remove and check if that helps.

The stack trace mostly shows a lot of thread stuck on that println actually.

It seems that scalacenter#1847 is hanging on trying to lock the out object and since the println here is not really useful I think it's fine to remove and check if that helps.
@tgodzik tgodzik requested review from dos65 and kpodsiad November 14, 2022 20:21
Copy link
Collaborator

@kpodsiad kpodsiad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively, cleanUpNonStableCliDirectories can accept logger and log that message at info/debug level. I have no idea how useful it'll though.

@tgodzik
Copy link
Contributor Author

tgodzik commented Nov 14, 2022

Alternatively, cleanUpNonStableCliDirectories can accept logger and log that message at info/debug level. I have no idea how useful it'll though.

I was thinking about it, but I don't think I have ever seen this being useful.

@tgodzik tgodzik merged commit f7292aa into scalacenter:main Nov 14, 2022
@tgodzik tgodzik deleted the remove-println branch November 14, 2022 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants