Race condition at the end of hot code replacement causes inconsistent UI state

At the end of JavaHotCodeReplaceProvider.redefineClasses() execution JavaHotCodeReplaceProvider.stepIntoThread(ThreadReference) is called which sends JDI StepRequest to the target process and subscribes for StepEvent, on reception of which the following events for the UI are populated in that order:
context.getProtocolServer().sendEvent(new Events.StoppedEvent("step", thread.uniqueID())); context.getProtocolServer().sendEvent(new Events.ContinuedEvent(thread.uniqueID()));

However, ProtocolServer.sendEvent(DebugEvent) usually reverses this order by putting StoppedEvent to the event queue until ProtocolServer command processing (redefineClasses in this case) has completed. All other types of events are sent immediately. As JDI StepRequest is usually processed very quickly by the target process, the usual order for the VS Code UI to receive the events is ContinuedEvent > StoppedEvent. In contrast, if StepRequest processing happens to be slow then StoppedEvent is sent first and ContinuedEvent as the final one. In that case the Debug toolbar in VS Code UI will be shown like in running state with Stop button while the target process is still suspended.

從 JavaHotCodeReplaceProvider.redefineClasses() 和 stepIntoThread(ThreadReference) 開始，接著檢查 ProtocolServer.sendEvent(DebugEvent) 以及它對 StoppedEvent 和 ContinuedEvent 的處理。重現或追蹤 StepEvent 的時序，並在 VS Code UI 能夠一致反映目標程序在熱程式碼替換後處於暫停狀態時，視為該 issue 已完成。