by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Ólafur Páll Geirsson
    @olafurpg
    Testing an entire suite works as expected. It would be nice to be able to run individual tests. The syntax to declare tests is the same as for ScalaTest FunSuite
    the MUnit JUnit runner implements the Filterable interface to select a single test case
    Gábor Bakos
    @aborg0
    Is it a known issue that with sbt shell a CPU core remain active running Console Window Host (even if that sbt shell does nothing, just waits for input)? I tried searching youtrack, but nothing obvious popped up. (2019.3.4, Scala 2.13.1, IDEA Scala 2019.3.26 (Community), JDK 11, no auto-import, not using sbt for building, repro: https://github.com/aborg0/play-quill-jdbc/tree/feature/play_2.8, Windows 10 1909)
    Gábor Bakos
    @aborg0
    Thanks, added my vote. :)
    kerr
    @hepin1989
    Maybe this will be fixed once sbt 1.4 come up with an BSP?
    Oron Port
    @soronpo
    Ever since 2020.x I'm constantly getting compile-server connection issues. I change the port scala.xml, to match what IJ reports, and after some time the port changes and it's broken again
    Now I got to a point that I changed the xml, and it even affect anything.
    Nikolay Tropin
    @niktrop
    @soronpo We need more details. Let's continue in our tracker
    https://youtrack.jetbrains.com/newIssue?project=SCL
    Dmitrii Naumenko
    @unkarjedy
    @soronpo
    Do you use Nightly plugin?
    Do you observe the issue in some project with dotty?
    Do you observe the issue mainly on project opening?
    Do you have any worksheet editors open in your project?
    Oron Port
    @soronpo
    I use the nightly. haven't tried dotty
    No worksheets
    I observe the issue all the time now. Can't get out of it.
    Brian P. Holt
    @bpholt
    Random feature request: autocomplete of the latest version of a dependency in a .sbt file
    Is anyone aware of such a thing?
    Gavin Bisesi
    @Daenyth
    I think there's an sbt plugin that allows you to use 1.^ version strings or so and then have a lock file to pin them, like some other languages do
    might work?
    OlegYch
    @OlegYch
    @bpholt i think it already supports that
    Brian P. Holt
    @bpholt
    🤯
    Idk, I tried it with different combinations of "org.typelevel" %% "cats-effect" % "2.1." to no avail :(
    OlegYch
    @OlegYch
    do you have maven plugin enabled?
    Brian P. Holt
    @bpholt
    hmm, good question
    probably not, I disabled all the plugins I thought I wouldn't need
    Gavin Bisesi
    @Daenyth
    whoa really?
    I also disabled maven, I had no idea I could do that
    OlegYch
    @OlegYch
    after updating indexes it should suggest versions
    although updating indexes doesn't seem to work for me atm
    Brian P. Holt
    @bpholt

    Yeah, after enabling it, I do get versions!

    Although… it only suggests 0.4, 0.10.1, and 2.0.0. Huh. (for cats-effect, I mean)

    It is warning me about a lot of unknown artifacts though, maybe I need to set something else up
    OlegYch
    @OlegYch
    damn my keymap is completely crapped in latest idea eap
    Oron Port
    @soronpo
    @OlegYch happened to me too
    The keymap thing
    OlegYch
    @OlegYch
    not sure if there is a better place
    Oron Port
    @soronpo
    But it looks like it's better to have a new issue
    Pavel Fatin
    @pavelfatin
    Just a quick reminder: you can follow https://twitter.com/IntelliJScala to get news and updates from the IntelliJScala team :)
    Philip
    @philipschwarz
    a bit off topic, but maybe someone can help
    I am writing some unison code - if I add the .u extension to the Haskell file type the result is quite good
    image.png
    image.png
    image.png
    image.png
    is there a way of stopping simbols like :arrow_right: && ++ () from being shown as if 'selected' (appearing in a box of a different, lighter colour) ?
    Nikolay Tropin
    @niktrop
    @philipschwarz It's probably better to ask author of Haskell plugin you are using.
    Philip
    @philipschwarz
    @niktrop doh, of course, thanks
    Jason Zaugg
    @retronym

    @niktrop I'm currently reimplementing scala-async as a phase of the compiler: scala/scala#8816 . A few details of name mangling are changing and I'm investigating how to adapt intellij-scala to these.

    The refactoring effort is in part to support a user of scala-async that integrates it via a compiler plugin that demarcates async blocks with annotations. The effect is quite similar to Kotlin's suspend functions. So I'd also like to find a way to make support for async in "evaluate expression" work in their environment, too. My idea is to detect replace (or augment) the current InsideAsync static analysis with a dynamic analysis of the enclosing classes in the VM at the breakpoint. If one of these has the 'fingerprint" of an async state machine, we can trigger the strategy of evaluating local variables and methods as selections of fields and methods from the state machine class.

    Does this sound like a reasonable approach? How does Kotlin's compiler/debugger handle things?

    While looking at this, I noticed at least one bug and an inefficient implemetation in some code contributed (as part of JetBrains/intellij-scala#386) to the the debugger. I'm tring to rework this in: https://github.com/retronym/intellij-scala/pull/1/commits/ea56504671599f5f837c21a05f592a154b141d4f

    For both of these changes I'd like to add a test case. I have a manual test in https://github.com/retronym/boxer/blob/topic/xasync/README.md. But rather than trying to introduce another third-party dependency to your build, I was thinking it would be simpler to have a debugger test that has one set of sources that will be loaded in the project when debugging, and a "shadow" set of sources that will be used to create the classfiles. The "shadow" sources can include the expansions that a compiler plugin would have made. If you think this approach makes sense,

    ... could you give a few pointers on how to refactor ScalaDebuggerTestBase to support that?
    If you have any general suggestions about ways that we could compile async state machines with better metadata to support debugging, please let me know.