Do not store simulated drones in memory indefinitely

Knowabunga! 🐢🐢🐢🐢

This issue is tagged Knowabunga. It is only open for participants of the Knowabunga/DAV hackathon!

Thank you for your help :heart:

What is this project?

DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.

The specific project you are looking at is Mission Control. It is the brain in charge of orchestrating missions between DAV users and autonomous vehicles.

How you can help

Mission Control comes with a built in simulation environment which generates and controls simulated vehicles, allowing developers to start developing without investing in costly hardware first.

If a use is looking at any point on the map inside the missions app, and there are no vehicles around, the server will generate a few simulated vehicles on demand around that point.

Once we have many developers from around the world experimenting with the simulation environment, more and more vehicles will be kept in memory and never deleted.

What you can do

We need to add a TTL (Time To Live) expiration to the vehicles stored in Redis so that they are deleted automatically after 24 hours. And we need to reset that TTL, setting it to 24 hours again when those vehicles are accessed.

These vehicles are created in /server/store/vehicles.js, and the EXPIRE needs to be set when calling addNewVehicle() and getVehicle()

Contributing to Mission Control

[ ] Make sure no one has commented below that they are starting to work on this already.
[ ] Comment in this issue that you would like to do it.
[ ] Fork the repository from the Mission Control GitHub page.
[ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/missioncontrol.git
[ ] Make your changes.
[ ] Run npm test to verify that all the tests pass.
[ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
[ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/missioncontrol) and create a pull request for your changes.
[ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #6)
[ ] Get hooked on open source!

DAVFoundation / missioncontrol