[Copy of MC-8328] Powered mechanisms react when receiving a 0 tick redstone signal (existence of micro-pulses in general / inconsistent block update 'algorithm')

So if I understand correctly, this is an exact same issue as MC-8328, but applies to Minecraft: Pocket Edition?

Yes, exactly.
Sorry for the duplicate but I could not select "Minecraft Pocket Edition" or "Minecraft for Win10" in the list of affected versions of the original issue.
If you could add it to the list for me, you could delete this duplicate issue right here.

The bug has been discussed intensively in the comments section of the original issue (the conclusion is in the original report).

Can you give an example of a 0 tick pulse monostable for MCPE? Or what exactly did you test in MCPE that made you conclude that there are 0 tick pulses? Because the update system is as far as I can tell very much different from the PC version and I didn´t find any 0 tick technology that works in MCPE.
Edit: I found something that could be considered to be a 0 tick pulse. Ignore this.

I gave one way to replicate it in the description of MC-8328.

Please respond and add the current version if you can reproduce this issue.

Still the same. Bug not solved.

Affects 0.15.10. (Tested on Windows 10.) See comment below.

WAIT!! I WAS WRONG!

https://bugs.mojang.com/secure/attachment/105392/2015-11-22_13.56.56.png

I built this in MCPE, but what I forgot was that this test would be affected by MCPE-11871. Because of this, the test was INVALID. By moving the dispenser one block to the right and by adding another redstone dust between the dispenser and the torch, I found that the dispenser would never fire. This means that MCPE does NOT have 0 ticks! I think this issue can be closed, unless someone can find a legitimate proof of the existence of micropulses in MCPE.

Please test the bug with pistons as described in my initial report (MC-8328):
"To replicate it, OR the input of an instant NOT gate (http://youtu.be/vCsJWc7PcT0) and it's output together and attach it to another piston. Toggle the input"

@unknown That test is impossible to perform, as MCPE pistons have different timings from Java edition pistons and therefore an instant NOT gate cannot be constructed. See MCPE-15607. I am currently investigating this issue, though. There IS definitely some odd timing stuff going on with MCPE redstone, though I'm not sure 0-ticking is one of those things. Keep in mind that MCPE redstone is programmed VERY differently from the Java edition, and seemingly similar problems may be causes by very different things in each edition.

This is a bulk resolve of issues that haven't been updated to 0.16.0+ yet. Please comment below (To open the ticket) and update your affected versions. If you cannot reproduce the bug, please write in the comments so we can resolve it as "Cannot Reproduce". Thank You!

Resolving as invalid, as I can find no evidence of 0-ticking being a thing in MCPE redstone. (See my previous comment on how the example cases were invalid as they were actually being caused by a separate bug, and by using modified versions of the test which weren't affected by that bug, the supposed 0-tick behavior did NOT occur, and therefore this was never a bug to begin with.