Closed jneilliii closed 4 years ago
Since this part is str/bytes sensitive: are you using Python 2 or Python 3?
Python 3.7
In your config.yaml, is plugins/ngrok/auth_pass
obfuscated or clear-text?
Is plugins/ngrok/_config_version
set?
Do you use any special characters in your password?
I'm not having luck reproducing this error.
These are the steps that I used to convert my virtualenv.
https://community.octoprint.org/t/upgrade-your-octoprint-install-to-python-3/21232
Settings never save because of the error it seems, nothing in config.yaml, password has no special characters just text and numbers. There was also error on version migration, so I even tried clearing the settings completely. Let me do a full uninstall/reinstall of the plugin and see what happens.
Ah, I see what is going on: the settings migrations is not working as expected. ~Fortunately this only affects those who tested my plugin since last friday (so... you?).~ Nope, everyone.
Could you test 90fef2a (the devel branch)?
Yep, that version works.
I just looked at your changes and think it's catching the scenario now where there is a blank auth token, where before sending an empty string to those util functions were breaking.
Good point, let me test that before I push a release.
That was my first test, by clearing the data during uninstall. Be careful though because there is a bug with OctoPrint that if you clear the data it can leave a ngrok: null
in config.yaml which causes all kind of binding headaches.
Done some more testing with partial configurations. Tagging 0.1.1
Be careful though because there is a bug with OctoPrint that if you clear the data it can leave a
ngrok: null
in config.yaml which causes all kind of binding headaches.
For the record, that bug will be fixed with 1.4.1.
Thanks again!
(I swear I don't always fumble around like this :pleading_face:)