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

[backport] sbt bridge reporting improvements #12845

Merged
merged 3 commits into from
Jun 16, 2021

Conversation

smarter
Copy link
Member

@smarter smarter commented Jun 16, 2021

This backports #12735 and #12838 to 3.0.1, these PRs do not fix a regression from 3.0.0 but I still think it's worth backporting them since they're low-risk and #12838 especially should make metals much nicer to use.

This also backports #12720 to avoid a flaky test failure.

Markus Sutter and others added 2 commits June 16, 2021 12:30
There are compile call paths relying on
meaningful toString impl. for error/warning
log messages. Therefor lets add toString, which is:
"concise but informative representation that is easy for a person to read."

Without this, e.g. users of https://github.com/davidB/scala-maven-plugin
get unsuitable compile problems like:
[Warn] dotty.tools.xsbt.PositionBridge@4fbdc20: match may not be exhaustive....

Example call path:
log:45, SbtLogger (sbt_inc)
log:47, Logger (sbt.util)
warn:43, Logger (sbt.util)
logWarning:159, LoggedReporter (sbt.internal.inc)
display:168, LoggedReporter (sbt.internal.inc)
log:142, LoggedReporter (sbt.internal.inc)
doReport:43, DelegatingReporter (dotty.tools.xsbt)
report:150, Reporter (dotty.tools.dotc.reporting)
issueWarning:32, report$ (dotty.tools.dotc)
warning:67, report$ (dotty.tools.dotc)
checkExhaustivity:847, SpaceEngine (dotty.tools.dotc.transform.patmat)
....
@smarter smarter added this to the 3.0.1 milestone Jun 16, 2021
@smarter smarter requested a review from adpi2 June 16, 2021 10:32
Copy link
Member

@adpi2 adpi2 left a comment

Choose a reason for hiding this comment

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

There is a failed scaladoc test but I don't think it can be caused by the current changes. So it is probably a flaky test.

Error:  Test dotty.tools.scaladoc.sourcelinks.RemoteLinksTest.runTest failed: Expected to find Predef at https://github.com/scala/scala/blob/v2.13.6/src/library/scala/Predef.scala at line 96, took 3.056 sec

@smarter
Copy link
Member Author

smarter commented Jun 16, 2021

@romanowski is the sourcelinks.RemoteLinksTest failure an issue that is fixed in master and should be backported to the release-3.0.1 branch?

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

4 participants