jotomo/AndroidAPS#29 Don't raise alarm on 'double cancellation'.

This commit is contained in:
Johannes Mockenhaupt 2017-07-22 11:36:52 +02:00
parent 3480cc5441
commit fcd6f4ea0e
No known key found for this signature in database
GPG key ID: 9E1EA6AF7BBBB0D1

View file

@ -35,10 +35,11 @@ public class CancelTbrCommand implements Command {
MainApp.getConfigBuilder().getTempBasalFromHistory(System.currentTimeMillis() - 30 * 1000)); MainApp.getConfigBuilder().getTempBasalFromHistory(System.currentTimeMillis() - 30 * 1000));
log.debug("active temp basal now:: " + log.debug("active temp basal now:: " +
MainApp.getConfigBuilder().getTempBasalFromHistory(System.currentTimeMillis())); MainApp.getConfigBuilder().getTempBasalFromHistory(System.currentTimeMillis()));
// TODO keep checking logs to ensure this case only happens because CancelTbrCommand was called
// twice by AAPS
log.warn("No TBR active to cancel"); log.warn("No TBR active to cancel");
return new CommandResult() return new CommandResult()
// Raise a warning about this, until we know it's safe to ignore. .success(true)
.success(false)
// Technically, nothing was enacted, but AAPS needs this to recover // Technically, nothing was enacted, but AAPS needs this to recover
// when there was an issue and AAPS thinks a TBR is still active, // when there was an issue and AAPS thinks a TBR is still active,
// so the ComboPlugin can create a TempporaryBasel to mark the TBR // so the ComboPlugin can create a TempporaryBasel to mark the TBR