On 16.01.2014 19:06, Mark Haney wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/16/2014 12:48 PM, Michael Friedrich wrote:
Dang. You guys are on it. Nice work.
Thanks to my photographic memory. Otherwise you should've just opened an
issue. Rejecting issues marked as duplicate don't hurt anyone.
I didn't see if there was a
temporary work around for 0.0.6, not that it matters.
While the Icinga 2 releases happen on a 3 weeks schedule for our
development sprints, this is not true for holiday season. That's mainly
the reason why there isn't 0.0.7 already. But as a matter of fact you
should use the snapshot package repository, even that may sound odd.
Our development model is git flow, and features are developed in feature
branches until they're considered stable. Fixes also last a while in fix
branches, and are only merged without --no-ff *if* they are quickfixes.
In general that means that 'git next' as a base for snapshot package
builds on every push is more fixed stable than the master only
representing the last tech preview release.
I'm more
curious as to what the fix is.
Oh, the Classic UI doesn't like entries such as
define service {
...
action_url
icon_image
}
In short, it tries to interpret a null value. Core 1.x doesn't write
such values, but a recent change for Icinga 2 0.0.6 wrote custom
attributes even if their value was empty. The fix in icinga 2 git
reflects that by adding additional checks for the strings not being
empty before adding those to the file stream for objects.cache
The patch fits most likely against 0.0.6 though such fix backports will
happen once the first stable 2.0.0 is released. When development targets
2.1.0, we may still release 2.0.x bugfix releases then. Like we're
keeping several branches supported for Icinga 1.x now - support/1.10 etc
on git, where releases for older development branches are cut off.
I broke it while refactoring huge parts of the compatutility value
fetching in performance regards:
https://git.icinga.org/?p=icinga2.git;a=commit;h=66765311c31be29883ec587a5af49ed669da4824
kind regards,
Michael
--
DI (FH) Michael Friedrich
mail: michael.friedr...@gmail.com
twitter: https://twitter.com/dnsmichi
jabber: dnsmi...@jabber.ccc.de
irc: irc.freenode.net/icinga dnsmichi
icinga open source monitoring
position: lead core developer
url: https://www.icinga.org
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
