Uploaded image for project: 'Forge'
  1. Forge
  2. FORGE-1012

Forge occassionally requires an additional keystroke to be terminated

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 1.3.3.Final
    • Fix Version/s: 1.4.0.Final
    • Component/s: UI - Shell
    • Labels:
      None

      Description

      This is related to the behavior described in FORGE-593. In that bug, a keystroke consumed by Forge was lost due to the blocking thread. The bugfix for that issue did not involve any fixes around the blocking read on System.in.

      Hence, the reader thread continues to block when reading System.in, thus requiring users to send another keystroke (again to be consumed by the blocking reader) on exiting Forge (since the reader operates in a non-daemon thread).

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                vineet.reynolds Vineet Reynolds
                Reporter:
                vineet.reynolds Vineet Reynolds
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: