Skip to content
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.

Sign up for GitHub

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

Jump to bottom

mbed dm init without API key gives out ugly backtrace, it would be better to handle the exception #845

Closed
teetak01 opened this issue Feb 13, 2019 · 3 comments
Closed

mbed dm init without API key gives out ugly backtrace, it would be better to handle the exception #845

teetak01 opened this issue Feb 13, 2019 · 3 comments
Labels
bug Jira status: CLOSED mirrored

Comments

@teetak01
Copy link

Currently if I run "mbed dm init ..." without any API-key defined, it gives quite long backtrace from cloud-sdk which can be confusing to understand.

It would be more clear to catch this Exception and point to either use "-a" flag to provide the API-key, or define CLOUD_SDK_API_KEY parameter.
@screamerbg screamerbg added the bug label Feb 13, 2019
@bridadan
Copy link
Contributor

bridadan commented Feb 13, 2019 •
edited

Hi @teetak01, I'm currently fixing this in an mbed-os PR: ARMmbed/mbed-os#9635

@ciarmcom
Copy link
Member

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-866

@cmonr
Copy link
Contributor

cmonr commented Feb 15, 2019

@teetak01 Mind retesting with master? It just came in :)

@ciarmcom ciarmcom closed this as completed Apr 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Jira status: CLOSED mirrored
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@cmonr @bridadan @screamerbg @ciarmcom @teetak01