There is probably scope for making the console output of the GES function more useful - at the moment there is a lot of counting (without much indication of how high we should expect the numbers to go!), and some output that may have been put in for debug reasons, that is the same on every step.
Improving this is relatively low priority, but also potentially quick+easy. Some ideas:
When running in the Azure function, output some useful values at every step, as well as a counter of what step out of how many we are on.
When running interactively, perhaps suppress those messages (by logging level), and have TQDM progress bars.
There is probably scope for making the console output of the GES function more useful - at the moment there is a lot of counting (without much indication of how high we should expect the numbers to go!), and some output that may have been put in for debug reasons, that is the same on every step. Improving this is relatively low priority, but also potentially quick+easy. Some ideas: