update vlass templates for pimscache python3.10 upgrade
Let's make sure pimscache can actually find python3.10 from a workflow...
Merge request reports
Activity
added 26 commits
- 7c409cd1...a573b188 - 16 earlier commits
- f407f560 - Forgot to update assertions
- 593fac76 - Using the basename of the prev_spool_dir and then relative paths to not move...
- 09c42bd9 - Put rawdata dir check in quotes to make it safe against spaces
- e899c4d0 - Updated signature for current_version to indicate it could return None
- f8a7b717 - Not necessary to check that current_version is None here, that's done by the restriction engine
- e4693278 - Updated alembic down revision
- a5faf075 - Corrected alembic down revision for ws_annihilator notification migration
- 74a3b0af - Renamed prev_spool to prev_processing to work towards a brighter future
- 087532e5 - Typo in bash var name
- 545dacff - update down revision
Toggle commit listadded 31 commits
-
545dacff...be540136 - 28 commits from branch
main
- f1ec067e - update vlass templates for pimscache python3.10 upgrade
- 5a0965ea - update down revision
- 8c3f0f96 - Merge remote-tracking branch 'origin/update-vlass-python' into update-vlass-python
Toggle commit list-
545dacff...be540136 - 28 commits from branch
mentioned in commit 2033c97f
Please register or sign in to reply