Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 13:38

    mwz on master

    Update mockito-scala to 1.11.0 … (compare)

  • 13:38
    mwz closed #354
  • 07:19
    scala-steward opened #354
  • 00:36
    mwz synchronize #350
  • 00:36

    mwz on update-scala-2.13

    Update mockito-scala to 1.10.6 … Update http4s-blaze-client, ...… Merge branch 'master' into upda… (compare)

  • 00:33
    mwz edited #350
  • 00:28
    mwz synchronize #350
  • 00:28

    mwz on update-scala-2.13

    Fix issues. Add sbt-tpolecat. Update Scapegoat tests. (compare)

  • Jan 21 23:29
    mwz commented #350
  • Jan 21 23:22

    mwz on master

    Update http4s-blaze-client, ...… (compare)

  • Jan 21 23:22
    mwz closed #352
  • Jan 21 23:22

    mwz on master

    Update mockito-scala to 1.10.6 … (compare)

  • Jan 21 23:22
    mwz closed #353
  • Jan 21 22:09
    scala-steward opened #353
  • Jan 21 22:09
    scala-steward opened #352
  • Jan 20 12:28
    mwz commented #351
  • Jan 20 11:44
    yuxh commented #351
  • Jan 20 11:44
    yuxh closed #351
  • Jan 20 11:44
    yuxh edited #351
  • Jan 20 11:40
    yuxh opened #351
Michael Wizner
@mwz
@/all 7.0.0 has been released along with new docker images here.
Almaz Murzabekov
@Almaz-KG

Hi, guys!

Can you help me with sonar on scala project with maven?
I all time got an error like: module1/src/test/scala/delta/MyClass.scala can't be indexed twice. Please check that inclusion/exclusion

Running script is:
mvn install sonar:sonar -Dsonar.projectKey=analytics -Dsonar.host.url=http://localhost:9000 -Dsonar.login=${LOGIN} -Dsonar.exclusions=test/ -Dsonar.sources=src/main/ -Dsonar.sourceEncoding=UTF-8 -Dsonar.scala.version=2.11 -Dsonar.core.codeCoveragePlugin=scoverage -Dsonar.scala.scoverage.reportPath=target/scoverage.xml -Dsonar.scoverage.reportPath=target/scoverage.xml -Dsonar.junit.reportsPath=target/surefire-reports

Michael Wizner
@mwz
Hi @Almaz-KG, I’ve not experienced this issue before, but maybe you should try using sonar.test.exclusions instead of sonar.exclusions to exclude tests?
Michael Wizner
@mwz
Please check that inclusion/exclusion patterns produce disjoint sets for source and test files
Almaz Murzabekov
@Almaz-KG
@mwz, Thanks!
Michael Wizner
@mwz
@/all 7.1.0 has been released along with new docker images here.
Michael Wizner
@mwz
Hi @BalmungSan, unfortunately SonarSource have depracated the sonar-github plugin in favour of their Developer edition of SonarQube, which is a paid version :moneybag: Sounds like I need to write a replacement plugin for integration with Github, are you interested in collaborating? :)
Luis Miguel Mejía Suárez
@BalmungSan

Wow, a surprise to be sure. I, and probably my team, will try to help - to be honest we have been thinking in adding it to our projects too :smile:

BTW, I'm sorry for not being too active the last months, I'm finishing my last semester while working, and it has been tougher of what I expected :disappointed:

Michael Wizner
@mwz
I hope you will do well! I’ve been there myself and I can remember that it isn’t easy juggling work and uni.
Deprecation of the github plugin is quite dissapointing, especially that I was relying on it in my other project for running analysis on public PRs (which I haven’t open-sourced yet but it’s close now), so it makes things a bit more complicated. The plugin actually no longer works starting from SonarQube 7.3 and I’m sure they will also remove the sonar.analysis.mode setting from sonar-scanner at some point too, but I hope we can find some workarounds. I’ll try to kick something off soon-ish. Forcing you to pay for the features that were free before isn’t a good way to go and that decision has made a lot of people unhappy!
Btw, they are also close to releasing the official SonarScala plugin with SonarQube 7.5, which is coming out later this year, I believe, so we’ll see what features it has (apparently includes scalastyle and scapegoat integration). They’ve made it available on SonarCloud recently, so I’ll give it a go and maybe even integrate our sonar-scala with it =) I haven’t seen their built-in inspections yet, but I’m planning to checki it out soon.
Luis Miguel Mejía Suárez
@BalmungSan

"I hope you will do well!"

Ty :smile:

"Deprecation of the github plugin is quite disappointing"
"Forcing you to pay for the features that were free before isn’t a good way to go and that decision has made a lot of people unhappy!"

Yeah, those are bad news for many people, even in an enterprise level, making it pay-only means that less people will have experience with it - even if you're paying and using it.

"I’m planning to check it out soon"

Cool, I hope they made it open source. If it is good enough we probably will end up contributing to it - I don't see any value in "compete" with them, unless there is a good reason to.

Michael Wizner
@mwz
@/all 7.2.0 and 6.7.0 have been released along with new docker images here.
Michael Wizner
@mwz
@/all 7.3.0 was released along with new docker images here.
Michael Wizner
@mwz
@/all 7.3.1 was released along with new docker images here.
Luis Miguel Mejía Suárez
@BalmungSan

@mwz Hi Michael, I have a question.
Looking at the code, the changes are not that hard...

However, since the concept of module has been removed, and all of our sensors are intended to work on module level, I am not sure how these changes will affect us ( and our users).

For single module projects, all will work as usual - but, for multi-module projects, I think they will not behave as we expect.

I am not sure what would the best, if generate aggregate reports (for Scoverage, Scalastyle, Scapegoat & Junit), or run sonar per module, or if we (from the plugin) aggregate all the reports.

Also, I am not sure if this means that we could just do nothing for now. Since sonar will do the aggregation manually.

"The new scanner engine will be in charge of aggregating data for the different modules and will generate a report with files only."

Because, they are talking about the Scanner, and not the Plugins directly.

Some links that I readed:
https://docs.sonarqube.org/latest/setup/upgrade-notes/
https://jira.sonarsource.com/browse/MMF-365
https://docs.sonarqube.org/display/DEV/API+Changes

Michael Wizner
@mwz
Thanks @BalmungSan! The recent changes look interesting, I'll have a look at the docs and will get back to you.
Michael Wizner
@mwz
@/all 6.8.0 LTS was released along with new docker images here.
Michael Wizner
@mwz
@/all 7.4.0 was released along with new docker images here. Thanks for all of your PRs @BalmungSan!
Michael Wizner
@mwz
@/all 7.5.0 was released along with new docker images here.
Michael Wizner
@mwz
@/all 7.7.0 was released with support for SonarQube 7.9 LTS. New docker images can be found here.
Martin Todorov
@carlspring
Hi, guys! :)
Is there a way to set the scalastyle report path location?
Michael Wizner
@mwz
Hi @carlspring, I’m not sure what happened to the discussion in the thread above, but Gitter is so bad that I had to disable it as it doesn’t work.
To answer your question, there is no way to use an external scalastyle report in sonar-scala. Scalastyle gets executed inside the plugin and the config including severity levels come directly from your quality profile in SonarQube. I mentioned about this before in my post here https://github.com/mwz/sonar-scala/issues/179#issuecomment-477719803.
Martin Todorov
@carlspring
Thanks for the explanation, @mwz!
Slack is probably a better chat
Martin Todorov
@carlspring
For my own OSS project we're using RocketChat on our own cloud server
It has its issues as well, but it's free and it's better than Gitter.
I had high hopes for Gitter, where we started the project, but its sadly not very good... (I appreciate that it's a free service, of course).
Michael Wizner
@mwz
Zulip and Discord are also good options
Martin Todorov
@carlspring
I haven't tried either, but might give them a go soon enough, because RocketChat is a bit buggy as well... :(
Yaroslav Derman
@yarosman
Hello. Have you ever had problems with showing failed test in sonar? For example, my Spec failed on some step, but in sonar I don't see specific failed test. I see only failed Spec file
Michael Wizner
@mwz
Hi @yarosman, this might be actually not implemented yet, but I'd need to double check. We might have left this out because it just doesn't make sense to have broken tests in your project.
Yaroslav Derman
@yarosman
It works, if you don't have integration tests. But in my case I have integration tests with third party side, and it would be much better to see failed test in sonar rather than somewhere in console
Michael Wizner
@mwz
Makes sense, could you raise an issue on Github?
Yaroslav Derman
@yarosman
Done
Michael Wizner
@mwz
Thanks
Luis Miguel Mejía Suárez
@BalmungSan
I must say, that I love the new logo :tada:
Michael Wizner
@mwz
Haha thanks, I hope you enjoy the new functionality too :smile:
Luis Miguel Mejía Suárez
@BalmungSan
Yeah, looking forward to using it once I return to my scala projects. On these days I have been doing Python for an "Analytical" project :disappointed:
Michael Wizner
@mwz
Python is ok, but personally I couldn’t take a long break from Scala!
I’ve been doing a bit of ML with Python recently outside of work and it it’s just shocking to me how everything is mutable and non-referentially transparent. Obviously, you don’t need those in Jupyter notebooks, but regardless mutating state still feels wrong to me :laughing:
@/all 7.8.0 was released with support for pull request decoration on Github. New docker images can be found as always here.
Luis Miguel Mejía Suárez
@BalmungSan
@mwz my two problems with Python are. The weak and dynamic type system, like I do not understand how people is capable of knowing what to do with their variables. And second, that even if everyone says that it is an easy language, every time I need to do something serious I need to do a lot of work and if I replicate that in Scala it becomes a few lines of more readable code. But yeah, Python libraries like Numpy are fantastic!
Michael Wizner
@mwz
yeah the entire ML ecosystem is focused around Python, although I’ve recently discovered this https://scalapy.dev and the bindings for tensorflow https://github.com/shadaj/scalapy-tensorflow - I haven’t tried it yet but it looks promising
and recently released Polynote which is a notebook with Scala support makes it easy to mix Python and Scala https://polynote.org
Luis Miguel Mejía Suárez
@BalmungSan
Cool!
Luis Miguel Mejía Suárez
@BalmungSan
@mwz I was thinking that probably it would be better to drop the sbt-sonar gitter room and just leave this.
Since you already move the documentation to the same micro-site.
Also, what about creating a github org with all the related repos.
Michael Wizner
@mwz
yeah, I’m planning to do all of that :sweat_smile:
Luis Miguel Mejía Suárez
@BalmungSan
Haha, yeah a lot of work going on these days.
Thanks for all this :smile:
Michael Wizner
@mwz
;) also next on my list is forking and sorting out Scalastyle - I want to add 2.13 support
this PR has perfect timing scalastyle/scalastyle#353
Luis Miguel Mejía Suárez
@BalmungSan
:tada:
Michael Wizner
@mwz
@/all sonar-scala has a website now, so make sure you check it out - https://sonar-scala.com