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

Error appears randomly over REPL Sessions #16897

Closed
cruiztorresj opened this issue Feb 12, 2023 · 1 comment
Closed

Error appears randomly over REPL Sessions #16897

cruiztorresj opened this issue Feb 12, 2023 · 1 comment
Labels
itype:bug stat:needs triage Every issue needs to have an "area" and "itype" label

Comments

@cruiztorresj
Copy link

Scala code runner version 3.2.1 -- Copyright 2002-2022, LAMP/EPFL

The following error appears randomly[1], so I am not sure you actually will be able to reproduce it.

Minimized code

scala> val arreglo: Array[Int] = Array(1, 2, 3, 4, 3, 2, 1)
scala> arreglo.sortWith(_ < _)
scala> val (sorted1: Array[Int], sorted2: Array[Int]) = arreglo.sortWith(_ < _).splitAt(arreglo.length / 2)

Output

Bad symbolic reference. A signature
refers to JFunction2$mcZII$sp/T in package scala.runtime.java8 which is not available.
It may be completely missing from the current classpath, or the version on
the classpath might be incompatible with the version used when compiling the signature.
1 error found

Expectation

No error should be happening.

Underlying System Info.

The Scala REPL is running on top of Java 17 over a Windows Subsystem for Linux 2 (WSL2) installation.

Welcome to Scala 3.2.1 (17.0.5, Java Java HotSpot(TM) 64-Bit Server VM).
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu

[1]
RandomErrorInREPL

Thanks.

--
Caleb

@cruiztorresj cruiztorresj added itype:bug stat:needs triage Every issue needs to have an "area" and "itype" label labels Feb 12, 2023
@smarter
Copy link
Member

smarter commented Feb 12, 2023

Duplicate of #15562, would you mind posting the content of your issue as a comment there? It could help track down the root cause.

@smarter smarter closed this as not planned Won't fix, can't repro, duplicate, stale Feb 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
itype:bug stat:needs triage Every issue needs to have an "area" and "itype" label
Projects
None yet
Development

No branches or pull requests

2 participants