Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Apr 10 11:40
    dotta commented #764
  • Apr 10 11:40
    dotta commented #764
  • Apr 10 11:39
    dotta commented #764
  • Apr 06 12:39
    typesafe-tools commented #973
  • Apr 06 12:39

    eed3si9n on develop

    fix ScalaInstance constructor Merge pull request #973 from ad… (compare)

  • Apr 06 12:39
    eed3si9n closed #973
  • Apr 06 12:39
    eed3si9n closed #972
  • Apr 06 11:11
    adpi2 review_requested #973
  • Apr 06 11:07
    typesafe-tools commented #973
  • Apr 06 11:07
    adpi2 opened #973
  • Apr 06 11:05
    adpi2 commented #972
  • Apr 05 21:18
    eed3si9n commented #972
  • Apr 05 21:18
    eed3si9n assigned #972
  • Apr 05 20:13
    slandelle edited #972
  • Apr 05 20:13
    slandelle opened #972
  • Apr 05 08:38
    dotta commented #764
  • Apr 04 08:21
    retronym commented #764
  • Apr 04 08:20
    retronym commented #764
  • Apr 04 08:18
    retronym commented #764
  • Apr 04 07:44
    dotta commented #764
eugene yokota
@eed3si9n
I wonder if the alpine image is missing some library that openjdk11 is using
eugene yokota
@eed3si9n
I got the tests to pass on JDK 11 - sbt/zinc#640
Jorge
@jvican
Great, I’ll have a look today then
eugene yokota
@eed3si9n
sbt/zinc#601 has been open for a while
it's a cleanup PR that removes most of warnings, but since it touches a bunch of files it conflicts easily
eugene yokota
@eed3si9n
just published zinc 1.3.0-M3
eugene yokota
@eed3si9n
@jvican do you know what's going on with https://ci.scala-lang.org/sbt/zinc? it can't seem to download artifacts from Maven Central
eugene yokota
@eed3si9n
ftr, CI is now back in operation
Piotr Kołaczkowski
@pkolaczk_twitter
How to publish zinc locally so I can test it with another project?
eugene yokota
@eed3si9n
open sbt, +publishLocal
eugene yokota
@eed3si9n
@/all please check this out. Lightbend Community Code of Conduct - https://discuss.lightbend.com/t/lightbend-community-code-of-conduct-for-all-repos-under-sbt/5099
eugene yokota
@eed3si9n
gave a talk on Zinc at ScalaSphere - https://twitter.com/eed3si9n/status/1181878462165983232
Dave Nicponski
@virusdave
heyas, qq: Is there, or has there ever been a zinc issue using classpath manifest jars?
eugene yokota
@eed3si9n
I'm not aware of it but I won't be surprised if the incremental compilation doesn't account for Class-Path entry in MANIFEST.MF
Dave Nicponski
@virusdave
hmm :/
Initial attempt makes me think it's not even working for clean build. Will investigate more today
Donald Andrew Bronson
@Recon419A
Hey, quick question. I pulled sbt/zinc and the version of zinc in the build.sbt is 1.3.0-SNAPSHOT while the release version is 1.3.3. Is there a reason the build anteversions the release?
eugene yokota
@eed3si9n
no that should be 1.4.0-SNAPSHOT instead
Donald Andrew Bronson
@Recon419A
Okay, just wanted to be sure I wasn't smoking something.
eugene yokota
@eed3si9n
Alex Shubert
@lure
Hi everyone. I tried to upgrade to Gradle 6 from Gradle 5 and build time increased two times.
The apache/kafka#7677 states, this is a tradeof in new zinc
The new version of Gradle uses a new version of Zinc which trades full compilation speed for incremental compilation speed.
However can't find the explanation on that in zinc docs. Is that really the case? Are there any worksrounds. Thank you.
Guillaume Martres
@smarter
no, that's really weird/unexpected
seems like a gradle bug
Guillaume Martres
@smarter
zinc shouldn't be adding more than a few percent to compilation time
a sudden 2x slowdown means something has gone terribly wrong somewhere
Alex Shubert
@lure
It is consistently two times slower. Just replacing 5.6.2 to 6.3/6.2.1 and back provides stable 11m vs 6m. Nothing else is changed.
I mentioned your answer in GitHub issue. May be you could leave some suggestion there, if you got some spare minutes?
I mean, your opinion would be much more helpful :)
Guillaume Martres
@smarter
I know nothing about gradle or how they interact with zinc, so I can't say much
if you're invoking gradle multiple times from the command line, are you sure that it's reusing the same JVM instance ? Maybe something changed in how gradle handles JVMs
a cold JVM can easily be twice as slow at compiling scala than a hot JVM
otherwise, I guess you'll need to get a profiler and start measuring
Alex Shubert
@lure
Both builds use cold jvm. It's cloud CI agents. Anyway, I am going to measure module by module. Who knows, may be it is something else inside my own project. I just was surprised by the phrase about tradeoff.
Guillaume Martres
@smarter
yeah, try to reproduce it locally first
maybe the new gradle uses more memory but your JVM still has the same maximum heap, so you're spending more time doing GC, who knows
eugene yokota
@eed3si9n
the tradeoff likely comes from class-based name hashing introduced in Zinc 1 which does create more stuff to persist. 2x does seem like some pathological case. maybe you need to give more memory?
eugene yokota
@eed3si9n
Guillaume Martres
@smarter
@eed3si9n Wasn't there a https://gitter.im/sbt/sbt-contrib room previously? It doesn't seem to exist anymore.
eugene yokota
@eed3si9n
@smarter Yea, I deleted it since I don't use Gitter much, it was mostly unused, and we created a discussion forum on GitHub - https://github.com/sbt/sbt/discussions
Guillaume Martres
@smarter
oh
Guillaume Martres
@smarter
@eed3si9n in https://eed3si9n.com/sbt-1.5.0-beta you say "Due to the transitive dependencies to Dokka, which is planned to be removed eventually, the following resolver is required to use Scala 3.0.0-RC1 for now:" but I think that dependency has already been removed from 3.0.0-RC1
(also the announcement starts by mentioning 1.5.0-M1 instead of M2)
related question: do you have an ETA for 1.5.0 final?
eugene yokota
@eed3si9n
I don't have any ETA. I'd happy to ship it when Darja says ship it.
Guillaume Martres
@smarter
@eed3si9n Our current plan is to do 3.0.0-RC2 in ~3 weeks and final 4 weeks later if all goes well (also Darja isn't responsible for release management fwiw)
Guillaume Martres
@smarter
@eed3si9n the release notes for 1.5.0-RC2 still mention ThisBuild / resolvers += Resolver.JCenterRepository for 3.0.0-RC1 which isn't necessary.
eugene yokota
@eed3si9n
thanks. I'll remove that.