Skip to content

Conversation

@jessebraham
Copy link
Member

Since the list of available ports were being filtered down by default, when specifying a port via CLI option or configuration file which had been filtered out, the port was reported as unavailable. This should resolve the issue by only filtering the list of ports if no port was specified.

@trombik are you able to test this branch out and confirm that it indeed resolves the issue for you, please?

Closes #692

Copy link
Member

@SergioGasquez SergioGasquez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes LGTM! Let's wait for the confirmation that it fixes the issue. Thanks!

@trombik
Copy link

trombik commented Oct 24, 2024

Confirmed that the patch fixed the issue. Tested with -p and espflash.toml.

By the way, it is always impressive how quickly espressif responds to issues and reports. Other vendors should follow the same practice.

@jessebraham
Copy link
Member Author

Thank you for confirming the fix, and for the kind words! There are still some additional small changes I'd like to make, but I hope to publish new releases next week.

@jessebraham jessebraham added this pull request to the merge queue Oct 24, 2024
Merged via the queue into esp-rs:main with commit 8db0081 Oct 24, 2024
28 checks passed
@jessebraham jessebraham deleted the fixes/specify-port branch October 25, 2024 07:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

-p option does not work as expected

3 participants