[2.0.20] script equipment grid ghost interactions/removal can create a lingering item request

[Quezler]

steps to reproduce:

- load world with mods (reproducible without the platform construction mod too)
- place a linked/infinity chest and put each of your 3 tiers of personal battery away
- head into remote view
- place a (tier 3) battery as shown on the picture
- confirm personal roboport is on and that there is a missing item request
- board the train and drive over the landmine
- notice the battery ghost is now gone from the grid, yet the alert remains

it is potentially caused by a removal proxy being created (first) by the equipment train stop mod, since this in a fresh world does not cause the issue:
/c game.player.selected.grid.order_removal(game.player.selected.grid.equipment[1])

regardless, that it is able to get into this state is a bug, possibly can crash during prototype changed validity checks and such

[Rseding91]

Can you reproduce this in the latest version? (2.0.32 or later)

Also, do you have exact steps to reproduce the issue from scratch?

[Quezler]

During the process of trying to reproduce it i found an instance of lingering requests, not sure if its "exactly the same one", but reproducible nonetheless:

- install kry-vehicle-grids_2.1.15 (+ kry_stdlib_2.0.1)
- new world
- place enough rails for a locomotive
- /c battery = game.player.selected.grid.put{name = "battery-equipment", ghost = true}
- /c battery = game.player.selected.grid.put{name = "battery-equipment", ghost = true}
- notice 2 requests
- remove the 1 ghost from the locomotive grid
- notice 1 request still remains, without a ghost

[Quezler]

The save itself also seems to still cause the initial glitch even in .33, additionally there might be a migration issue in general related to grids stored in items:

[Rseding91]

Thanks for the report. This is now fixed for 2.0.42.