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

[BUG] Dbus Event handler keeps publishing data even on unsuccessful connections #123

Open
PFigs opened this issue Sep 2, 2019 · 0 comments
Open

[BUG] Dbus Event handler keeps publishing data even on unsuccessful connections #123

PFigs opened this issue Sep 2, 2019 · 0 comments
Assignees
@GwendalRaoul
Labels
bug Something isn't working interface/transport Issues related to the gateway transport interface
Milestone
1.3.0

Comments

@PFigs
Copy link
Contributor

PFigs commented Sep 2, 2019

Describe the bug
The transport service keeps receiving DBUS packets and calling received_data even when a MQTT connection is not established correctly.

I've observed that sometimes the transport service exits cleanly as expected.

To Reproduce
Steps to reproduce the behavior:

  1. Configure incorrect user/pwd credentials
  2. Start the gateway services

Expected behavior
The transport service should exit

Platform details:

  • OS: Ubuntu 19.04
  • Gateway host: x86_64 desktop
  • Python version: 3.6
  • Docker engine: 18.06.1-ce
  • MQTT Broker vendor: mosquitto
  • MQTT Broker version: 1.6
@PFigs PFigs added bug Something isn't working interface/transport Issues related to the gateway transport interface labels Sep 2, 2019
@PFigs PFigs added this to the 1.3.0 milestone Sep 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@GwendalRaoul GwendalRaoul

Labels
bug Something isn't working interface/transport Issues related to the gateway transport interface
Projects
None yet
Milestone
1.3.0
Development

No branches or pull requests
2 participants
@PFigs @GwendalRaoul