Services

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
undoing DG messaging for door switches

Remove extra blank line. And why is there any blank line here?

Remove extra blank line. And why is there any blank line here?

Seems like we're setting a start time offset here, not a time stamp.

Seems like we're setting a start time offset here, not a time stamp.

Should be rpmAlarmStartTime

Should be rpmAlarmStartTime

Did we want this offset to revert to zero here or should Dialin have to do a reset?

Did we want this offset to revert to zero here or should Dialin have to do a reset?

I don't think this results in an elapsed time. It's just a different start time. The calcTimeSince below gives you the elapsed time.

I don't think this results in an elapsed time. It's just a different start time. The calcTimeSince below gives you the elapsed time.

DEN-12845 resolved merge conflicts during cherry picking process

  1. … 4 more files in changeset.
DEN-12224 updated the messages

Should we set this flag only if we are in normal state?

Should we set this flag only if we are in normal state?

Remove extra blank line.

Remove extra blank line.

Should this be set to FALSE?

Should this be set to FALSE?

"reset" should be "rest" I think.

"reset" should be "rest" I think.

Agree. Dara, make these look something like "C_CALIBRATION_CMD".

Agree. Dara, make these look something like "C_CALIBRATION_CMD".

We will want to tighten these eventually.

We will want to tighten these eventually.

It is used on lines 302, 1172, 1795, 1875.

It is used on lines 302, 1172, 1795, 1875.

We want release s/w to be fully enabled with no special test code. SW configs are structured such that a disabled config is what is wanted for release s/w and so forcing all s/w configs to be disab...

We want release s/w to be fully enabled with no special test code. SW configs are structured such that a disabled config is what is wanted for release s/w and so forcing all s/w configs to be disabled in a release build ensures we don't accidentally leave a config in the wrong state.

NoDRcr should be FALSE.

NoDRcr should be FALSE.

NoBRcr should be TRUE and NoDRcr should be FALSE.

NoBRcr should be TRUE and NoDRcr should be FALSE.

Do we need this state?

Do we need this state?

For all DG faults, the NoRes should be TRUE, but the NoRin and NoEnd should be FALSE so user can perform rinseback and/or end treatment.

For all DG faults, the NoRes should be TRUE, but the NoRin and NoEnd should be FALSE so user can perform rinseback and/or end treatment.

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

  1. … 6 more files in changeset.
RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

One letter enums could be more descriptive with their names.

One letter enums could be more descriptive with their names.