test_config_defs.py

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Updated

Updated

Does this string need to change as well?

Does this string need to change as well?

- Updated test configs - Updated valves

  1. … 2 more files in changeset.
LEAHI-DIALIN-LDT-3344_Firmware support for Beta 2 FPGA updates.
LEAHI-DIALIN-LDT-3344_Firmware support for Beta 2 FPGA updates.
merged staging into dry bicart branch and code is pushed

merged staging into dry bicart branch and code is pushed

New code pushed

New code pushed

Merging branch staging into LDT-2004-dry-bicart---dd

  1. … 3 more files in changeset.
Could you update all the overrides to use the generic method? So we don't need to maintain these on more than one place Broadcast -> cmd_generic_broadcast_interval_override others -> cmd_generic_ov...

Could you update all the overrides to use the generic method? So we don't need to maintain these on more than one place
Broadcast -> cmd_generic_broadcast_interval_override
others -> cmd_generic_override

You can check any of the other modules how to use them

This is not the code that is currently on staging, so I think you need to update it from there

This is not the code that is currently on staging, so I think you need to update it from there

fixed it

fixed it

LDT-2004 implementing code review comments + test config for drybicart initial fill test in pre-gen

  1. … 1 more file in changeset.
This is a change from Zoltan and I am updated that into my local branch

This is a change from Zoltan and I am updated that into my local branch

testconfig fix

  1. … 2 more files in changeset.
Merge branch 'LDT-3350-add_from_str' into staging

  1. … 1 more file in changeset.
for Dry Bicart , I have reserved the message ID long time back as 0x70 and its correct. I was confused after staging branch merged with my local branch, since all of my other message ID are used by...

for Dry Bicart , I have reserved the message ID long time back as 0x70 and its correct. I was confused after staging branch merged with my local branch, since all of my other message ID are used by other modules except BICART_DATA. please dis regard this question.

This is a merge issue. when I updated the code and aligned to staging , this all change happened. Need to check with Dara

This is a merge issue. when I updated the code and aligned to staging , this all change happened. Need to check with Dara

Add a blank line between functions.

Add a blank line between functions.

Is this staying? Is all of above replacing this class?

Is this staying? Is all of above replacing this class?

We agreed to change back the enums into the static variation. Why would that cover a class that has been implemented to mask the enums from direct access, so if they need to be changed to dynamic o...

We agreed to change back the enums into the static variation.
Why would that cover a class that has been implemented to mask the enums from direct access, so if they need to be changed to dynamic or renamed or anything, the other repositories that are using them through this class won't be affected or need any update.