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
The default value provided for server.plugins in config.yaml is resulting in an unexpected None in some checks. While this one again brings up the idea of checking for defaults / expected values on an initial config load and warning appropriately, it's easier in the near term to make sure that if we set the value that it's valid.
The specific example where this is causing problems:
Our current server.config value
server:
plugins:
The code in GUI that is pulling this value breaks when server.plugins exists but isn't a valid form
plugins = ait.config.get('server.plugins', [])
for i in range(len(plugins)):
Removing server.plugins or setting it to an empty list fixes this problem.
The text was updated successfully, but these errors were encountered:
Issue #216 - Update server.plugins default value in config to an empty
list so it doesn't fall back to None. This prevents it from breaking
other code that checks if the value exists and falls back to a sane
default if it doesn't.
Issue #217 - Handler class path wasn't updated as part of the changes in
issue #214.
The default value provided for
server.plugins
inconfig.yaml
is resulting in an unexpected None in some checks. While this one again brings up the idea of checking for defaults / expected values on an initial config load and warning appropriately, it's easier in the near term to make sure that if we set the value that it's valid.The specific example where this is causing problems:
Our current
server.config
valueThe code in GUI that is pulling this value breaks when
server.plugins
exists but isn't a valid formRemoving
server.plugins
or setting it to an empty list fixes this problem.The text was updated successfully, but these errors were encountered: