Skip to content

Board and port selected always shows with warning icon #200

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
toogooda opened this issue Mar 10, 2021 · 11 comments
Closed

Board and port selected always shows with warning icon #200

toogooda opened this issue Mar 10, 2021 · 11 comments
Assignees
Labels
conclusion: resolved Issue was resolved criticality: low Of low impact topic: code Related to content of the project itself type: enhancement Proposed improvement

Comments

@toogooda
Copy link

Describe the bug
Every board I select always shows with a warning icon next to it, even though upload works and so does output.

To Reproduce
Steps to reproduce the behavior:

  1. Select any valid board and com port
  2. See warning icon

Expected behavior
No idea as there is nothing to tell you what it is for, it shows a red 'x' when nothing is connected so I assume a green icon or nothing when a arduino is connected.

Screenshots
warning

Desktop (please complete the following information):

  • OS: Windows
  • Version: 10

Additional context
I wasted time trying to work out what I had wrong because the warning icon indicated a potential issue.
Tried on multiple Arduino compatible devices.

@kittaakos kittaakos added the conclusion: invalid Issue/PR not valid label Mar 11, 2021
@kittaakos
Copy link
Contributor

Thanks for reporting, @toogooda. It's the expected behavior. You can see here how it works. In a nutshell: if the Arduino CLI cannot recognize your board, no fqbn is available via the board list command, you will see a warning.

This is the CLI's output when I have attached a MKR1000 and ESP8266 board. You can see the details for the ESP8266 is not available.

./arduino-cli board list --format json
[
  {
    "address": "/dev/cu.URT2",
    "protocol": "serial",
    "protocol_label": "Serial Port"
  },
  {
    "address": "/dev/cu.URT1",
    "protocol": "serial",
    "protocol_label": "Serial Port"
  },
  {
    "address": "/dev/cu.Bluetooth-Incoming-Port",
    "protocol": "serial",
    "protocol_label": "Serial Port"
  },
  {
    "address": "/dev/cu.usbserial-0001",
    "protocol": "serial",
    "protocol_label": "Serial Port (USB)"
  },
  {
    "address": "/dev/cu.usbmodem14401",
    "protocol": "serial",
    "protocol_label": "Serial Port (USB)",
    "boards": [
      {
        "name": "Arduino MKR1000",
        "FQBN": "arduino:samd:mkr1000",
        "VID": "0x2341",
        "PID": "0x804E"
      }
    ]
  }
]

I am closing as invalid. Let me know if you disagree, @toogooda. I am happy to discuss it further. Thanks!

@toogooda
Copy link
Author

Hi kittaakos,
Thanks for your explination. by far the majority of clones will use the CH340G/C which will not return a FQBN as the chip uses a default I believe. This will just be a nag or confusing(what have I done wrong?) to everyone who uses them. Is this feature more hinderance than help?
It is helpful displaying the selected board and port, and auto populating when you can but this permanent warning seems like a step to far.
I could do a hundred successful uploads and it will still be warning me.
Can I toggle it off?

@ubidefeo
Copy link

@toogooda you are in the right.
A warning sign should be an indicator that something is wrong.

We'll look into it 👍🏼

@toogooda
Copy link
Author

@toogooda you are in the right.
A warning sign should be an indicator that something is wrong.

We'll look into it 👍🏼

Thank you

@kittaakos kittaakos reopened this Mar 12, 2021
@ckuethe
Copy link

ckuethe commented Mar 17, 2021

Can there be a way to set my preferred serial port patterns? I only ever have ttyUSB* (rarely ttyACM*) and right now ttyUSB0 is waaaaaaaaayyyyyy down at the bottom, below a bunch of ttyS* devices.

Also, I have some devices that don't even have a usb-serial on them; I just plug in the nearest 4-pin serial cable to the UART header.

@ubidefeo ubidefeo added priority: low Resolution is a low priority type: enhancement Proposed improvement and removed conclusion: invalid Issue/PR not valid type: bug labels Mar 19, 2021
@ubidefeo
Copy link

@ckuethe

Can there be a way to set my preferred serial port patterns? I only ever have ttyUSB* (rarely ttyACM*) and right now ttyUSB0 is waaaaaaaaayyyyyy down at the bottom, below a bunch of ttyS* devices.

Unfortunately cleaning up your serial ports files is up to you.
we run a serial discovery which lists every serial device on the system so if you have 50 serial ports that's what you'll get

@steveboak
Copy link

I too wasted time investigating this warning before I found this post.
I would like to propose a solution: An explanatory message pop up when the mouse is hovered over the warning icon.

@toogooda
Copy link
Author

toogooda commented Jul 21, 2021

I too wasted time investigating this warning before I found this post.
I would like to propose a solution: An explanatory message pop up when the mouse is hovered over the warning icon.

I disagree, a warning suggests a problem and there is not, and there is nothing that can be done to fix it it is just a permanent nag! Please remove it.

@moth4017
Copy link

moth4017 commented Sep 8, 2021

I agree a warning triangle is to inform of an issue.

@per1234 per1234 added the topic: code Related to content of the project itself label Oct 28, 2021
@rsora rsora added criticality: low Of low impact and removed priority: low Resolution is a low priority labels Nov 2, 2021
@ubidefeo
Copy link

ubidefeo commented Apr 5, 2022

Just an update on this issue:
we're reworking the iconography for this area of the UI and this is being addressed in the process.
This issue will remain open and be connected to our internal development backlog in order to be closed by an upcoming PR

Thank you for your patience ✌🏼

@per1234
Copy link
Contributor

per1234 commented Jul 19, 2022

Closing as fixed by #1193

@per1234 per1234 closed this as completed Jul 19, 2022
@per1234 per1234 added the conclusion: resolved Issue was resolved label Jul 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conclusion: resolved Issue was resolved criticality: low Of low impact topic: code Related to content of the project itself type: enhancement Proposed improvement
Projects
None yet
Development

No branches or pull requests

9 participants