tinkering with git commit logs being stored during build, and hit a BUG - back to functional, but cant do git yet

This commit is contained in:
2022-12-28 21:36:28 +11:00
parent dc80db45f8
commit ec95cbfd47
3 changed files with 7 additions and 4 deletions

4
BUGs
View File

@@ -1,4 +1,4 @@
### Next: 109
### Next: 112
BUG-100: I managed to get 2 photos matching mich in the NOT_WORKING photo (probably dif refimgs but same p.tag?)
= /photos/2012/20120414-damien/IMG_8467.JPG
BUG-105: show unmatched needs to handle overrides (ignore face, etc.)
@@ -9,3 +9,5 @@ BUG-109: add mich force override, removed it, then re-added it, then rebuild DB
- this is actually only? possible if we restart job_mgr before its processed the metadata job(s) -- as the initialisation processes the metadata on the file
system, and then presumably the delete of the metadata will come as the next job to run...
NEED TO CONSIDER => better to defend the duplicate on load, OR, process all meta jobs before processing meta on FS OR both???
BUG-111: can't install git to container, it changes the python version and then gunicorn dies... THINK I need to try a newer base Ubuntu and see if gunicorn will just die, also fix the deprecation warning around FLASK_ENV