Skip to content

[Bug] device forward's blocking behaviour is on the website but missing from --help and the bundled docs #109

Description

@informramiz

Summary

device forward prints Listening on 127.0.0.1:5555. and then occupies the terminal for the lifetime of the forward. An agent that runs it as a normal command and waits for it to return will wait until something else stops it.

The website does say this, in a note under the argument list:

"The port forward remains active until the CLI session or the forward process ends. The local port stays occupied while the forward process is running — stop the forward process to release it."

That is the sentence that makes the behaviour legible. It never reached us, because the two places an agent actually looks do not carry it.

What --help gives, and what it leaves out

kobiton device forward --help gives the address format (Addresses format: tcp:port), the usage line, and a description of each argument. It does not carry the note above, the worked example, or the --mode mux|demux option — we did not know --mode existed until we read the website. The plugin's bundled documentation does not carry the note either.

Why it matters

Nothing in the command's own help text distinguishes it from adb forward, which returns immediately. A command that prints one line and then does not return is indistinguishable, from the caller's side, from one that has stalled — and an unattended agent has only --help to tell it which this is.

Ask

Bring device forward's --help and the plugin's bundled docs up to the website's level: the blocking note, the example, and --mode. One clause in --helpthis command runs in the foreground until interrupted — is enough.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions