I’m trying out VIKTOR for the first time and when I tried the “Create your first app” tutorial, I can’t seem to get the updated code to run when refreshing the app in my developer workspace until I restart “viktor-cli”.
If I understand the tutorial correctly, this should not be required - only to refresh the webpage.
What am I doing wrong?
Everything should be up to date:
VIKTOR connector v5.18.2
VIKTOR SDK v13.7.1
I’m using Visual Studio Code and I’m not getting that output in the terminal window:
2023-01-26 09:50:14.078 INFO : Connecting to platform...
2023-01-26 09:50:15.696 INFO : Connection is established (Ctrl+click to open in browser): https://cloud.viktor.ai
2023-01-26 09:50:15.697 INFO : The connection can be closed using Ctrl+C
2023-01-26 09:50:16.697 INFO : App is ready
2023-01-26 09:50:22.071 INFO : Job (uid: 106961) received - EntityType: Controller - call: parametrization
2023-01-26 09:50:22.074 INFO : Job (uid: 106961) completed in 0ms
2023-01-26 09:50:22.363 INFO : Job (uid: 106962) received - EntityType: Controller - call: beam_visualisation
2023-01-26 09:50:22.787 INFO : Job (uid: 106962) completed in 421ms
I added a line of code here and saved app.py and refreshed the page:
2023-01-26 09:50:44.837 INFO : Job (uid: 106963) received - EntityType: Controller - call: parametrization
2023-01-26 09:50:44.845 INFO : Job (uid: 106963) completed in 0ms
2023-01-26 09:50:45.145 INFO : Job (uid: 106964) received - EntityType: Controller - call: beam_visualisation
2023-01-26 09:50:45.597 INFO : Job (uid: 106964) completed in 448ms
Also tried with another browser, but the “new code” doesn’t get executed then either.
Thanks for the additional information. I now understand what is happening.
The autoreload functionality works by adding the files in your app folder to a file watcher. However, to increase the reloading speed several files are excluded, for example the files in the virtual environment folder or tests. The latter is done by excluding all files and directories that are prefixed with test. Because of the fact that your app folder is called testing the entire folder is not added to the file watcher.
If you change the name of your app folder to something else you should see that the autoreload works as expected.
Thank you for reporting, I will add this to our internal issue tracker to account for this case in future versions of the CLI.