Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

`resolveObject` fails with `IndexOutOfBoundsException`

Aperta
  • Qualcosa non va?
#164 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Damtev ci sta già lavorando.

Dal 29/11/2023.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

bug

Run ContestEstimator with the following options:

timeLimit = 120
methodFilter = "io.seata.core.protocol.transaction.GlobalBeginResponse.doEncode"
projectFilter = listOf("seata-core-0.5.0")

There are the following errors in log:

15:03:28.174 | ERROR | executor.execute((id:23)io.seata.core.protocol.transaction.GlobalBeginResponse#doEncode()) failed
java.lang.IndexOutOfBoundsException: Index: 15, Size: 15
	at java.util.ArrayList.rangeCheck(ArrayList.java:659) ~[?:1.8.0_392]
	at java.util.ArrayList.get(ArrayList.java:435) ~[?:1.8.0_392]
	at org.usvm.api.util.JcTestStateResolver.resolveEnumValue(JcTestStateResolver.kt:281) ~[usvm-jvm-local3.jar:?]
	at org.usvm.api.util.JcTestStateResolver.resolveObject(JcTestStateResolver.kt:222) ~[usvm-jvm-local3.jar:?]
	at org.utbot.contest.usvm.jc.JcTestExecutor$MemoryScope.resolveObject(JcTestExecutor.kt:164) ~[main/:?]
	at org.utbot.contest.usvm.jc.JcTestExecutor$MemoryScope.resolveObject(JcTestExecutor.kt:117) ~[main/:?]
	at org.usvm.api.util.JcTestStateResolver.resolveReference(JcTestStateResolver.kt:173) ~[usvm-jvm-local3.jar:?]
	at org.usvm.api.util.JcTestStateResolver.resolveExpr(JcTestStateResolver.kt:103) ~[usvm-jvm-local3.jar:?]
	at org.usvm.api.util.JcTestStateResolver.resolveLValue(JcTestStateResolver.kt:97) ~[usvm-jvm-local3.jar:?]
	at org.usvm.api.util.JcTestStateResolver.allocateAndInitializeObject(JcTestStateResolver.kt:268) ~[usvm-jvm-local3.jar:?]
	at org.usvm.api.util.JcTestStateResolver.resolveObject(JcTestStateResolver.kt:225) ~[usvm-jvm-local3.jar:?]
	at org.utbot.contest.usvm.jc.JcTestExecutor$MemoryScope.resolveObject(JcTestExecutor.kt:164) ~[main/:?]
	at org.utbot.contest.usvm.jc.JcTestExecutor$MemoryScope.resolveObject(JcTestExecutor.kt:117) ~[main/:?]
	at org.usvm.api.util.JcTestStateResolver.resolveReference(JcTestStateResolver.kt:173) ~[usvm-jvm-local3.jar:?]
	at org.usvm.api.util.JcTestStateResolver.resolveExpr(JcTestStateResolver.kt:103) ~[usvm-jvm-local3.jar:?]
	at org.usvm.api.util.JcTestStateResolver.resolveLValue(JcTestStateResolver.kt:97) ~[usvm-jvm-local3.jar:?]
	at org.utbot.contest.usvm.jc.JcTestExecutor$MemoryScope.createUTest(JcTestExecutor.kt:132) ~[main/:?]
	at org.utbot.contest.usvm.jc.JcTestExecutor.execute(JcTestExecutor.kt:76) ~[main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$runUsvmGeneration$1$9$5.invoke(ContestUsvm.kt:179) [main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$runUsvmGeneration$1$9$5.invoke(ContestUsvm.kt:172) [main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1$1$1.addState(ContestUsvm.kt:284) [main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1$1$1.addState(ContestUsvm.kt:278) [main/:?]
	at org.usvm.statistics.collectors.CoveredNewStatesCollector.onStateTerminated(CoveredNewStatesCollector.kt:26) [usvm-core-local3.jar:?]
	at org.usvm.statistics.CompositeUMachineObserver.onStateTerminated(UMachineObserver.kt:48) [usvm-core-local3.jar:?]
	at org.usvm.UMachine.run(Machine.kt:77) [usvm-core-local3.jar:?]
	at org.usvm.machine.JcMachine.analyze(JcMachine.kt:199) [usvm-jvm-local3.jar:?]
	at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1.invoke(ContestUsvm.kt:276) [main/:?]
	at org.utbot.contest.usvm.ContestUsvmKt$analyzeAsync$1.invoke(ContestUsvm.kt:274) [main/:?]
	at org.utbot.common.ThreadBasedExecutor$invokeWithTimeout$1.invoke(ThreadUtil.kt:75) [utbot-core-2023.11-SNAPSHOT.jar:?]
	at org.utbot.common.ThreadBasedExecutor$ensureThreadIsAlive$1.invoke(ThreadUtil.kt:129) [utbot-core-2023.11-SNAPSHOT.jar:?]
	at org.utbot.common.ThreadBasedExecutor$ensureThreadIsAlive$1.invoke(ThreadUtil.kt:125) [utbot-core-2023.11-SNAPSHOT.jar:?]
	at kotlin.concurrent.ThreadsKt$thread$thread$1.run(Thread.kt:30) [kotlin-stdlib-1.8.22.jar:1.8.22-release-407(1.8.22)]
15:03:28.689 | ERROR | (x2) executor.execute((id:23)io.seata.core.protocol.transaction.GlobalBeginResponse#doEncode()) failed
java.lang.IndexOutOfBoundsException: Index: 1073741824, Size: 15
	at java.util.ArrayList.rangeCheck(ArrayList.java:659)
15:03:30.259 | ERROR | (x5) executor.execute((id:23)io.seata.core.protocol.transaction.GlobalBeginResponse#doEncode()) failed
java.lang.IndexOutOfBoundsException: Index: 1025, Size: 15
	at java.util.ArrayList.rangeCheck(ArrayList.java:659)
15:03:37.867 | ERROR | (x10) executor.execute((id:23)io.seata.core.protocol.transaction.GlobalBeginResponse#doEncode()) failed
java.lang.IndexOutOfBoundsException: Index: 1073741824, Size: 15
	at java.util.ArrayList.rangeCheck(ArrayList.java:659)
Lingua principale
Kotlin
Stelle
33
Fork
27
Merge medio
3g 8h
PR unite (30g)
7

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di UnitTestBot/usvm

Tutte le issue di UnitTestBot/usvm

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.