Skip to content
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

Prevent exception due to value not being set #261

Closed
wants to merge 1 commit into from

Conversation

sposs
Copy link

@sposs sposs commented Aug 25, 2020

In case described, the value is set to None, so it is in the dict. This raises the exception mentioned. The fix prevents the error.

In case described, the value is set to None, so it is in the dict. This raised the exception mentionned.
@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.678% when pulling e71897c on sposs:master into 8554603 on maxtepkeev:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.678% when pulling e71897c on sposs:master into 8554603 on maxtepkeev:master.

@maxtepkeev maxtepkeev self-assigned this Dec 30, 2022
@maxtepkeev maxtepkeev added the bug label Dec 30, 2022
@maxtepkeev
Copy link
Owner

Hi @sposs

It took me a while to reply... Sorry about that and thanks for raising this issue, the problem was actually way more serious as we were raising the exception for all attributes that actually exist, but their value was set to None, so this PR wasn't enough and we had to make a global fix (0de5689) which will work for all resources.

@maxtepkeev maxtepkeev closed this Dec 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants