java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
at OSGi$.pekkoImport(OSGi.scala:147) at OSGi$.$anonfun$exports$1(OSGi.scala:136) at scala.Function1.$anonfun$compose$1(Function1.scala:49) at sbt.internal.util.EvaluateSettings$MixedNode.evaluate0(INode.scala:229) at sbt.internal.util.EvaluateSettings$INode.evaluate(INode.scala:171) at sbt.internal.util.EvaluateSettings.$anonfun$submitEvaluate$1(INode.scala:88) at sbt.internal.util.EvaluateSettings.sbt$internal$util$EvaluateSettings$$run0(INode.scala:100) at sbt.internal.util.EvaluateSettings$$anon$3.run(INode.scala:95) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1583) [error] java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1 Can't reload the sbt 何品 PJ Fanning <[email protected]> 于2025年11月17日周一 05:33写道： > This issue seems to be caused by https://github.com/apache/pekko/pull/2312 > It's not the only part of our build that is negatively affected when > we run from raw source as opposed to a git checkout. > With a git checkout, sbt-dynver calculates a version value for the > build based on git tags. > Otherwise, sbt generates a value but one that causes this OSGI code to > fail. > You can workaround the issue by specifying a version. > You can add a version.sbt file with a value like: > ThisBuild / version := "1.3.0" > > You can add this to the build.sbt too. > Or you can specify it in the sbt command line. > > I have verified that the version.sbt approach avoids this issue. > > If it is acceptable, reviewers can use this workaround for this > release and we can rework the OSGI build script to be more robust for > future releases. > > On Sun, 16 Nov 2025 at 22:09, Samuele Resca <[email protected]> > wrote: > > > > Hey, > > > > I was verifying the RC. I’m getting compile error on Java 21 and 17 due > to the inline. Am I missing something? I attach below the error. > > Thanks in advance. > > > > [info] Scala 2 optimizer/inliner enabled, to disable set the > pekko.no.inline system property > > java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for > length 1 > > at OSGi$.pekkoImport(OSGi.scala:147) > > at OSGi$.$anonfun$exports$1(OSGi.scala:136) > > at scala.Function1.$anonfun$compose$1(Function1.scala:49) > > at > sbt.internal.util.EvaluateSettings$MixedNode.evaluate0(INode.scala:229) > > at > sbt.internal.util.EvaluateSettings$INode.evaluate(INode.scala:171) > > at > sbt.internal.util.EvaluateSettings.$anonfun$submitEvaluate$1(INode.scala:88) > > at > sbt.internal.util.EvaluateSettings.sbt$internal$util$EvaluateSettings$$run0(INode.scala:100) > > at sbt.internal.util.EvaluateSettings$$anon$3.run(INode.scala:95) > > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) > > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) > > at java.base/java.lang.Thread.run(Thread.java:840) > > [error] java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds > for length 1 > > > > > > > On 16 Nov 2025, at 19:21, PJ Fanning <[email protected]> wrote: > > > > > > Hello Pekko Community, > > > > > > This is a call for a vote to release Apache Pekko (Core) 1.3.0-RC1. > > > > > > The discussion thread: > > > > > > https://lists.apache.org/thread/fdqmbzz8ddvd8bqwdtl11djd81k88oc0 > > > > > > The release candidate: > > > > > > https://dist.apache.org/repos/dist/dev/pekko/1.3.0-RC1/ > > > > > > This release has been signed with a PGP key available here: > > > > > > https://downloads.apache.org/pekko/KEYS > > > > > > Release Notes: > > > > > > > https://github.com/apache/pekko/pull/2500/files#diff-b77608f9884c5f0b45c2d1fd1ef389c7abb249fcc4cc785d31268edcefebe118 > > > > > > Git tag for the release: > > > > > > https://github.com/apache/pekko/tree/v1.3.0-RC1 > > > Git commit ID: 594e0572e135ff01733ee85d0e3ae0c38ebd2c3b > > > > > > Please download, verify, and test. > > > > > > I have also staged jars in the Apache Nexus Repository. These were > built > > > with the same code as appears in this Source Release Candidate. > > > I would appreciate if users could test with these too. > > > If anyone finds any serious problems with these jars, please also > notify us > > > on this thread. > > > > > > https://repository.apache.org/content/groups/staging/org/apache/pekko/ > > > > > > For sbt 1.9.4 or greater you can add this resolver > > > > > > resolvers += Resolver.ApacheMavenStagingRepo > > > > > > Otherwise for older versions of sbt > > > > > > resolvers += "Apache Pekko Staging" at > > > "https://repository.apache.org/content/groups/staging"; > > > > > > > > > The VOTE will pass if we have more positive votes than negative votes > > > and there must be a minimum of 3 approvals from Pekko PMC members. > > > Anyone voting in favour of the release, could you please provide a > list of > > > the checks you have done? > > > The vote will be left open for at least 72hrs. > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove with the reason > > > > > > To learn more about Apache Pekko, please see https://pekko.apache.org/ > > > > > > Checklist for reference: > > > > > > [ ] Download links are valid. > > > [ ] Checksums and signatures. > > > [ ] LICENSE/NOTICE files exist > > > [ ] No unexpected binary files > > > [ ] All source files have ASF headers > > > [ ] Can compile from source > > > [ ] Can verify the binary build > > > > > > To compile from the source, please refer to: > > > > > > > https://github.com/apache/pekko/tree/1.3.x?tab=readme-ov-file#building-from-source > > > > > > To verify the binary build, please refer to: > > > > > > > https://github.com/apache/pekko-site/wiki/Pekko-Release-Process#verifying-the-binary-build > > > > > > Some notes about verifying downloads can be found at: > > > > > > https://pekko.apache.org/download.html#verifying-downloads > > > > > > Thanks, > > > PJ Fanning (Apache Pekko PMC member) > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
