Briefly describe changes proposed in this pull request:
Fix how TEMPO messages are decoded
Crossing T's and dotting I's
Please follow these checklists to help prevent any unexpected issues from being introduced by the changes in this pull request. If an item does not apply then indicate so by surrounding the line item with ~~ to strikethrough the text. See basic writing and formatting syntax for more information.
I. Web service and data model checklist
Please follow these checks if any changes were made to any classes in the web, service, or persistence layers.
Code checks:- [ ] Endpoints were tested to ensure their integrity.- [ ] Screenshots have been provided to demonstrate changes made to the response body JSON schema and/or swagger page.- [ ] Unit tests were updated in relation to updates to the mocked test data.
II. Neo4j models and database schema checklist:
- [ ] Neo4j persistence models were changed.- [ ] The graph database produces the expected changes to models, relationships, and/or property names. [provide screenshot of updated elements in graph db below]
III. Message handlers checklist:
- [ ] Changes in this PR affect the workflow of incoming messages.
[x] Messages are following the expected workflow when published to the topic(s) changed or introduced in this pull request.
- [ ] Unit tests were added to ensure messages are handled as expected.
If no unit tests were updated or added, then please explain why: n/a
Please describe how the workflow and messaging was tested/simulated:
Describe your testing environment:
NATS [local, local docker, dev server, production]
Neo4j [local, local docker, dev server, production]
SMILE Server [local, local docker, dev server, production]
Other: TEMPO team published with their python client
IV. Configuration and/or permissions checklist:
- [ ] New topics were introduced.- [ ] The topics and appropriate permissions were updated in smile-configuration.- [ ] If applicable, a new account was set up and the account credentials and keys are checked into smile-configuration.- [ ] Account credentials and keys were shared with the appropriate parties.
General checklist:
[ ] All requested changes and comments have been resolved.
[ ] The commit log is comprehensible. It follows 7 rules of great commit messages. For most PRs a single commit should suffice, in some cases multiple topical commits can be useful. During review it is ok to see tiny commits (e.g. Fix reviewer comments), but right before the code gets merged to master or rc branch, any such commits should be squashed since they are useless to the other developers. Definitely avoid merge commits, use rebase instead.
TEMPO message handler patch
Briefly describe changes proposed in this pull request:
Crossing T's and dotting I's
Please follow these checklists to help prevent any unexpected issues from being introduced by the changes in this pull request. If an item does not apply then indicate so by surrounding the line item with
~~to strikethrough the text. See basic writing and formatting syntax for more information.I. Web service and data model checklist
Please follow these checks if any changes were made to any classes in the web, service, or persistence layers.
Code checks:
- [ ] Endpoints were tested to ensure their integrity.- [ ] Screenshots have been provided to demonstrate changes made to the response body JSON schema and/or swagger page.- [ ] Unit tests were updated in relation to updates to the mocked test data.II. Neo4j models and database schema checklist:
- [ ] Neo4j persistence models were changed.- [ ] The graph database produces the expected changes to models, relationships, and/or property names. [provide screenshot of updated elements in graph db below]III. Message handlers checklist:
- [ ] Changes in this PR affect the workflow of incoming messages.- [ ] Unit tests were added to ensure messages are handled as expected.If no unit tests were updated or added, then please explain why: n/a
Please describe how the workflow and messaging was tested/simulated:
Describe your testing environment:
Other: TEMPO team published with their python client
IV. Configuration and/or permissions checklist:
- [ ] New topics were introduced.- [ ] The topics and appropriate permissions were updated in smile-configuration.- [ ] If applicable, a new account was set up and the account credentials and keys are checked into smile-configuration.- [ ] Account credentials and keys were shared with the appropriate parties.General checklist: