fix for issue #667

[NEC-Vishal]

Proposed changes

Resolved TODO at Line 126 of src/reporter/tests/test_timescale_types.py (#667 )

Types of changes

What types of changes does your code introduce to the project? Put an x in the boxes that apply

• [ ] Bugfix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] Maintenance (update of libraries or other dependences)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [x] I have read the CONTRIBUTING doc
• [x] I have signed the CLA
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] I have run all the existing tests locally (not just those related to my feature) and there are no errors
• [x] After the last push to the PR branch, I have run the lint script locally and there are no changes to the code base
• [x] I have updated the RELEASE NOTES
• [x] I have added necessary documentation (if appropriate)
• [x] Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

"Martel Open Source Software Individual Contributor License Agreement"

"Contributing to QuantumLeap"

"QuantumLeap Release Notes"

[github-actions[bot]]

CLA Assistant Lite bot All contributors have signed the CLA ✍️

[NEC-Vishal]

Hi @c0c0n3 can you Please check this now. I just tried to make the insert_entities same as earlier, for this I need to make change in the test function I change some expected value.

also I add a time wait in geo_queries_fixture.py as it is failing in getting the data.

[c0c0n3]

hi @NEC-Vishal, nice try, but I think the latest refactoring has more issues than the previous version...but I'm sure you've got good reasons for those changes. Can we have a call to brainstorm about this PR? Just drop me a line to schedule a meeting--- @pooja1pathak has my email address.

I think it's quicker to chat than typing here...

[NEC-Vishal]

Hi @c0c0n3 can you Please check this PR also, as discussed I have updated the PR.

[c0c0n3]

@NEC-Vishal excellent, thanks a stack!!