Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'LDT-5205-dd_nvm_update' into staging

  1. … 8 more files in changeset.
No, it won't cause an error. The execute() function checks for the leahi-common folder existence first, if it does not exists, it returns, skipping the whole update process. Not everyone have acces...

No, it won't cause an error. The execute() function checks for the leahi-common folder existence first, if it does not exists, it returns, skipping the whole update process.
Not everyone have access to that folder and a whl file don't need to run the update every time, it's more like for those who develop the code.

Also if it's not at the very beginning, the enums will be processed in the next imports, and updating them afterwards is meaningless as it won't reflect in the running code. The files needs to be updated before any other object tries to call them to make an instance.

This will be called when a user imports leahi-dialin, right? ( import leahi-dialin ) and thus cause a traceback cause the user wont have the path to the header files required for this execute call....

This will be called when a user imports leahi-dialin, right? ( import leahi-dialin ) and thus cause a traceback cause the user wont have the path to the header files required for this execute call.

suggest keeping the call in if _name_ == '_main_': of enum_update and running that

LEAHI-DIALIN-LDT-5615_[Dialin] Update Priming related data for auto-priming service
LEAHI-DIALIN-LDT-5615_[Dialin] Update Priming related data for auto-priming service
- Added new enums - Renamed some members - Added missing _str_lists - Adjusted code for renaming

  1. … 9 more files in changeset.
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

typo fix

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

  1. … 1 more file in changeset.
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
fixed td records import

LEAHI-DIALIN-LDT-5205_[DD] Update NVM records architecture in Dialin
LEAHI-DIALIN-LDT-5205_[DD] Update NVM records architecture in Dialin
Updated TD records fields

    • -0
    • +76
    ./records_get_requests.py
    • -0
    • +100
    ./records_get_responses.py
    • -0
    • +111
    ./records_set_requests.py
    • -0
    • +96
    ./records_set_responses.py
  1. … 1 more file in changeset.
Merge branch 'staging' into LDT-5205-dd_nvm_update

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

- Fixed cond sensor fp indexing - Fixed UI initate treatment params

  1. … 2 more files in changeset.