Skip to content

fix: MQTT client_id and protocol not passed down to Client#3252

Merged
cyberw merged 2 commits intolocustio:masterfrom
ionutab:master
Nov 1, 2025
Merged

fix: MQTT client_id and protocol not passed down to Client#3252
cyberw merged 2 commits intolocustio:masterfrom
ionutab:master

Conversation

@ionutab
Copy link
Copy Markdown
Contributor

@ionutab ionutab commented Oct 31, 2025

When migrating the MqttClient from Locust Plugins I accidentally modified the call to the parent constructor.

SvenskaSpel/locust-plugins@f1845b9#diff-94fac3dc568e54a6e6f7dc07955bfe16912cea237d2dfcc98f54d97d9d556071L115

@ionutab
Copy link
Copy Markdown
Contributor Author

ionutab commented Oct 31, 2025

should I add a test to ensure that the protocol is passed on correctly?
I'm not sure how I would implement it.
Would it be worth it?
Thanks

@ionutab ionutab changed the title fix: client_id and protocol not passed down to Client fix: MQTT client_id and protocol not passed down to Client Oct 31, 2025
@cyberw
Copy link
Copy Markdown
Collaborator

cyberw commented Oct 31, 2025

No need for a test, but probably nice to add an example for how to use it!

@cyberw cyberw merged commit 9bda566 into locustio:master Nov 1, 2025
16 of 18 checks passed
@cyberw
Copy link
Copy Markdown
Collaborator

cyberw commented Nov 1, 2025

I just realized that you were only correcting a mistake in moving it, in which case no need for anything more :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants