-
-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Support from_time for the /tracking/<user_ids> endpoint #2277
Comments
Hey @Turbo87 do you think this is a good idea ? Would you merge this if I create a PR ? The query parameter could be called
The advantage would be that I don't have to pull 12h of track every time I retrieve positions from Skylines. It would save bandwidth and CPU. What do you think ? |
seems like a reasonable request. I'm a little worried about breaking the existing code though, so it would be great if you could ensure that we have decent test coverage for these endpoints before modifying them. 🙏 |
Thanks @Turbo87 I'll give it a try. I am having troubles installing the Vagrant env. On the first Do you have updated instructions on how to setup the development environment and run the tests ? Thanks, |
I haven't run if for a while. It's possible that some dependency update broke it... 😞 welcome to the rabbit hole 🎉 |
I can try to investigate this. How do you debug the server ? What are the steps to install the python deps an run the tests ? I guess |
depends on what exactly you mean by that
skylines/.github/workflows/ci.yml Lines 114 to 119 in 2a6c948
|
I have hacked a working config using https://github.com/nektos/act Using the comand:
I should be able to make some progress with that. Thanks for your help. |
This feature request is similar to how
/tracking/<user_id>/json
supports alast_update
parameter to only fetch the latest points... but a bit different.The idea is to be able to request the updates for a group of pilots from a given time so
last_update
should be a timestamp (number of seconds since January 1, 1970 12:00:00 AM).The way
last_update
is implemented in/tracking/<user_id>/json
would not work.That's because in this case
last_update
is the number of seconds since prior midnight UTC of the first track point.Let's say pilotA starts flying at 23:30 UTC and pilotB starts flying at 00:30 UTC then their reference day would be different and there is no one
last_update
value that is common to both. Makinglast_update
a timestamp for the/tracking/<user_ids>
endpoint would solve this.Context: I am revamping the SkyLines tracker support into flyxc.app.
Thanks !
The text was updated successfully, but these errors were encountered: