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
What would you recommend for continued debugging of this issue? Since spark-rapids is using mvn and not sbt, it isn't clear to me how the unmanaged/managed concept from the SBT docs applies here.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When running test suites from spark-rapids, Metals is unable to resolve my source files with the following error:
If I evaluate local variables in the stack frame, it works fine. But if I try to access e.g. a test suite class definition, I see the following error:
Per the Scala documentation, "Unmanaged files are manually created files that are outside of the control of the build." I am surprised to see
/home/ec2-user/my-spark-rapids/spark-rapids/tests/target/spark311/test-classes
listed as unmanaged, because it is definitely an artifact created when the module is built.What would you recommend for continued debugging of this issue? Since
spark-rapids
is usingmvn
and notsbt
, it isn't clear to me how the unmanaged/managed concept from the SBT docs applies here.Beta Was this translation helpful? Give feedback.
All reactions