You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 8, 2022. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
jcooklin
added a commit
to jcooklin/snap
that referenced
this issue
Jun 11, 2016
…cause a panic (intelsdi-x#989)
* Fixesintelsdi-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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: