As a rule of thumb - everything that fathomably interfaces with the compiler has to be compiled against exact version of it.
Scala compiler API has no guarantees even between patch versions, so things like ammonite (and parts of Almond) need to be cross-published against full scala version :) Just like many compiler plugins.
Hello, has anyone run into an issue like this?
[IJ]test:runMain amm
[warn] sbt 0.13 shell syntax is deprecated; use slash syntax instead: Test / runMain
[info] running amm
[error] (run-main-0) java.lang.ExceptionInInitializerError
[error] java.lang.ExceptionInInitializerError
[error] at amm.main(amm.scala)
[error] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[error] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
[error] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[error] at java.base/java.lang.reflect.Method.invoke(Method.java:564)
[error] Caused by: java.lang.NullPointerException: Cannot invoke "scala.collection.mutable.ArraySeq$ofRef.toList()" because the return value of "scala.Predef$.wrapRefArray(Object[])" is null
[error] at ammonite.Main$.main(Main.scala:279)
[error] at amm$.<clinit>(amm.scala:1)
[error] at amm.main(amm.scala)
[error] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[error] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
[error] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[error] at java.base/java.lang.reflect.Method.invoke(Method.java:564)
[error] stack trace is suppressed; run 'last Test / bgRunMain' for the full output
[error] Nonzero exit code: 1
[error] (Test / runMain) Nonzero exit code: 1
[error] Total time: 2 s, completed May 22, 2021, 7:02:27 PM
From the source code of the failing method it looks like it's failing on the primary entry point for Ammonite...
If it helps, my build.sbt is here: https://pastebin.com/Hbz1ya0Q
It's due to the main method changes in Scala 3
In the latest version of Ammonite I get the following simply when trying to do an import
❯ amm
Loading...
Welcome to the Ammonite Repl 2.3.8-124-2da846d2 (Scala 2.13.6 Java 11.0.11)
@ import scala.util.Try
error while loading NotGiven, Missing dependency 'Add -Ytasty-reader to scalac options to parse the TASTy in /Users/ckipp/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala3-library_3/3.0.0/scala3-library_3-3.0.0.jar(scala/util/NotGiven.class)', required by /Users/ckipp/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala3-library_3/3.0.0/scala3-library_3-3.0.0.jar(scala/util/NotGiven.class)
error while loading FromDigits, Missing dependency 'Add -Ytasty-reader to scalac options to parse the TASTy in /Users/ckipp/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala3-library_3/3.0.0/scala3-library_3-3.0.0.jar(scala/util/FromDigits.class)', required by /Users/ckipp/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala3-library_3/3.0.0/scala3-library_3-3.0.0.jar(scala/util/FromDigits.class)
error while loading CommandLineParser, Missing dependency 'Add -Ytasty-reader to scalac options to parse the TASTy in /Users/ckipp/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala3-library_3/3.0.0/scala3-library_3-3.0.0.jar(scala/util/CommandLineParser.class)', required by /Users/ckipp/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala3-library_3/3.0.0/scala3-library_3-3.0.0.jar(scala/util/CommandLineParser.class)
error while loading LowPriorityNotGiven, Missing dependency 'Add -Ytasty-reader to scalac options to parse the TASTy in /Users/ckipp/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala3-library_3/3.0.0/scala3-library_3-3.0.0.jar(scala/util/LowPriorityNotGiven.class)', required by /Users/ckipp/Library/Caches/Coursier/v1/https/repo1.maven.org/maven2/org/scala-lang/scala3-library_3/3.0.0/scala3-library_3-3.0.0.jar(scala/util/LowPriorityNotGiven.class)
Compilation Failed
why it it looking in Scala3 jars?
nevermind, I see it's reported already com-lihaoyi/Ammonite#1182
@keynmol: just a step ahead of me
I had to pin the ammonite version to one released for 2.13.4 to unbreak my things :-)
any ideas?
btw, one cannot build mill if it's not under git, e.g. if it is extracted from the tar.gz, due to https://github.com/lefou/mill-vcs-version/blob/main/core/src/de/tobiasroeser/mill/vcs/version/VcsVersion.scala#L26
would be nice if that got fixed
I think building is still possible, but for (local) publishing, you need to override one target.
I've a java.nio.file.Path instance that I'd like to pass to
os.write(), somehow I expected the conversation to be implicit, but the compiler complains about a type mismatch
I somehow assume that I just miss some import or other magic
no scala implicit magic invovled
basically yeah, because we are downcasting from "who knows what this YOLO" to "definitely a normalized canonicalized absolute path", so you need either pass in an explicit base directory to absolute-ize relative paths, or accept that relative paths will blow up with an exception. Neither of those would be great to do implicitly
1 reply
Trying to get Visual Studio code to work with Ammonite. I've got VS Code v 1.56.2 on Windows 10 and am trying to get a simple Scala worksheet working. I created a new Scala3 sbt project using "sbt new scala3/scala-cross.g8" to get started. build.sbt shows that it has set the default scalaVersion := 3.0.0. VS Code is giving me a "Error fetching Ammonite 2.3.8-58-aa8b2ab1 for Scala 2.13.6" (Source: Scala Metals). Any hints how to fix?
so in Metals you're a bit limited by the default versions that we have and a mismatch between those and the latest versions available in Ammonite. Typically we add support for a new Scala version pretty quickly before Ammonite has a chance to
in an ammonite script in Metals you can actually specify the exact version of Ammonite and Scala version with comments at the top of the file
since metals uses ammonite-runner under the hood https://github.com/alexarchambault/ammonite-runner
switching my project to scala 3 results in
[error] -- [E007] Type Mismatch Error:
[error] 22 | os.symlink(symlink, dir)
[error] | ^^^^^^^^^^^^^^^^^^^^^^
[error] |Found: (Context.this.dir : os.Path#ThisType#ThisType)
[error] |Required: os.FilePath
[error] |I guess that's an issue with different handling of implicits in Scala 3. Anything I could do?
Hi there, how add resolvers to a script?
import coursierapi.MavenRepository
interp.repositories() ++= Seq(
MavenRepository.of("https://packages.atlassian.com/maven-public/")
)
import $ivy.`com.atlassian.browsers:atlassian-browsers-auto:3.1.0`
@main
def main(): Unit = println("Hello")Failed to resolve ivy dependencies:Error downloading com.atlassian.browsers:atlassian-browsers-auto:3.1.0
not found: /root/.ivy2/local/com.atlassian.browsers/atlassian-browsers-auto/3.1.0/ivys/ivy.xml
not found: https://repo1.maven.org/maven2/com/atlassian/browsers/atlassian-browsers-auto/3.1.0/atlassian-browsers-auto-3.1.0.pom
Is there a way to reduce the noise from the compiler errors a bit eg: the path
ammonite.$file.src.main.scala.response.Response_10. repeated everywhere in error, making it really difficult to read.type mismatch;
found : ammonite.$file.src.main.scala.response.Response_10.UHttp[ammonite.$file.src.main.scala.response.Response_10.ChannelEvent[ammonite.$file.src.main.scala.response.Response_10.Request],ammonite.$file.src.main.scala.response.Response_10.ChannelOperation[ammonite.$file.src.main.scala.response.Response_10.Response]]
(which expands to) ammonite.$file.src.main.scala.response.Response_10.ChannelEvent[ammonite.$file.src.main.scala.response.Response_10.Request] => zio.ZIO[Any,Option[Nothing],ammonite.$file.src.main.scala.response.Response_10.ChannelOperation[ammonite.$file.src.main.scala.response.Response_10.Response]]
required: ammonite.$file.src.main.scala.response.Response_10.Http[?,?,ammonite.$file.src.main.scala.response.Response_10.ChannelEvent[Any],ammonite.$file.src.main.scala.response.Response_10.ChannelOperation[Nothing]]
(which expands to) ammonite.$file.src.main.scala.response.Response_10.ChannelEvent[Any] => zio.ZIO[?,Option[?],ammonite.$file.src.main.scala.response.Response_10.ChannelOperation[Nothing]]
The useful parts are only —
type mismatch;
found : UHttp[ChannelEvent[Request],ChannelOperation[Response]]
(which expands to) ChannelEvent[Request] => zio.ZIO[Any,Option[Nothing],ChannelOperation[Response]]
required: Http[?,?,ChannelEvent[Any],ChannelOperation[Nothing]]
(which expands to) ChannelEvent[Any] => zio.ZIO[?,Option[?],ChannelOperation[Nothing]]
Hi there, how can I integrate mainargs with ammonite? I don't get any results... 😕
import $ivy.`com.lihaoyi::mainargs:0.2.1`
import mainargs.{main, arg, ParserForMethods, Flag}
@main
def run(@arg(short = 'f', doc = "String to print repeatedly")
foo: String,
@arg(name = "my-num", doc = "How many times to print string")
myNum: Int = 2,
@arg(doc = "Example flag, can be passed without any value to become true")
bool: Flag) = {
println(foo * myNum + " " + bool.value)
}
def main(args: Array[String]): Unit = ParserForMethods(this).runOrExit(args)
$ amm args-test.sc
Compiling /root/args-test.sc