New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 711283 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Feature

Blocking:
issue 518942



Sign in to add a comment

bluetooth: mac: Clarify logs statements and make them consistent.

Project Member Reported by fbeaufort@chromium.org, Apr 13 2017

Issue description

Logs are sometimes confusing. We should clarify them and make them consistent.

We currently have:

- "Read characteristic" when dispatching characteristic read requests.
- "Read request arrived" when successfully reading a characteristic.
- "Write characteristic" when dispatching write requests.
- "Write value succeeded" when successfully writing to a characteristic.
- "Read value." when dispatching descriptor read requests.
- "Value read." when successfully reading a descriptor.
- "Write value." when dispatching descriptor write requests.
- "Value written." when successfully writing a descriptor.




 
Components: IO>Bluetooth
My bad "Read value." and "Value read." are different but the same size hence my mistake.
May we rename "Value read" to "Did read value"?

Comment 3 by ortuno@chromium.org, Apr 17 2017

Blocking: 518942

Comment 4 by ortuno@chromium.org, Apr 17 2017

Labels: -Type-Bug Type-Feature

Comment 5 by ortuno@chromium.org, Apr 17 2017

Cc: jlebel@chromium.org
Labels: Hotlist-GoodFirstBug
Owner: ----
Status: Available (was: Untriaged)

Comment 6 by ortuno@chromium.org, Apr 17 2017

Description: Show this description

Comment 7 by ortuno@chromium.org, Apr 17 2017

Summary: bluetooth: mac: Clarify logs statements and make them consistent. (was: bluetooth: mac: Descriptors are read twice)
Project Member

Comment 8 by sheriffbot@chromium.org, Apr 18 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Owner: ortuno@chromium.org
Status: Assigned (was: Untriaged)
Mac triage:

Assigning to ortuno@ for routing.

ortuno@, if we're not likely to ever work on this, let's just WontFix it instead of leaving it hanging around.
Status: WontFix (was: Assigned)
:( I was hoping for someone to pick this up. Marking as won't fix, since we'll probably never get to it.

Sign in to add a comment