-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
enhance(main/rust): Suppress hard linking failed warning. #24947
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
Conversation
TomJo2000
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to check.
This only turns off the warning being emitted by the compiler?
It does not mean the compiler will actually try to do hardlinks on Android.
|
This only turns off the message. |
|
Just wanted to make sure. |
|
I think that it's alright now. Sorry it's actually my first day working with diffs. |
No worries about that, that's what we have contribution resources and PR reviews for. |
|
|
Thank you. It seems like being dump helps somehow haha |
|
I'd say it made me aware of a gap in the linter coverage that should be addressed. |
|
Oops (again) because of this change unused errors are triggered will fix that. |
cdd09ab to
be2b632
Compare
|
Well the third time is the charm. i am pretty sure that it's fixed now.. |
Famous last words. LOL |
|
The CI succeeded 🎉 |
licy183
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks for your contribution!
Well Android does not support hard linking. but rust does not know that and keeps filling the terminal with this useless warning.
This pr patches only one line from the upstream to suppress it.
Please refer to #4921.
See this image
Note: this issue was reported to the upstream for almost 5 years. But unfortunately it seems that no one really cares about it. rust-lang/rust#75997
@TomJo2000 I followed the commit message guidelines this time ;)