python-mapswipe-workers icon indicating copy to clipboard operation
python-mapswipe-workers copied to clipboard

MapSwipe Back-End

Results 100 python-mapswipe-workers issues
Sort by recently updated
recently updated
newest added

There is a lot potential to improve the database schema in order to reduce storage needs / disk size. This will help to reduce costs. At the moment database size...

Over the past week, osmcha.org has been down at least twice. This causes a crash in our project creation worker: ``` 2022-09-09 07:42:43,433 - INFO - mapswipe_workers.py - cli -...

bug

We should add something simple to ping admins on slack when some service is down. It could be as simple as a cronjob running every N hours that checks that...

enhancement
effort-half-to-one-day

scope a proposal for overhauling how tutorials are setup as it would be useful to have increased flexibility, especially with the information presented on the first page. for example, what...

enhancement
question

the default Group Size is 120 when creating a new project on the dev server. if you forget to make it smaller, it makes testing a pain. requesting that it...

**Describe the bug** Tasking Manager geometries generated by MapSwipe contain tasks that are entirely contained within other tasks (i.e. overlapping tasks). **To Reproduce** Please provide steps to reproduce the problem:...

bug

In the `load_testing.py` script, we [create temporary accounts](https://github.com/mapswipe/python-mapswipe-workers/blob/a7c769af3be67de92c2c05554a56cdb89376800a/mapswipe_workers/locust_files/load_testing.py#L127) in the form `[email protected]` but these are never cleaned up. It would be useful to remove them when the script exits, or...

good first issue
low-priority

Current setup: 2 VPS: - production: n1-standard-2, 2 cpu, 8GB RAM, 700GB SSD - staging: n1-standard-1, 1 cpu, 4GB RAM, 200GB SSD (~150GB used) Monthly cost: Current: ~300 GBP/month Expected...

docs should be updated to include details on the new mission type. should also plan for possible future mission type(s) with any structural changes to how the docs are organized.

When there is a result such as the one below in Firebase, this will lead to an error when transfering the results to postgres. This is linked to this issue...