Skip to content

we need some feedback that the observatory is up and available to connect to #42

Closed

Description

@abarth

From https://github.com/flutter/tools/issues/110

The CLI VM prints out Observatory listening on http://127.0.0.1:8989 when run w/ the observatory enabled. Perhaps the flutter runtime should to the same?

It looks like the VM doesn't print on startup if you use the default port of 8181. And parsing stdout for a token isn't the most reliable way of doing things.

We could change the flutter start command to not return until the process is up and running on android. Then we'd know, when that completes, that the observatory is ready to connect to.

Activity

  1. added
    toolAffects the "flutter" command-line tool. See also t: labels.
    on Nov 7, 2015
  2. sethladd commented on Dec 8, 2015

    @sethladd
    Contributor

    cc @devoncarew still needed?

  3. devoncarew commented on Dec 9, 2015

    @devoncarew
    Contributor

    Yup -

  4. added this to the milestone on Dec 12, 2015
  5. eseidelGoogle commented on May 13, 2016

    @eseidelGoogle
    Contributor

    We print this now.

  6. github-actions commented on Aug 17, 2021

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  7. locked as resolved and limited conversation to collaborators on Aug 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    c: new featureNothing broken; request for a new capabilitytoolAffects the "flutter" command-line tool. See also t: labels.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions