| 27 May 2024 |
 hugo_vr | Not sure if this is a Scala or sbt issue. But I tried the new usePipelining on Scala 3.5.0-RC1 and I'm getting lots of import not found errors. Any idea on how I can investigate this? | 10:31:34 |
| hugo_vr | Hmm, I also get it with 3.4.1 (plus some warnings about pickling options that don't exist and a CancellationException at the end | 10:36:55 |
| hugo_vr | * Not sure if this is a Scala or sbt issue. But I tried the new usePipelining on Scala 3.5.0-RC1 and I'm getting lots of import not found errors. Any idea on how I can investigate this? It's a Scala.js project | 10:39:12 |
|  floren_007 joined the room. | 11:40:10 |
| 28 May 2024 |
|  fernandobasso joined the room. | 10:07:40 |
|  weebs_ joined the room. | 16:52:01 |
 matthiasberndt | Does anybody else have trouble using sbt --client in GitHub actions? It doesn't print some error messages (e. g. when publish fails). And it does when I remove --client | 17:17:29 |
 balmungsan3 | armanbilge I believe you once talked to me about this or something similar? | 17:18:09 |
 armanbilge | that's why the client invocation is not printing them out | 17:19:15 |
| armanbilge | and I feel like I remember some issues with printing. | 17:19:17 |
| armanbilge | probably the error messages are going to the sbt server | 17:19:19 |
| armanbilge | tl;dr don't use --client in CI | 17:19:27 |
| matthiasberndt | Well to be fair that is the point that it won't start a process | 18:18:15 |
| matthiasberndt | But the failure to print some error messages is a deal breaker | 18:18:51 |
|  ardal changed their profile picture. | 19:00:17 |
 sideeffffect | Hello in here, I'm struggling with sbt and crosscompilation. I'd like to ask for help, because my sbt skills are failing me. Here's the situation:
There is a module circe-yaml-common
* it should be crosscompiled for both 2.12 and 2.13
There's another module circe-yaml-scalayaml
* it depends on circe-yaml-common
* it depends on another library which isn't for 2.12, only for 2.13
* it thus should be crosscompiled only for 2.13
Both circe-yaml-common and circe-yaml-scalayaml are aggregated in root module.
When CI runs
sbt 'project rootJS' '++ 2.12' 'scalafixAll --check'
It fails with totally nonsensical error
[info] Resolved circe-yaml-scalayaml_sjs1_2.13 dependencies
[warn]
[warn] Note: Unresolved dependencies path:
[info] compiling 2 Scala sources to /home/ondra/Projects/circe-yaml/circe-yaml-common/js/target/scala-2.12/classes ...
[error] sbt.librarymanagement.ResolveException: Error downloading io.circe:circe-yaml-common_sjs1_2.13:0.15.1-32-4dde710-SNAPSHOT
[error] Not found
[error] Not found
[error] not found: /home/ondra/.ivy2/local/io.circe/circe-yaml-common_sjs1_2.13/0.15.1-32-4dde710-SNAPSHOT/ivys/ivy.xml
[error] not found: https://repo1.maven.org/maven2/io/circe/circe-yaml-common_sjs1_2.13/0.15.1-32-4dde710-SNAPSHOT/circe-yaml-common_sjs1_2.13-0.15.1-32-4dde710-SNAPSHOT.pom
What do I need to do so that sbt doesn't take circe-yaml-scalayaml into account when trying to work with 2.12 modules? Could somebody please help me with this? 🙏
https://github.com/circe/circe-yaml/pull/431 | 21:24:48 |
| armanbilge | What do I need to do so that sbt doesn't take circe-yaml-scalayaml into account when trying to work with 2.12 modules? Could somebody please help me with this? 🙏
it's not easily possible. to put it plainly, sbt is broken in this regard | 21:49:36 |
| sideeffffect | 🙀 | 21:50:02 |
| armanbilge | https://discord.com/channels/632150470000902164/922600050989875282/1234914642783113276 | 21:50:35 |
| armanbilge | https://discord.com/channels/632150470000902164/922600050989875282/1053405092373606420 | 21:51:00 |
| armanbilge | you can use sbt-projectmatrix or you can hack the build in various ways | 21:51:36 |
| armanbilge | separately, personally I'm not sure if I agree with the goals of that PR | 21:52:08 |
| sideeffffect | I can always remove 2.12 from the project altogether. But that'd be a bit unfortunate, the other parts of the project still work well with 2.12... | 21:52:09 |
| armanbilge | why not just work on circe-scala-yaml | 21:52:14 |
| sideeffffect | circe-scala-yaml uses totally different backend, a Java library | 21:52:55 |
| armanbilge | I'm not sure I understand | 21:53:05 |
| armanbilge | https://github.com/armanbilge/circe-scala-yaml | 21:53:11 |
| armanbilge | it uses a Scala YAML by VirtustLab which is 100% Scala | 21:53:23 |
| armanbilge | (we're off-topic for here, let's continue in #circe on #typelevel) | 21:53:41 |
| armanbilge | * it uses Scala YAML by VirtustLab which is 100% Scala | 21:53:47 |
