Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
- Added new enums - Renamed some members - Added missing _str_lists - Adjusted code for renaming

  1. … 9 more files in changeset.
removed commented out line

We will need to get the event_id first, to know how to process the content as Operation status content is different from rest. So this line is just for getting the event id, and based on the resul...

We will need to get the event_id first, to know how to process the content as Operation status content is different from rest.

So this line is just for getting the event id, and based on the result, process the rest into the correct variables

removed

removed

fixed

fixed

remove if we are sure about the message ID

remove if we are sure about the message ID

Will we need this after adding the below code?

Will we need this after adding the below code?

Fix typo

Fix typo

fixed operation status event processing

  1. … 2 more files in changeset.
fix td event

LEAHI-DIALIN-LDT-5482_[Dry Self Test] Update the module to match the current dev changes
LEAHI-DIALIN-LDT-5482_[Dry Self Test] Update the module to match the current dev changes
- Updated pre treatment - Added patient connect command

  1. … 1 more file in changeset.
LEAHI-DIALIN-LDT-5205_[DD] Update NVM records architecture in Dialin
LEAHI-DIALIN-LDT-5205_[DD] Update NVM records architecture in Dialin
Merge branch 'LDT-5152-handler_refactor' into staging

  1. … 4 more files in changeset.
I think that's what is usually shown, the first 7 char, but in this case it might have been a typo

I think that's what is usually shown, the first 7 char, but in this case it might have been a typo

Was it a regulatory requirement before to have 7 characters from commit ID or something we implemented?

Was it a regulatory requirement before to have 7 characters from commit ID or something we implemented?

No need, in a different CR I have a module that pulls the Alarm ID, Reject Reason and Msg Ids directly from the FW. After that's merged, this file won't be needed any more manual update. For more ...

No need, in a different CR I have a module that pulls the Alarm ID, Reject Reason and Msg Ids directly from the FW. After that's merged, this file won't be needed any more manual update.

For more information check LDT-5205 CR, file: utils\ enum_updater.py

fixing msg ids and enums

  1. … 4 more files in changeset.
In FW we pre-populated Alarm IDs up to 300 to help with the reservation process. Would this also benefit dialin if we reserve up to 300?

In FW we pre-populated Alarm IDs up to 300 to help with the reservation process. Would this also benefit dialin if we reserve up to 300?

Wrong MsgID Update the entity name too

Wrong MsgID
Update the entity name too

Wrong MsgID Update the entity name too

Wrong MsgID
Update the entity name too

Update header

Update header

Update header

Update header

.name Use the name as key, to match the above suggested changes

.name

Use the name as key, to match the above suggested changes

.name Use the name instead of the full enum for key

.name
Use the name instead of the full enum for key

import from msg_ids, because the enum located there not in msg_defs

import from msg_ids, because the enum located there not in msg_defs