Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Logistics] Storage units fail to initialize (Nova v0.18-alpha.8) #537

Closed
5 tasks done
GabFran opened this issue Dec 18, 2024 · 0 comments
Closed
5 tasks done

[Logistics] Storage units fail to initialize (Nova v0.18-alpha.8) #537

GabFran opened this issue Dec 18, 2024 · 0 comments
Labels
resolution: fixed The bug has been fixed type: bug Something isn't working

Comments

@GabFran
Copy link

GabFran commented Dec 18, 2024

Agreements

  • I am using an official build of Nova.
  • I am running the latest version of Nova.
  • I am using a server software supported by Nova
  • I am running the latest version of my server software.
  • I have checked for similar issues.

Check for plugin incompatibilites

There are no other plugins running on my server.

Plugin Version, Server Software, Server Version

Paper 1.21.4-15, Nova v0.18-alpha.8

Nova Addons and Versions

Simple-Upgrades v1.5-alpha.2, Machines v0.4.7-alpha.5, Logistics v0.2.10-alpha.4

Expected behavior

No response

Observed/Actual behavior

Storage units fail to initialize upon loading, giving out an error for each storage unit loaded, and making them uninteractible.

Steps to reproduce

  1. Load a chunk which contains storage units
  2. Watch the console spit out errors

Server log

https://mclo.gs/F4kbzJr

Errors

[20:14:50 ERROR]: [Nova] Failed to initialize tile entity pos=BlockPos(world=world, x=53, y=63, z=79), blockState=logistics:vacuum_chest[], data={
  "inventory": xyz.xenondevs.invui.inventory.VirtualInventory@152bc409
  "itemHolder": {
    "channels": {NORTH=0, EAST=0, SOUTH=0, WEST=0, UP=0, DOWN=0}
    "connectionConfig": {NORTH=EXTRACT, EAST=EXTRACT, SOUTH=EXTRACT, WEST=EXTRACT, UP=EXTRACT, DOWN=EXTRACT}
    "containerConfig": {NORTH=00000000-0000-0000-0000-000000000a11, EAST=00000000-0000-0000-0000-000000000a11, SOUTH=00000000-0000-0000-0000-000000000a11, WEST=00000000-0000-0000-0000-000000000a11, UP=00000000-0000-0000-0000-000000000a11, DOWN=00000000-0000-0000-0000-000000000a11}
    "extractFilters": {}
    "extractPriorities": {NORTH=50, EAST=50, SOUTH=50, WEST=50, UP=50, DOWN=50}
  }
  "ownerUuid": 3e67b1b3-f6e9-4aba-8c6a-26f54cb75c53
  "persistent": (serialized) 0100
  "region.default": 3
  "upgrades": {simple_upgrades:range=4}
  "uuid": dbb6d66b-403b-469c-b947-b7aa9f104bf4
}
java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
        at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:100) ~[?:?]
        at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:106) ~[?:?]
        at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:302) ~[?:?]
        at java.base/java.util.Objects.checkIndex(Objects.java:385) ~[?:?]
        at java.base/java.util.ArrayList.set(ArrayList.java:470) ~[?:?]
        at xyz.xenondevs.invui.inventory.Inventory.setPreUpdateHandler(Inventory.java:391) ~[?:?]
        at Logistics-0.2.10-alpha.4.jar/xyz.xenondevs.nova.addon.logistics.tileentity.VacuumChest.<init>(VacuumChest.kt:66) ~[Logistics-0.2.10-alpha.4.jar:?]
        at Logistics-0.2.10-alpha.4.jar/xyz.xenondevs.nova.addon.logistics.registry.Blocks$VACUUM_CHEST$1.invoke(Blocks.kt:76) ~[Logistics-0.2.10-alpha.4.jar:?]
        at Logistics-0.2.10-alpha.4.jar/xyz.xenondevs.nova.addon.logistics.registry.Blocks$VACUUM_CHEST$1.invoke(Blocks.kt:76) ~[Logistics-0.2.10-alpha.4.jar:?]
        at Nova-0.18-alpha.8.jar/xyz.xenondevs.nova.world.format.chunk.RegionChunk.initNovaTileEntities(RegionChunk.kt:117) ~[Nova-0.18-alpha.8.jar:?]
        at Nova-0.18-alpha.8.jar/xyz.xenondevs.nova.world.format.chunk.RegionChunk.<init>(RegionChunk.kt:76) ~[Nova-0.18-alpha.8.jar:?]
        at Nova-0.18-alpha.8.jar/xyz.xenondevs.nova.world.format.chunk.RegionChunk$Companion.read(RegionChunk.kt:616) ~[Nova-0.18-alpha.8.jar:?]
        at Nova-0.18-alpha.8.jar/xyz.xenondevs.nova.world.format.chunk.RegionChunk$Companion.read(RegionChunk.kt:583) ~[Nova-0.18-alpha.8.jar:?]
        at Nova-0.18-alpha.8.jar/xyz.xenondevs.nova.world.format.RegionizedFileReader.read$lambda$4$lambda$3(RegionizedFile.kt:141) ~[Nova-0.18-alpha.8.jar:?]
        at Nova-0.18-alpha.8.jar/xyz.xenondevs.nova.world.format.RegionFile$Companion$1.invoke(RegionFile.kt:27) ~[Nova-0.18-alpha.8.jar:?]
        at Nova-0.18-alpha.8.jar/xyz.xenondevs.nova.world.format.RegionFile$Companion$1.invoke(RegionFile.kt:27) ~[Nova-0.18-alpha.8.jar:?]
        at Nova-0.18-alpha.8.jar/xyz.xenondevs.nova.world.format.RegionizedFileReader.read(RegionizedFile.kt:138) ~[Nova-0.18-alpha.8.jar:?]
        at Nova-0.18-alpha.8.jar/xyz.xenondevs.nova.world.format.RegionizedFileReader.read(RegionizedFile.kt:116) ~[Nova-0.18-alpha.8.jar:?]
        at Nova-0.18-alpha.8.jar/xyz.xenondevs.nova.world.format.WorldDataStorage$getOrLoadRegionizedFileAsync$2$1$1.invokeSuspend(WorldDataStorage.kt:58) ~[Nova-0.18-alpha.8.jar:?]
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) ~[?:?]
        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101) ~[?:?]
        at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:113) ~[?:?]
        at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89) ~[?:?]
        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:589) ~[?:?]
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:823) ~[?:?]
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:720) ~[?:?]
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:707) ~[?:?]

Additional context

Release v0.18-alpha.7 does not have this issue.
Issue is contained within changes made for release v0.18-alpha.8.

@GabFran GabFran added the type: bug Something isn't working label Dec 18, 2024
@NichtStudioCode NichtStudioCode added the resolution: fixed The bug has been fixed label Dec 19, 2024
@GabFran GabFran changed the title [Logistics] - Storage units fail to initialize (Nova v0.18-alpha.8) [Logistics] Storage units fail to initialize (Nova v0.18-alpha.8) Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolution: fixed The bug has been fixed type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants