feat: upgrade scala native to latest and enable multithreading

[asr2003]

Upgraded ZIO and Scala-Native to their latest versions and while enabling multithreading=true, it resulted in the Out of heap space which is an issue with scala-native and an active discussion is going here in the upstream:

• "Out of heap space grow heap" error after migration to v0.5.5 scala-native/scala-native#4032

Note that the GC change is only needed for few tests which are memory intensive. Once that's upstream is fixed I think we can remove that config safely

fixes #720
/claim #720

[987Nabil]

Closing in favor of #732 since this is not fixing #720
While reactivating multithreading and updating zio/scala-native is something we want, #720 was already fixed by me in #726
I only use #732 to collect the bounty since it is related and easier then to communicate with algora.

[asr2003]

@987Nabil I didn't get it what's wrong with my PR 🙄 and closed I have seen yesterday the issue and I am also one of who tried enabling multithreading in Zio along with @varshith257, so I have good context of this upgradation and Multithreading issue, so seems the same work of Zio here and raised PR. I

…

On Sat, 31 Aug, 2024, 6:03 pm Nabil Abdel-Hafeez, ***@***.***> wrote: Closing in favor of #732 <#732> since this is not fixing #720 <#720> While reactivating multithreading and updating zio/scala-native is something we want, #720 <#720> was already fixed by me in #726 <#726> I only use #732 <#732> to collect the bounty since it is related and easier then to communicate with algora. — Reply to this email directly, view it on GitHub <#735 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGXZB6A5JW6FPOQBTRBBMATZUGZYBAVCNFSM6AAAAABNNJ7WEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRSHA4DIMJRGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[asr2003]

zio/scala-native is something we want

Yes I have done the same of upgrading zio and native .

…

On Sat, 31 Aug, 2024, 6:11 pm Unknown, ***@***.***> wrote: @987Nabil I didn't get it what's wrong with my PR 🙄 and closed I have seen yesterday the issue and I am also one of who tried enabling multithreading in Zio along with @varshith257, so I have good context of this upgradation and Multithreading issue, so seems the same work of Zio here and raised PR. I On Sat, 31 Aug, 2024, 6:03 pm Nabil Abdel-Hafeez, < ***@***.***> wrote: > Closing in favor of #732 <#732> > since this is not fixing #720 > <#720> > While reactivating multithreading and updating zio/scala-native is > something we want, #720 <#720> > was already fixed by me in #726 > <#726> > I only use #732 <#732> to collect > the bounty since it is related and easier then to communicate with algora. > > — > Reply to this email directly, view it on GitHub > <#735 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/BGXZB6A5JW6FPOQBTRBBMATZUGZYBAVCNFSM6AAAAABNNJ7WEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRSHA4DIMJRGQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[987Nabil]

@asr2003 #720 mentions clearly fixing the CI. The CI was already fixed in #726. Updating zio and reenabling native multi threading has nothing to do with the issue.