Skip to content

Serial monitor in Arduino IDE v. 2.0.0-rc4 doesn't pad timestamps correctly #905

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
colde opened this issue Mar 11, 2022 · 2 comments
Closed
Assignees
Labels
conclusion: duplicate Has already been submitted topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project

Comments

@colde
Copy link

colde commented Mar 11, 2022

Describe the bug
When enabling timestamps in the serial monitor, timestamps might be formatted as 18:2:13.521 instead of as expected 18:02:13.521

I.e. this is the data i got in my console:

17:56:13.570 -> New message received
17:58:24.586 -> New message received
18:0:14.054 -> New message received
18:2:13.521 -> New message received
18:2:18.212 -> New message received

To Reproduce
Steps to reproduce the behavior:

  1. Have a board connected that outputs serial data
  2. Enable the serial monitor timestamp feature
  3. Wait for a time where between 0 and 9 minutes past the hour
  4. See error

Expected behavior
The timestamps should prepend a 0 for single digit minutes

Desktop (please complete the following information):

  • OS: macOS Monterey 12.2.1
  • Version: 2.0.0-rc4
@colde colde added the type: imperfection Perceived defect in any part of project label Mar 11, 2022
@per1234
Copy link
Contributor

per1234 commented Mar 11, 2022

Hi @colde. Thanks for taking the time to submit an issue.

I see we have another report about this at #580.

It is best to have only a single issue per subject so we can consolidate all relevant discussion to one place, so I'll go ahead and close this in favor of the other.

If you end up with additional information to share, feel free to comment in the other thread.

@per1234 per1234 closed this as completed Mar 11, 2022
@per1234 per1234 self-assigned this Mar 11, 2022
@per1234 per1234 added conclusion: duplicate Has already been submitted topic: code Related to content of the project itself labels Mar 11, 2022
@colde
Copy link
Author

colde commented Mar 12, 2022

Apologies. My search didn't find that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conclusion: duplicate Has already been submitted topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project
Projects
None yet
Development

No branches or pull requests

2 participants