| 2016-01-21 18:45:40 |
Mark Sturdevant |
description |
For a share type extra-spec to match a Boolean capability (using CapabilitiesFilter), the current design requires the extra-spec value to use the syntax '<is> True' instead of just True or 'True'. When normal humans but True in there, they will find a logged message from the scheduler saying True is not equal True. This is because there is a mismatch between the the extra-spec value (string) and the actual boolean reported.
The scheduler filter should be made to recognize how to match a Boolean with a boolean-like string so that the awkward <is> syntax is not needed. |
For a share type extra-spec to match a Boolean capability (using CapabilitiesFilter), the current design requires the extra-spec value to use the syntax '<is> True' instead of just True or 'True'. When normal humans put True in there, they will find a logged message from the scheduler saying True is not equal True. This is because there is a mismatch between the the extra-spec value (string) and the actual boolean reported.
The scheduler filter should be made to recognize how to match a Boolean with a boolean-like string so that the awkward <is> syntax is not needed. |
|
