-
Notifications
You must be signed in to change notification settings - Fork 579
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.
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
[dev.icinga.com #8002] typeof() seems to return null for arrays and dictionaries #2380
Comments
Updated by tobiasvdk on 2014-12-05 08:11:29 00:00 Also happens with git commit 795b5b8 |
Updated by gbeutner on 2014-12-05 09:15:19 00:00
Probably a problem with operator precedence (in vs. &&). |
Updated by gbeutner on 2014-12-05 14:02:30 00:00
|
Updated by gbeutner on 2014-12-05 14:04:10 00:00 typeof() seems to return null for arrays and dictionaries:
|
Updated by tobiasvdk on 2014-12-05 14:46:22 00:00 gunnarbeutner wrote:
|
Updated by gbeutner on 2014-12-05 15:01:29 00:00
|
Updated by gbeutner on 2014-12-05 15:02:02 00:00 Nope, this has nothing to do with Boost. The problem is that GetReflectionType() returns NULL for certain built-in Icinga types. |
Updated by gbeutner on 2014-12-05 15:06:29 00:00 This is fixed in the validator branch. |
Updated by gbeutner on 2014-12-08 07:37:04 00:00
Applied in changeset 04ca634. |
Updated by gbeutner on 2014-12-10 09:19:07 00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/8002
Created by tobiasvdk on 2014-12-05 07:05:29 00:00
Assignee: gbeutner
Status: Resolved (closed on 2014-12-08 07:37:04 00:00)
Target Version: 2.2.2
Last Update: 2014-12-10 09:19:07 00:00 (in Redmine)
The assign conditions are not checked successively, e.g. if you have object vars which can be an array or a dictionary.
Simple Host config:
Simple Service config:
The error:
Using icinga 2.2.1 from debian unstable on debian wheezy.
Changesets
2014-12-08 07:36:03 00:00 by gbeutner 04ca634
2014-12-08 07:36:47 00:00 by gbeutner e3673bf
2014-12-08 10:03:50 00:00 by gbeutner 37ffda1
The text was updated successfully, but these errors were encountered: