Skip to content
This repository has been archived by the owner on Nov 6, 2024. It is now read-only.

Improve CLI error handling #18

Open
davidg238 opened this issue Sep 6, 2021 · 0 comments
Open

Improve CLI error handling #18

davidg238 opened this issue Sep 6, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@davidg238
Copy link

I am developing a device driver and have errors in my code, possibly in the Pins designated for I2C.
If I have a print statement before I attempt to instantiate the i2c bus, I get the following on the CLI:

david (master *+) fw_keyboard $ toit device run tests/fw_display_test.toit
2021-09-06T23:08:49.612633Z: <process initiated>
2021-09-06T23:09:18.207427Z: <process initiated>
start i2c
2021-09-06T23:09:18.256972Z: <process initiated>
2021-09-06T23:09:46.503321Z: <process initiated>
start i2c
2021-09-06T23:09:46.574833Z: <process initiated>
start i2c
2021-09-06T23:09:46.685314Z: <process initiated>

If I do not have a print statement before, I get:

david (master *+) fw_keyboard $ toit device run tests/fw_display_test.toit
Cannot receive data from stream: rpc error: code = Unavailable desc = Bad Gateway: HTTP status code 502; transport: received the unexpected content-type "text/html; charset=UTF-8"
rpc error: code = Unavailable desc = Bad Gateway: HTTP status code 502; transport: received the unexpected content-type "text/html; charset=UTF-8"
david (master *+) fw_keyboard $ 

The console does show a problem, by the looping restarts.

@davidg238 davidg238 added the enhancement New feature or request label Sep 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant