search

brackets-archive / bracketsIssues

Archive of issues in brackets.
0 stars 0 forks source link

Brackets shouldn't launch with the debugging enabled for the same port twice and incorrect infobar shown on second launch. #14622

Open core-ai-bot opened 3 years ago

core-ai-bot commented 3 years ago

Issue by abgowda Friday Nov 29, 2019 at 12:57 GMT Originally opened as https://github.com/adobe/brackets/issues/14988

1.Launch Brackets 1.14.1 from the terminal/Cmd line with the port number.

  1. Again launch Brackets 1.14.1 from the terminal/Cmd line with the same port number.

Expected: Brackets shouldn't launch with the remote debugging enabled for the same port number for which the Brackets was launched first.

Actual behavior: Brackets launches with the debugging enabled for the same port number and incorrect info bar displayed.

Brackets 1.14.1-17752 Platforms: Win /Mac /Ubuntu

Incorrect info bar on second launch

terminal message on launcnhing brackets with same port

@yprasad1@narayani28@jha-g

core-ai-bot commented 3 years ago

Comment by nayankankariya Monday Dec 02, 2019 at 09:33 GMT

Scenario 2: Same behavior is encountered if a port is blocked and trying to launch Brackets with remote debugging enabled with the blocked port.

Steps:

  1. Block port 1234 by executing the below command: (sudo pfctl -sr 2>/dev/null; echo "block drop quick on lo0 proto tcp from any to any port = 1234") | sudo pfctl -e -f - 2>/dev/null

  2. Launch Brackets with remote debugging enabled on port 1234.

Expected behavior : Brackets shouldn't notify that remote debugging is enabled for the blocked port.

Actual behavior: Brackets launches with incorrect info bar displayed.

Note: http://localhost:1234 does not load the content in the browser