[0.17.49]Closed signal with path reserved through not reading state

[reduke]

Doesn't happen in .48, started in .49

When a train reserves a path through a signal that is subsequently closed via the circuit network before the train has finished passing, the signal stops reading it's colour state as soon as it is closed.

Prior to .49, it would keep reading it's state until the train had finished passing.

[reduke]

OK, update after more experimentation to recreate:

If a train reserves a path through but does not start passing the signal before it closes, then it will not read the change in state to red (the amber state stops being red correctly, but red doesn't start).

If the same train reserves a path through and starts (but does not finish) passing the signal before it closes, the red state is read correctly.

[kovarex]

I'm almost certain that it is related to a bug I solved for the next release.

Fixed that opening signal by circuit network could let train to go to a reserved/occupied block. (72000)

[reduke]

Unfortunately this has not been resolved in 0.17.50