Skip to content

Conversation

@timber-they
Copy link
Contributor

@timber-they timber-they commented Dec 4, 2025

Type of Change

  • Dependency upgrade
  • Bug fix (non-breaking change)
  • Breaking change
    • e.g. a fixed bug or new feature that may break something else
  • New feature
  • Code quality improvements
    • e.g. refactoring, documentation, tests, tooling, ...

Implementation

Update timescaledb and split up the transaction / use more bulk inserts in saveMeasurements.

Checklist

  • I gave this pull request a meaningful title
  • My pull request is targeting the dev branch
  • I have added documentation to my code
  • I have deleted code that I have commented out

Additional Information

@timber-they timber-they self-assigned this Dec 4, 2025
@timber-they timber-they linked an issue Dec 4, 2025 that may be closed by this pull request
3 tasks
Copy link
Collaborator

@scheidtdav scheidtdav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice job!

Did adjust a small thing: Moved the lat and lng into the value range (-180 to 180, -90 to 90) to use some sensible values and to make sure future updates that may validate these values don't break the tests.

@scheidtdav scheidtdav merged commit d7df360 into dev Dec 10, 2025
9 of 10 checks passed
@scheidtdav scheidtdav deleted the fix/deadlock-possible-when-posting-box-locations-via-measurement branch December 10, 2025 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

deadlock possible when posting box locations via measurement

3 participants