Hugo van Rijswijk

For anyone also running into this issue, a workaround is to set the Temp drive to `D:\Temp`. For example, as a first step on GitHub actions: ```yaml steps: # https://github.com/ryanclark/karma-webpack/issues/494...

Hi @varnit24! This would be a great feature to have. What do you think would be a good workflow for aggregating multiple reports? Stryker4s now writes a file in a...

Hi, does Stryker4s still continue? Since 0.14.0 Stryker4s is able to deal with compile errors and mark them in the report. We don't have enough type information to know Spark...

@monoti I don't think that will happen anytime in the near future. Otherwise if we ever do type analysis for every mutant we'd have to check a possible mutation to...

Sorry for the late reply 😅. I quite like the idea of limiting the amount of messages outputted to the user in the scenario you outlined. The console reporter is...

@MercurieVV Thanks for looking into it! Last time I had a look I found the same. Back then I thought maybe compiling any dependencies to semanticdb would be the solution,...

> Btw what's your typical workflow for testing the plugin locally Yes, `publishLocal`, then change the version number in `plugins.sbt` and run Stryker. No need to clean anything. > Please...

@cbrunnkvist any update on this?

Hi! Thanks for creating this issue. I think this is a bug in Stryker4s. I can reproduce the example repo. Removing `base-dir: "."` from the config fixes the exception thrown....

@cbrunnkvist Yes, to prevent duplicate data in the JSON, the mutation score is calculated on the fly. Rendering the html report definitely doesn't seem ideal, haha. You might want to...