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

[Capabilities] Incorrect warning logged #49

Closed
VWoeltjen opened this issue Jul 14, 2015 · 1 comment
Closed

[Capabilities] Incorrect warning logged #49

VWoeltjen opened this issue Jul 14, 2015 · 1 comment
Assignees
@VWoeltjen
Milestone
Ymir

Comments

@VWoeltjen
Copy link
Contributor

Observing No key defined for capability; skipping. frequently on console. This appears to occur when a capability has been overridden, due to a logic error in the way this condition is checked for before it is logged. (Error introduced at 71ca980)
@VWoeltjen VWoeltjen self-assigned this Sep 8, 2015
@VWoeltjen VWoeltjen added this to the Ymir milestone Sep 8, 2015
VWoeltjen added a commit that referenced this issue Sep 11, 2015
@VWoeltjen
[Capabilities] Avoid erroneous logging
f17410a 
Fix logic error which caused an inaccurate warning to
be logged when capabilities are overridden by priority.
Addresses #49.
@VWoeltjen VWoeltjen mentioned this issue Sep 11, 2015
Merged
@VWoeltjen
Copy link
Contributor Author

Verified during testathon 9/17/2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@VWoeltjen VWoeltjen

Labels
None yet
Projects
None yet
Milestone
Ymir
Development

No branches or pull requests
1 participant
@VWoeltjen