by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 13:32
    ctataryn commented #1334
  • 11:14
    lloydmeta commented #61
  • Jul 06 16:01
    olafurpg commented #1334
  • Jul 04 18:51
    ctataryn opened #1334
  • Jul 03 15:08
    mnd999 commented #1322
  • Jul 03 01:01
    lloydmeta opened #1333
  • Jul 02 14:49
    pityka commented #1332
  • Jul 02 00:05
    jeffrey-aguilera opened #1332
  • Jun 30 22:22

    bloopoid on gh-pages

    Deploy website Deploy website … (compare)

  • Jun 30 21:59

    jvican on master

    Revert `sonatypeBundleRelease` … (compare)

  • Jun 30 20:54

    jvican on master

    Disable sonatypeBundleRelease t… (compare)

  • Jun 30 20:49

    jvican on v1.4.3

    (compare)

  • Jun 30 20:18

    bloopoid on gh-pages

    Deploy website Deploy website … (compare)

  • Jun 30 19:56
    jvican commented #1322
  • Jun 30 19:53

    jvican on v1.4.3

    (compare)

  • Jun 30 19:53

    jvican on master

    Refine README for 1.4.3 (compare)

  • Jun 30 14:40
    jvican closed #1330
  • Jun 30 14:36

    jvican on master

    Add support for Scala 2.13.3 Add release notes for 1.4.3 Finish 1.3.3 release notes [DOC… and 1 more (compare)

  • Jun 30 14:36
    jvican closed #1331
  • Jun 30 10:14
    jvican commented #1330
Krzysiek Bochenek
@kpbochenek
in Macros.scala you have @main as top level. It works as it it.
Now move @main to object Logger, it will throw mentioned error
now bonus points!
move method back to top level(where it compiled previously) and it won't compile Oo
(sbt always compiles ok, bloop structure is generated via opening a project in VSCode and testing with bloop compile dotty-complex)
Jorge
@jvican
will have a closer look at this, thanks
Issue might be related to scalacenter/bloop#1289
Tomasz Godzik
@tgodzik
@jvican that issues doesn't happen with sbt and sbt generated Bloop config, only with Mill. I think it's more important to stop publishing that jar (scala-libary:0.23), it just hides some possible issues
raised an issue in Dotty: lampepfl/dotty#9024
if we can fix it easily in Bloop it would probably it would also be useful, but I think it is most likely not only Bloop that will have this issue
Krzysiek Bochenek
@kpbochenek
@jvican it is not related, as @tgodzik mentioned it is not the case with sbt, also I checked and I have no scala-library:0.X in bloop config
Matt Hicks
@darkfrog26
@jvican it may have to do with the fact that I'm using Scala 2.13?
Alan Devlin
@spf3000
How does bloop decide which jdk to run? My bloop is pointing to an old graalvm that I've removed, and seems to not be fixed just by updating $JAVA_HOME
Alan Devlin
@spf3000
^^ It was just specific to a particular project. I removed .bloop/ and re-Installed. Ignore me! :)
Max
@maxstreese
image.png
Hi everyone I am wondering if anyone else is running into this issue but when I do bloop console <some-project I get the above strange error when bloop or coursier tries to download some things (scala compiler and reflect !?). Has anyone else tried to run bloop console with the latest release (1.4.1)?
Jorge
@jvican
@darkfrog26 I don't know but it's strange indeed, would help if you could file a ticket
@maxstreese Hmmm, can you make sure you have the latest version of coursier installed?
8 replies
Jakub Kozłowski
@kubukoz
Can someone give me a hand with the zsh completions? I tried to get them to work as an oh-my-zsh plugin, but so far with no effect...
Jorge
@jvican
How are you installing bloop?
slice
@slice
is anyone else experiencing this strange error on java 14?
error: Unexpected error forces client exit!
java.lang.NumberFormatException: For input string: "0
"
        at java.lang.Integer.parseInt(Integer.java:652)
        at java.lang.Integer.parseInt(Integer.java:770)
        at snailgun.protocol.Protocol.$anonfun$processChunkFromServer$1(Protocol.scala:193)
        at scala.util.Try$.apply(Try.scala:213)
        at snailgun.protocol.Protocol.processChunkFromServer(Protocol.scala:180)
        at snailgun.protocol.Protocol.sendCommand(Protocol.scala:108)
        at snailgun.TcpClient.run(TcpClient.scala:34)
        at bloop.bloopgun.BloopgunCli.executeCmd$1(Bloopgun.scala:268)
        at bloop.bloopgun.BloopgunCli.fireCommand(Bloopgun.scala:274)
        at bloop.bloopgun.BloopgunCli.run(Bloopgun.scala:230)
        at bloop.bloopgun.Bloopgun$.main(Bloopgun.scala:638)
        at bloop.bloopgun.Bloopgun.main(Bloopgun.scala)
Jorge
@jvican
@slice Wow, that's really unexpected
It's weird the Nailgun server is returning that status code. How are you using bloop?
Tomasz Godzik
@tgodzik
Has anyone used Bloop run something with DCEVM with hotswapping option? Seems problematic when running main, but haven't tried it yet.
Matt Hughes
@matthughes
What does Bloop do differently for SJS projects besides just compile? Like I see it generating sjsir files, but to what end? Who uses those? Is there a way to disable that stuff when using Bloop/Metals? I just want compilation for symbol lookup, etc. I don’t want every incremental change to build SJS artifacts that I’m not gonna use.
slice
@slice
@jvican pretty standardly—i installed everything (bloop, adoptopenjdk, coursier) with homebrew
Jorge
@jvican
@slice first time i see that error, you say you can reproduce it consistently?
@matthughes sjs files are just like class files, they are produced by the scalajs compiler plugin
slice
@slice
@jvican it gets thrown on every bloop command i run, yes
Jakub Kozłowski
@kubukoz

How are you installing bloop?

@jvican nix-env -i bloop

user753
@user753
How to fix Couldn't retrieve module ch.epfl.scala:compiler-bridge_2.13:1.3.0-M4+42-5daa8ed7:compile error ?
slice
@slice
@maxstreese @jvican this may be of interest, i was encountering some problems like this several days ago: https://github.com/scalacenter/bloop/issues/1226#issuecomment-625749487
17 replies
the problem boils down to bloop's built-in coursier being outdated, i believe
i think that bloop never uses the system coursier
Jorge
@jvican
@kubukoz that's something you should tell the person maintaining the nix package then, it's not an official way of installing bloop
pear-programmer
@pear-programmer
Hi! I'm having trouble using scala metals and I think the problem might be with bloop. Maybe my gradle project isn't set up properly for it. I have a gradle project with multiple subprojects. After bloop is run, i have a json file for one subproject that references another subproject in its classpath: "/Users/work/src/PROJECT_ROOT/.bloop/common/build/classes" Unfortunately, that directory doesn't exist. I'm assuming it should so that coc-metals can get completion info. Any ideas?
Only bloop output i've noticed is
2020.05.28 11:50:38 INFO compiling common (239 java sources) 2020.05.28 11:50:38 INFO time: compiled common in 78ms
which seems a little fast
Krzysiek Bochenek
@kpbochenek
When I run my application and I read from StdIn it seems to hang forever not getting input. I execute bloop run <project> and in my main I have val action = StdIn.readLine(). I type things and press 'Enter' but it is not received by my app. It works okay with sbt run but as I already have everything compiled and ready to run it would be awesome to be able to get this working
Is it possible to provide some flag or workaround it in any way?
Arthur McGibbon
@Arthurm1
@pear-programmer Although the project file refers to ...../.bloop/PROJECT_NAME/build/classes, in reality the class file location is slightly different - depending on the client you use (e.g. CLI, Metals). You should see class files under ...../bloop/PROJECT_NAME/build/bloop-XXXX-classes or similar.
From the log message it looks like Bloop has successfully compiled your project. The reason it's so quick is that Bloop will only recompile if it thinks something has changed - fast incremental compilation is its forte. You can try bloop clean then bloop compile PROJECT_NAME to see it compile from scratch.
I see it says (239 java sources) so I'm assuming this is a Java project? While Bloop will compile and run java projects, Metals does not support Java files scalameta/metals-feature-requests#5 - you won't get any code completion on them. Vote on the issue if you need that.
Glen Marchesani
@fizzy33
I wanted to say great work @jvican and the rest of the team. I just took all my businesses scala projects and got them going with bloop, took 30 minutes and many improvements all around. A total of 500K lines of code 5 repos and over 200 sbt modules/projects.
it "just worked (tm)"
and using the BSP support solved a TON of intellij glitches we are having.
responsiveness for our standard workflow is significantly improved and opened up new simpler possibilities thanks again
Rafał Krzewski
@rkrzewski
@kpbochenek I've also run into it recently but haven't got around to reporting it. I've checked the issue tracker now: scalacenter/bloop#882
Hmm the issue mentions underlying problem with nailgun: facebook/nailgun#115 but Bloop uses https://github.com/jvican/snailgun now. Yet the issue persists...
Jorge
@jvican
@fizzy33 really happy to hear that, that's fantastic
@kpbochenek @rkrzewski yes, we need to figure out what to do so that stdin is working again, it's quite hard to make it work from the stdin
i would appreciate if someone could have a look at it