-
-
Notifications
You must be signed in to change notification settings - Fork 799
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PVS Studio throws AttributeError: 'NoneType' object has no attribute 'lower' #4237
Comments
Hi @TD-er ! So how do I reproduce the issue? What environment to run? I'd appreciate a bit more details. |
The actual error output:
|
Just curious, what was the bug? |
TBH, I wasn't able to reproduce it, although I figured out where it may fail. Anyway, please do retest with the latest development version of the PlatformIO. Please note I also updated the PVS package to the latest 7.18. |
I just tested with PIO 6.0.1 and I'm sorry to report that it still isn't fixed :(
|
Not 100% sure what I may have changed, but now I do get some usable output from PVS Studio, but the output is not browseble in the PIO Home inspect window. What I did (and have tried several times):
The output is like this:
|
Configuration
Operating system:
PlatformIO Version (
platformio --version
):Description of problem
The error itself seems to be similar to this (closed) issue: #3989
I also have contacted the PVS Studio team about this and their reply was:
It is about my project ESPEasy: https://github.com/letscontrolit/ESPEasy
I do have several PIO envs defined for checking with PVS Studio. They all have names starting with:
spec_debug_*
A while ago, the PVS Studio inspect option was running, but I could not browse through the found issues anymore.
Still the error output contained all PVS Studio output, so I could browse through it by copying it to a notepad and process them by hand.
N.B. Due to a very busy time with me moving to my rebuilt house, I had not yet found the time to open this issue.
My mail contact about this with the PVS Studio team was in the first half of March.
The text was updated successfully, but these errors were encountered: