AE2 illegal item error

[Lennartos]

Your GTNH Discord Username

Lennart#9359 / Lennartos

Your Pack Version

2.7 Beta 3

Your Server

private server

Java Version

Java 17

Type of Server

Vanilla Forge

Your Expectation

After update all was ok, we started to migrate to the new recipies.

The Reality

A few days ago we start to notice server slowdown and when i check, the log gets flooded with FATAL: DETECTED ILLEGAL ITEM TO BE INSERTED IN STORAGE CELL, PLEASE REPORT TO GITHUB.
This happens A LOT, server speed is abysmal and logs get to GB size in minutes.
We noticed a few weird issues, like corrupted fluid packets in storage (which we deleted with a trash can), and one item cell with droplets in it, that would not move to fluid storage.
Threw that in trash can as well... but no change.
Error persists.

Your Proposal

use the stack trace to find the issue, or extend the error message so it tells us the type and location of the offending item so we can kill it.

Final Checklist

• I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying the bug still exists will prompt us to investigate and reopen it once we confirm your report.
• I can reproduce this problem consistently by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.
• I have asked other people and they confirm they also have this problem by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.

[Lennartos]

I think i found it.
A storage cell was programmed with a oredict, and what was in it was not what it was programmed with.
once i removed that from the network it was fixed

[Lennartos]

I think something broke after the update / upgrade... some cells show this oredict, even when there is nothing in them.

This is only seen when you partition them, and when they are filled suddenly we get the crash bug as its illegal to put lets say a glass block into a dust* cell

[Lennartos]

Just saw a digital singluarity cell that is completely new (except partition with nether quartz dust) cause the bug when sucking nether quartz dust in a IO port from the main storage.
The cell did not show a dust* as i expected, main network did not have any nether quarts dust left, still the error came every tick.
Could there be a overlap in whatevr the io port requests so it tries to put different items that match its query inside a partitioned cell that then complains?