•  

Comment Results

Review Name Created Custom Fields Content
DG-DEN-15265-1 04 May 2023

name is idleState (not state).

DG-DEN-15265-1 04 May 2023

RESOLVED in CODE WALKTHROUGH.

DIALIN-DEN-15199-3 05 May 2023

This is to very clearly indicate to the user that we are in an unknown state until Dialin receives the status of the test configs from firmware.

DIALIN-DEN-15199-3 05 May 2023

Done

DIALIN-DEN-15199-3 05 May 2023

This is to be identical to the enum in firmware but in a Dialin enum we cannot have two enums with one number assigned to them since the Dialin enum is an ordered dictionary so we cannot have multiple keys with one number. I removed the commented enum.

HD-DEN-15267-1 08 May 2023

Done.

HD-DEN-15199-1 02 May 2023

Remove extra blank line.

HD-DEN-15199-1 08 May 2023

RESOLVED in CODE WALKTHROUGH.

HD-DEN-15199-1 02 May 2023

Let's discuss how test config is being used in this case. It seems like it's all over the place to me.

HD-DEN-15199-1 08 May 2023

RESOLVED in CODE WALKTHROUGH.

HD-DEN-15267-1 04 May 2023

Remove extra blank line.

HD-DEN-15199-1 09 May 2023

RESOLVED in CODE WALKTHROUGH.

HD-DEN-15199-1 08 May 2023

Is this needed? Why would a worn cartridge fail pressure test?

HD-DEN-15199-1 09 May 2023

RESOLVED in CODE WALKTHROUGH.

DIALIN-DEN-15199-3 02 May 2023

Why commented out and why setting to a DG test config?

HD-DEN-15199-1 09 May 2023

Done

HD-DEN-15199-1 09 May 2023

Done

DIALIN-DEN-15199-3 02 May 2023

Why 0xFFFFFFFF?

DIALIN-DEN-15199-3 09 May 2023

RESOLVED.

DG-DEN-15246-1 11 May 2023

Done

DG-DEN-15246-1 11 May 2023

Done

DG-DEN-15246-1 02 May 2023

Update header.

HD-DEN-15196-2 15 May 2023

Fixed. Thanks!

DG-DEN-15246-1 11 May 2023

RESOLVED in CODE WALKTHROUGH.

DG-DEN-15246-1 04 May 2023

Add blank line before return statement.

DG-DEN-15246-1 11 May 2023

RESOLVED in CODE WALKTHROUGH.

DG-DEN-15246-1 11 May 2023

Done

DG-DEN-15246-1 04 May 2023

This looks like 104.

HD-DEN-15274-1 11 May 2023

Add comment

LEAHI-APPLICATION-LDT-1616-1 17 Sep 2025

Related comment.

TBDL: Let's discuss more later.

HD-DEN-15199-1 08 May 2023

This was a mistake. I fixed it.

DIALIN-DEN-15199-3 09 May 2023

RESOLVED.

HD-DEN-15199-1 08 May 2023

I don't think a worn cartridge should fail here (should still be dry). I think only wet cartridge should be checked here.

HD-DEN-15199-1 09 May 2023

RESOLVED in CODE WALKTHROUGH.

DG-DEN-15246-1 11 May 2023

RESOLVED in CODE WALKTHROUGH.

HD-DEN-16782-1 02 Apr 2024

Done.

UI-DEN-16657-5 04 Apr 2024

RESOLVED
will be closed.

HD-DEN-15104-1 12 May 2023

Added space. I modified slightly, Since this is called outside of the interrupt where the sci2FEOEError is being set I believe it should get the value and only reset it if was TRUE.

HD-DEN-16782-1 02 Apr 2024

There is already a function similar to this in pre-treatment mode module. Do we need both?

HD-DEN-15104-1 12 May 2023

Corrected

HD-DEN-15104-1 12 May 2023

RESOLVED in CODE WALKTHROUGH.

HD-DEN-15274-1 12 May 2023

If res 1 is active, you will not set rsrvrCmd to anything but you are still sending command below.

HD-DEN-16851-1 01 May 2024

Change to "bldPumpOcclusionLongFilter".

CLOUDSYNC-DEN-16690-1 09 Apr 2024

Split will have a value in index 0 as long as the subprocess call is successful. If the subprocess is not successful, the exception will be caught in the message handler and CS will report an error.

CLOUDSYNC-DEN-16690-1 09 Apr 2024

fixed. thanks!

CLOUDSYNC-DEN-16690-1 09 Apr 2024

RESOLVED.

CLOUDSYNC-DEN-16690-1 28 Mar 2024

has it been checked if the parameters[0] passed/exists/none-zero?

HD-DEN-16851-1 02 May 2024

Done.

CLOUDSYNC-DEN-16690-1 09 Apr 2024

The exception handling was redundant since the message handler will catch it in ui_cs_request_handler.py and log it as CS_LOG_ROTATION_ERROR.

Added check for split() length and if it fails, it'll write to the gutils logger that the subprocess call failed in the chance that subprocess.check_output succeeds but doesn't not contain any data.

CLOUDSYNC-DEN-16690-1 09 Apr 2024

a catchall exception is not a good idea, please separate the split() and [0], and first check the index exists, the use it.
it is good to keep it if the process fails, but incorrect/unexpected result is not being caught.