)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"bba1ef9e331f7ee2620af7921d7de5032060616c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"4acb7211_e0270c4c","updated":"2025-05-29 10:00:44.000000000","message":"I think I have somewhat better alternative to this one: https://review.opendev.org/c/openstack/trove/+/948628","commit_id":"9cb87e6c60c1ceb70bcb6907f24fa023193801ec"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"1509b3fa4ce578aa58094783b1ef6b090b38a031","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c071319e_51bb3fb7","updated":"2025-05-29 10:02:07.000000000","message":"Oh, right. Now I see","commit_id":"9cb87e6c60c1ceb70bcb6907f24fa023193801ec"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"0eb357ec95534dd2d32c8f05a3c0926b88a95732","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"acae5271_173b049f","updated":"2025-05-29 10:03:15.000000000","message":"yes, right, we can do that 😊\nAlways not considering option to make a python from venv a default one.","commit_id":"9cb87e6c60c1ceb70bcb6907f24fa023193801ec"},{"author":{"_account_id":26285,"name":"wu.chunyang","email":"wchy1001@gmail.com","username":"wu.chunyang"},"change_message_id":"28cb3c0546cf64b00d53c62357e448aeafe06083","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ac7f2b2a_76d9c8e4","in_reply_to":"acae5271_173b049f","updated":"2025-05-30 01:29:29.000000000","message":"Yes, Linking default python3 symbolic to a venv python binary usually is not a good option. but we are in a container environment, and this container is only used to do backup actions. So, It\u0027s fine in such case.","commit_id":"9cb87e6c60c1ceb70bcb6907f24fa023193801ec"},{"author":{"_account_id":26285,"name":"wu.chunyang","email":"wchy1001@gmail.com","username":"wu.chunyang"},"change_message_id":"8a02cac86594b17792828e27ea7a519bb161a5a3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"800fd0eb_fccec1ff","updated":"2025-06-03 07:04:49.000000000","message":"Using update-alternative to replace the /usr/bin/python3 seems not work properly.","commit_id":"b6bcf34a92632a8b6ea3d6818de5ec84136fb047"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"8971085d89a22662e6b8898a03d2f4768f581db2","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ce63fef4_f959c98d","in_reply_to":"800fd0eb_fccec1ff","updated":"2025-06-03 07:08:08.000000000","message":"Are you sure this approach won\u0027t break compatibility of backup script?","commit_id":"b6bcf34a92632a8b6ea3d6818de5ec84136fb047"},{"author":{"_account_id":26285,"name":"wu.chunyang","email":"wchy1001@gmail.com","username":"wu.chunyang"},"change_message_id":"41676d560182e700e6c9589bb66566106c1f4a81","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"878b5798_7cf14ffe","in_reply_to":"82f4f081_6dde32a9","updated":"2025-06-03 09:35:17.000000000","message":"I think this should not break the compatibility in most case. As these codes are only executed in the geust vm. the present databases should still use old code, because when the trove(trove-api.trove-taskmanager,trove-conductor) was upgraded from previous version, the trove code in guest vm should not be updated.  but when the user use the newer coder to built the backup images. it may not work. i didn\u0027t have a good idea for this. maybe we can still use break-system-packages flags until we remove the support of the current datastore versions?\n\nUsing shebang may face the same problem.  any good suggestion?","commit_id":"b6bcf34a92632a8b6ea3d6818de5ec84136fb047"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"da7b1caee46a45219130d73d62c73f6f2ed35357","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"19627571_796a6a47","in_reply_to":"878b5798_7cf14ffe","updated":"2025-06-04 09:16:26.000000000","message":"`--break-system-packages` on 24.04 really may lead to not best consequences. so IMO, worth doing venvs sooner then later.\n\nBut I think you;re right and this should not break anything. So I think this is good approach.","commit_id":"b6bcf34a92632a8b6ea3d6818de5ec84136fb047"},{"author":{"_account_id":28619,"name":"Dmitriy Rabotyagov","email":"noonedeadpunk@gmail.com","username":"noonedeadpunk"},"change_message_id":"44b5469974aa8d6fa4b21e463c8758c61eafbda1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"82f4f081_6dde32a9","in_reply_to":"ce63fef4_f959c98d","updated":"2025-06-03 07:17:33.000000000","message":"Like it should not, but I\u0027m not daily driving docker, but know that it\u0027s images might have some quirks and unexpected behavior comparing to normal...\n\nAs might be we can set an executable flag on `main.py` and add shebang like `#!/usr/bin/env python3` and then get rid of python path from datastore code as a whole?","commit_id":"b6bcf34a92632a8b6ea3d6818de5ec84136fb047"}]}