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

wge100, did not get timestamp message should not only be debug #7

Open
wjwwood opened this issue Jan 7, 2013 · 0 comments
Open

wge100, did not get timestamp message should not only be debug #7

wjwwood opened this issue Jan 7, 2013 · 0 comments
Labels
bug

Comments

@wjwwood
Copy link
Member

wjwwood commented Jan 7, 2013

Opened 2 years ago
Last modified 12 months ago

Reported by: blaise
Owned by: blaise

Description:

Currently this is only seen with debugging on. Very misleading...

[DEBUG] [1284765338.042548750]: TriggerMatcher did not get timestamp for frame #24

Change History:

Changed 2 years ago by blaise

This message needs to be prioritized without resulting in spewage.

Changed 12 months ago by joq

component changed from camera_drivers to wge100_driver
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@wjwwood