Can confirm in 24w45a.
This bug is related to this bug report too: MC-278182
It is crucial to fix this bug for proper, consistent behavior from item entities when moved by pistons
@unknown's bug solution would be valid, as explained here: MC-278255
Furthermore, powder snow can cause the same bug too (1.17+ as the block was introduced back then)
There's your mistake. The issue isn’t with the entity itself. Instead, the item is summoned and pushed by the piston. A few game ticks later, the piston block entity completes its extension. At that point, a block suddenly appears where the item entity was originally located (glass pane instantly connecting upon shape update).
As I said earlier, it is the consequence of multiple, perfectly intentional behaviors.
Items do not end up inside the collision box, but rather the block ends up where the item is (it also does not happen in gt0, but a couple gt's after). Not a bug
Additionally, it is not related to MC-278182 . One is a consequence of 2 intentional features:
Block collision when entity is moved and entity is not in `noClip`
Item entities attempting to escape when their hitbox interescts with a block with collision, through `pushOutOfBlocks()` method
The other (MC-278182 ) is a mistake from mojang developers
This is not a bug.
It is the consequence of pushing item entities into a wall/floor. When the piston attempts to move any entities (through `pushEntities` method) it will use `move()` method from `Entity.class()`. Because the entity will collide against the block on the bottom, it will fail to be pushed by the piston, glitching inside it's head.
The expected behavior is the behavior that is being reported as a bug:
Entity attempting to escape by using `pushOutOfBlocks()` method.
This is NOT a bug. It is a consequence of 2 perfectly intentional features:
glass pane connecting to adjacent blocks upon shape updated
Entities attempting to escape when their hitbox overlaps with any blocks: Entity.class method `pushOutOfBlocks`, which is used by item entities in their `tick()` method. Fixing this would be nonesense.
It is also NOT related to https://bugs.mojang.com/browse/MC-278182 , as this is not an intended feature, but rather a mistake from mojang developers
This is not a bug! Specially hoppers ignoring PickupDelay.
Fixing this would screw over the entire community in an unimaginable way. The vast majority of farm collections would break.