Hey guys, I have an odd question so to say. A colleague of mine is trying to run/compile Junit5 test...

# server

[Paulien van Alst]

Hey guys, I have an odd question so to say. A colleague of mine is trying to run/compile Junit5 tests using JDK 16 on a linux system. The file system is encrypted, the Kotlin files do have the correct permissions. However, when the function names (using back ticks) are becoming too long, the compiler fails as the generated class file is becoming too long. Has anyone encountered this?
Is there a compile flag to set this to avoid this problem?

[Klitos Kyriacou]

I've never come across such a problem, but then my test function names are no longer than about 120 characters. As a workaround, maybe they can use shorter function names but use the JUnit5 annotation @DisplayName to make the test report show exactly the name they want.

[Paulien van Alst]

Yes I figured that out as well but I am actually curious about how to fix it differently. Although it might be more of a filesystem problem

[ephemient]

https://youtrack.jetbrains.com/issue/KT-17433

[ephemient]

I think your only options are to avoid such long names or avoid using Windows and other length-restricted filesystems

[Paulien van Alst]

Ok thanks!

[napperley]

With Linux systems it is preferable to stick with the ext4 (the official Linux file system - https://en.wikipedia.org/wiki/Ext4 ) file system. Ext4 is less restrictive on file names than the Windows based file systems like NTFS for example.

[ephemient]

if you want an encrypted filesystem on Linux, block-level encryption (dm-crypt) and non-stacked filesystem encryption (fscrypt) do not impose the constraints that stacking filesystems like eCryptfs do