StackOverflowError from KAPT on building Arrow about arrow-core HOT 14 OPEN

@calvellido that looks like something different: @nomisRev should take a look at that ^^

from arrow-core.

I tried:

• 4.15.0-74 ❌
• 4.15.0-72 ❌
• 4.15.0-70 ❌
• 4.10.0-38 ❌
• 4.8.0-53 ❌

All of them leading to the same error:

> Task :arrow-core:kaptKotlin FAILED
e: [kapt] An exception occurred: java.lang.StackOverflowError

😭

from arrow-core.

@1Jajen1 thanks for the poke!
@calvellido that is definitely something else, looks like a bad merge to me. I will take a look asap ;)

from arrow-core.

Thanks @abelkov! However, I think we could look at something else. I'm on Ubuntu 18.04 and I don't have that problem. We're using Ubuntu 18.04 on GitHub environments and it also works properly:

Run cat /proc/version
Linux version 5.0.0-1027-azure (buildd@lgw01-amd64-033) 
(gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) 
arrow-kt/arrow#29~18.04.1-Ubuntu SMP Mon Nov 25 21:18:57 UTC 2019

Run java -version
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (Zulu 8.42.0.23-CA-linux64) (build 1.8.0_232-b18)
OpenJDK 64-Bit Server VM (Zulu 8.42.0.23-CA-linux64) (build 25.232-b18, mixed mode)

Please, does it happen with previous commits? Thanks in advance!

from arrow-core.

And please, check your running processes, Gradle daemons, ...

from arrow-core.

Yes, it also fails on some previous commits and on a different JDK 8 from Azul, and when I run gradle with --no-daemon. Given that it's not blocking me and nobody else seems to have this problem, I think we can ignore this for now. Thanks.

from arrow-core.

Yes, it also fails on some previous commits and on a different JDK 8 from Azul, and when I run gradle with --no-daemon. Given that it's not blocking me and nobody else seems to have this problem, I think we can ignore this for now. Thanks.

Thank @abelkov so much for the info!! There is another person with the same problem. Let's see if we find some clue...

from arrow-core.

It also happens to me (similar environment), but I haven't been able to dig deeper on what could be the source for this 😢

from arrow-core.

Current tests are also failing due to a StackOverflow error, though I don't know how related these two are:

https://github.com/arrow-kt/arrow/pull/1934/checks?check_run_id=394918808#step:4:4960

from arrow-core.

I was reviewing this issue with @nomisRev because he got an error with JitPack.io.

We observed that the same commit produced different results:

• https://jitpack.io/com/github/arrow-kt/arrow/0.10.4/build.log
• https://jitpack.io/com/github/arrow-kt/arrow/d5d623338d1ed16271bbbb7f5422ce7a053ed96b/build.log

The only difference is the assigned machine.

After doing more checks with other commits, we observed that JitPack.io assigned machines in a random way:

• Linux 4.10.0-28-generic amd64
• Linux 4.14.63-xxxx-std-ipv6-64 amd64
• Linux 4.18.0-13-generic amd64

Just it works with 4.10.0-28-generic amd64.

More data from personal dev environments:

• KO: Linux 4.15.0-74-generic amd64
• OK: Linux 5.3.0-26-generic amd64

And GitHub Actions environment for ubuntu-latest: Linux 5.0.0-1028-azure amd64

from arrow-core.

Hi! this could be tried again with the new organization. Thanks!!

from arrow-core.

Still failing for me after the split 😭

• 4.15.0-88 ❌

from arrow-core.

After seeing #91 it seems to me that there might be some recursive calling in the Meta processors that some systems are able to handle due to bigger heap memory than others, that's why it could be happening "randomly" on CI based on #25 (comment) cc @raulraja @i-walker

from arrow-core.

After seeing #91 it seems to me that there might be some recursive calling in the Meta processors that some systems are able to handle due to bigger heap memory than others, that's why it could be happening "randomly" on CI based on #25 (comment) cc @raulraja @i-walker

That is the case, recursion in our kapt processors is not stack safe. It will also not terminate in some cases if you make complex recursive type nesting. We don't plan to fix it as we have reencoded most of them in meta or will be superceded soon by this new features.

from arrow-core.