DIALIN-DEN-8308

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

Has been addressed in http://dvm-linux02:8060/cru/DIALIN-DEN-8514-1

Has been addressed in http://dvm-linux02:8060/cru/DIALIN-DEN-8514-1

Has been addressed in http://dvm-linux02:8060/cru/DIALIN-DEN-8514-1

Has been addressed in http://dvm-linux02:8060/cru/DIALIN-DEN-8514-1

Has been addressed in http://dvm-linux02:8060/cru/DIALIN-DEN-8514-1

Has been addressed in http://dvm-linux02:8060/cru/DIALIN-DEN-8514-1

Has been addressed in http://dvm-linux02:8060/cru/DIALIN-DEN-8514-1

Has been addressed in http://dvm-linux02:8060/cru/DIALIN-DEN-8514-1

Should indicate the return type: instead of ): it should be ) -> None:

Should indicate the return type:
instead of

): 

it should be

) -> None:
Missing the cmd_ prefix in the function name

Missing the cmd_ prefix in the function name

Missing the cmd_ prefix in the function name

Missing the cmd_ prefix in the function name

The typing information is missing for accepted and reason here

The typing information is missing for accepted and reason here

RESOLVED

RESOLVED

RESOLVED

RESOLVED

Updated regarding our conversation.

Updated regarding our conversation.

I see a couple of issues here: The message response logic has been moved out of dialin and into your UI simulator in the testsuites respository. This creates a couple of problems: First, it upends ...

I see a couple of issues here:
The message response logic has been moved out of dialin and into your UI simulator in the testsuites respository. This creates a couple of problems: First, it upends the entire design of the HD / DG simulator. Second, it splits the responsibility for simulating an HD and DG into both dialin and your UI simulator program. This means that the caller of the dialin command must know how to construct a response. If I want to use your functions to simulate a response, I can't because they don't exist here. The logic for simulating an HD and DG must be fully contained inside the HD and DG simulators so other users of the API can call it, not dispersed to outside scripts. Also, your changes appear to be on an extremely old version of dialin. These changes are incompatible with the latest changes on staging. Please merge staging into your branch.

  • A message ID must not be passed to a simulator command. This ensures there is a one to one mapping between dialin commands and messages and that dialin can do its job of abstracting messages. This is how dialin works everywhere else and should not be changed.
  • Parameters should not be pre-converted to bytearrays before being sent to dialin.
  • If you have one, two, or five parameters in a denali message, your dialin function should accept one, two, or five parameters. This ensures the payload is clearly defined and described by the number of parameters passed to the function and that the function can do its job of abstracting the denali message.
RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

I'm not aware of this function usage, but in general, some of these fields provided by HD for later use, and UI is not using them and some other has recently been used.

I'm not aware of this function usage, but in general, some of these fields provided by HD for later use, and UI is not using them and some other has recently been used.

Updated

Updated

Updated

Updated

Please use snake_case for all variables Typing information is missing for parameters Typing information is missing for the return type

Please use snake_case for all variables
Typing information is missing for parameters
Typing information is missing for the return type

Add space after comma right before hasParameters.

Add space after comma right before hasParameters.

What information is needed to replace these TBDs?

What information is needed to replace these TBDs?

DIALIN-DEN-8308_UI DEV Treatment Log
DIALIN-DEN-8308_UI DEV Treatment Log