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.

Sign up for GitHub

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

Jump to bottom

New error "'NoneType' object is not subscriptable" #119

Closed
AntoninHL opened this issue Jul 5, 2019 · 4 comments
Closed

New error "'NoneType' object is not subscriptable" #119

AntoninHL opened this issue Jul 5, 2019 · 4 comments
Labels
question Further information is requested solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@AntoninHL
Copy link

Hey,

after the new pull to correct "stix2 module error", I have a new error

integration_1    | You are not allowed to do this.
integration_1    | 'NoneType' object is not subscriptable
integration_1    | You are not allowed to do this.
integration_1    | 'NoneType' object is not subscriptable

:-(

Antonin
@SamuelHassine
Copy link
Member

This is linked to the configuration of the integration that is generated or present in the volume "config". You can either: clear your Docker and start fresh with new volumes, or change directly the configuration in this volume and change the API key. I do not know why the key is stick to the old one, but is clearly a problem of how you implement the persistence.

@AntoninHL
Copy link
Author

:-(
ok... so I will destroy volumes... and restart all imports :-(

@richard-julien
Copy link
Member

Sorry for that situation @Wesh. It's clearly a kind of situation we want to avoid in the future. We plan to refactor this part to prevent any future problem of this nature.

@richard-julien
Copy link
Member

richard-julien commented Jul 7, 2019 •
edited

Will be fix by #74 and #121

@richard-julien richard-julien mentioned this issue Jul 7, 2019
Closed
@SamuelHassine SamuelHassine mentioned this issue Jul 7, 2019
Closed
@SamuelHassine SamuelHassine added question Further information is requested solved use to identify issue that has been solved (must be linked to the solving PR) labels Jul 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@AntoninHL @richard-julien @SamuelHassine