Subnet contents not visible through storage busses

[Kyramesh]

Your GTNH Discord Username

Kyramesh

Your Pack Version

2.7 Beta 3

Your Server

SP

Java Version

Java 21

Type of Server

None

Your Expectation

Making contents of an AE net available through Interface -> filtered Storage bus connections.

The Reality

Content of net A is inexplicably not visible in net B (in terminal and for autocrafting). Examples: https://discord.com/channels/181078474394566657/522098956491030558/1305298344259883159 Stocking Bus seems to be able to access contents even though a terminal can't.

https://discord.com/channels/181078474394566657/522098956491030558/1305901151102963743 Having storabge busses "importing" and "exporting" contents, especially if mutltiple nets are involed, seems to cause this, even if the storage busses are filtered in such a way that no recursive loop could form.

I think this issue then causes the following error when attempting to order crafts, which involve items from other nets:

I can't consistently cause the issue to arise. The system works fine for a while and then stops, for yet to determine reasons.

Your Proposal

Identify the issue and fix it.

Final Checklist

• [X] 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.
• [X] I can reproduce this problem consistently by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.
• [X] 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.

[Kyramesh]

Examples of the filtered storage busses: (quicklime later added here to fix the problem)

[hiroscho]

Oh hell yeah, here comes the bug report where I get a headache trying to fix my mess.

The extract filtering has two slightly different behaviors:

1. Get all available items
2. Get a single item

The first case is a dumb implementation that just gets all available items from the connected network and then filters them, this one is the problem. The second one doesn't have this problem since it checks the filter first and only then checks the connected network.

The reason why the problem exists is that AE2 has recursion protection, meaning the same network will not be checked twice. In this case the first storage bus gets all available items and filters them, this is fine. However the second storage bus when trying to get all available items will notice that the network was already scanned once and skip the scan.