Possibly due to an API change, the settings container cannot be resolved automatically in the monitor setup. We have to use container.resolve(:settings) to grab it. This was not the case before. We should look into updating this in one way or another.
Possibly due to an API change, the
settingscontainer cannot be resolved automatically in the monitor setup. We have to usecontainer.resolve(:settings)to grab it. This was not the case before. We should look into updating this in one way or another.