-
Notifications
You must be signed in to change notification settings - Fork 176
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
Cannot start a pipeline with a Notification data sink #3004
Comments
Hi @michaelreisvoid, thanks for opening the issue. I attempted to reproduce the problem on a new instance of StreamPipes version Could you clarify your setup? Did you set up a new StreamPipes instance, or did you migrate from version 0.93.0 to 0.95.0? If you migrated, did you update all of the Docker services or only the backend? |
Hi @tenthe , I am using the release directly, running locally with docker compose: I was using the mqtt adaptor, but I just tried with the machine data simulator, and still run into the same issue. I can create the pipeline, |
Ok, I also pruned all of my volumes, repeated the steps, and now it works as expected. |
@michaelreisvoid, ok. Thanks for the information, also if you have any further questions please feel free to ask. If anyone else is facing this issue during the update from 0.93.0 to 0.95.0, please feel free to reopen this issue. |
Apache StreamPipes version
Other StreamPipes version (please specify below)
Affected StreamPipes components
Backend, Processing Elements, UI
What happened?
in version 0.95, when I create a pipeline with a Notification data sink, or an Email Notification data sink, I can't start the pipeline, an error is displayed.
How to reproduce?
Create a pipeline with a Notification data sink, and then try to start the pipeline.
Expected behavior
Pipeline is started and notifications are stored.
Additional technical information
This happens with 0.95
This does not happen with 0.93
The following stacktrace is logged:
Are you willing to submit a PR?
None
The text was updated successfully, but these errors were encountered: