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

Plugins with multiple config policy nodes may cause a panic #988

Closed
jcooklin opened this issue Jun 11, 2016 · 0 comments
Closed

Plugins with multiple config policy nodes may cause a panic #988

jcooklin opened this issue Jun 11, 2016 · 0 comments
Assignees

Comments

@jcooklin
Copy link
Collaborator

When there are multiple config policy nodes
and there exists a metric which does not fall under any of the policies
and the root node does not contain a policy

The following example causes a panic since no policies apply to /intel/abc/baz.
metric types
/intel/abc/foo
/intel/def/bar
/intel/abc/baz

config at
/intel/abc/foo
/intel/def/bar

root
/intel

jcooklin added a commit to jcooklin/snap that referenced this issue Jun 11, 2016
@tiffanyfay tiffanyfay self-assigned this Jun 13, 2016
tiffanyfay added a commit to jcooklin/snap that referenced this issue Jun 16, 2016
tiffanyfay added a commit to jcooklin/snap that referenced this issue Jun 16, 2016
tiffanyfay pushed a commit to jcooklin/snap that referenced this issue Jun 16, 2016
tiffanyfay added a commit to jcooklin/snap that referenced this issue Jun 16, 2016
IRCody pushed a commit to IRCody/snap that referenced this issue Jun 23, 2016
…cause a panic (intelsdi-x#989)

* Fixes intelsdi-x#988 - Plugins with multiple config policy nodes may cause a panic

* Test for intelsdi-x#988 - Plugins with multiple config policy nodes may cause a panic
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants