Sender | Message | Time |
---|---|---|
22 May 2024 | ||
balmungsan3 | It still uses Scala 3 on sbt | 16:22:21 |
balmungsan3 | So I left that and fixed scalafmt instead | 16:22:31 |
bjaglin | oh 😦 I guess it's a limitation of metals which calls scalafix with the scalaVersion of the build, even for .sbt files | 17:21:38 |
tgodzik#4885 | Hmm... Isn't that because scalafix.conf only points to single Scala version | 17:23:27 |
bjaglin | That's unlikely with Auto | 18:57:44 |
tgodzik#4885 | Hmm... We do have info about a version for sbt though. Something might be wrong for sure though | 19:01:45 |
tgodzik#4885 | Worth filing an issue | 19:01:51 |
23 May 2024 | ||
azaad1789 joined the room. | 06:53:13 | |
im_bharadwajj changed their display name from boomboom9929 to im_bharadwajj. | 11:41:51 | |
_tibor_ joined the room. | 14:02:31 | |
YeOldePorkchop changed their display name from yeoldeporkchop to Michael D. | 15:43:58 | |
Jesse (jsatk) changed their profile picture. | 17:01:56 | |
28 May 2024 | ||
younguyen joined the room. | 10:50:33 | |
29 May 2024 | ||
btrachey changed their profile picture. | 13:03:25 | |
kubukoz#8644 changed their profile picture. | 15:59:59 | |
30 May 2024 | ||
lolgab changed their profile picture. | 17:02:05 | |
31 May 2024 | ||
Thibault joined the room. | 15:36:03 | |
Thibault | 15:36:04 | |
Thibault | Download IllegalFormatString.scala | 15:36:04 |
Thibault | Hi! I'm working on rules for Scalafix and I tried importing my rules to my codebase. When I try to run my rules, I get an error for some of them saying "Unable to get public no-arg constructor" even though my class doesn't take any arguments (it simply extends SemanticRule). In one of my classes, it was due to a global variable being present, but in the other class there is no such thing and I am really not seeing any reason for it. Did someone experience something similar? I attached my rule | 15:36:06 |
Thibault | * Hi! I'm working on rules for Scalafix and I tried importing my rules to my codebase. When I try to run my rules, I get an error for some of them saying "Unable to get public no-arg constructor" even though my class doesn't take any arguments (it simply extends SemanticRule). All tests pass though. In one of my classes, it was due to a global variable being present, but in the other class there is no such thing and I am really not seeing any reason for it. Did someone experience something similar? I attached my rule | 15:36:38 |
Thibault | * Hi! I'm working on rules for Scalafix and I tried importing my rules to my codebase. When I try to run my rules, I get an error for some of them saying " Unable to get public no-arg constructor " even though my class doesn't take any arguments (it simply extends SemanticRule). All tests pass though.In one of my classes, it was due to a global variable being present, but in the other class there is no such thing and I am really not seeing any reason for it. Did someone experience something similar? I attached my rule, the exact error I get is [error] (linter / Compile / scalafix) java.util.ServiceConfigurationError: scalafix.v1.Rule: fix.IllegalFormatString Unable to get public no-arg constructor | 15:37:42 |
Thibault | * Hi! I'm working on rules for Scalafix and I tried importing my rules to my codebase. When I try to run my rules, I get an error for some of them saying " Unable to get public no-arg constructor " even though my class doesn't take any arguments (it simply extends SemanticRule). All tests pass though.In one of my classes, it was due to a global variable being present, but in the other class there is no such thing and I am really not seeing any reason for it. Did someone experience something similar? I attached my rule, the exact error I get is [error] (linter / Compile / scalafix) java.util.ServiceConfigurationError: scalafix.v1.Rule: fix.IllegalFormatString Unable to get public no-arg constructor | 15:37:56 |
1 Jun 2024 | ||
brndt_43397 joined the room. | 18:42:44 | |
bjaglin | It doesn't ring a bell. I tried reproducing your issue (after stripping the internal import), but didn't get that error. 1. Are your rules distributed via a JAR? If so, which JDK is used to compile them vs the JRE to execute them? I am not aware of any bytecode incompatibility when instantiating scala classes via ServiceLoader (which is the source of the 0-arg public constructor constraint) but who knows... 1. I assume adding an explicit constructor fixes the issue? If not, did you check the bytecode via javap -c IllegalFormatString ? | 21:21:41 |
bjaglin | * It doesn't ring a bell. I tried reproducing your issue (after stripping the internal import), but didn't get that error. 1. Are your rules distributed via a JAR? If so, which JDK is used to compile them vs the JRE to execute them? I am not aware of any bytecode incompatibility when instantiating scala classes via ServiceLoader (which is the source of the 0-arg public constructor constraint) but who knows... 1. I assume adding an explicit constructor fixes the issue? If not, did you check the bytecode via something like javap -c IllegalFormatString ? | 21:22:01 |
bjaglin | * It doesn't ring a bell 🤔 I tried reproducing your issue (after stripping the internal import), but didn't get that error. 1. Are your rules distributed via a JAR? If so, which JDK is used to compile them vs the JRE to execute them? I am not aware of any bytecode incompatibility when instantiating scala classes via ServiceLoader (which is the source of the 0-arg public constructor constraint) but who knows... 1. I assume adding an explicit constructor fixes the issue? If not, did you check the bytecode via something like javap -c IllegalFormatString ? | 21:22:11 |
2 Jun 2024 | ||
Thibault | It doesn't ring a bell 🤔 I tried | 17:01:19 |
Thibault changed their display name from tiboepfl to Thibault. | 17:01:23 | |
23 Jun 2024 | ||
@devfuuu:matrix.org left the room. | 22:27:18 |