Worker.Stop cause all workers to stop

[Whitehouse112]

Hi,

just a quick question about how Worker.Stop() works:
I have different instances of worker class cause I want to acquire multiple sources at the same time. The strange thing is that if I call Stop() eg. on worker1 all other instantiated workers stop to receive data.

Am I missing something or this is the expected behavior?

Thanks
Regards

[K.Wagner]

Hello,

it looks like a bug. I have open a ticket for this . We will fix this as soon as possible.

Thanks for bringing this to our attention.

[K.Wagner]

Hello again,

we have fixed the problem and have built a beta package for testing purpose (it is not online neither here nor in Nuget.org).

If you are interesed in testing this, please write an email to support[at]peak-system.com mentioning this post and we will send you the package, which will need to be installed from a local folder instead of the nuget server
(more information in this: How do I install the assembly using Visual Studio).
Remark: Note that the package is marked as a "beta" version, so you need to allow prereleases installation in order to get this version installed.

We look forward to your test results.

[Whitehouse112]

Nice, thank you.

Are you planning to release the package also on Nuget as beta packet? I see there is the possibility to release packets marked as beta (eg https://www.nuget.org/packages/MQTTnet# ... s-body-tab).

Thanks
Regards

[K.Wagner]

Hello,

I see there is the possibility to release packets marked as beta

We are aware that this is possible, but we will not share this beta yet in NuGet.org. This version is just intended for you to assert that the issue is fixed.

[Whitehouse112]

Hi,

sorry but I can't request the beta package due to company policy. I can't receive attachment from an external domain: it would not be received.
Considering this bug is a general one, not only related to my implementation, I'd ask to release the beta package on NuGet.org to let me test it (even if it's easily reproducible and no need to be tested from my side btw, hence I can't get why you don't want to release on NuGet).
Let me know if it's possible.

Thanks a lot
Regards

[PEAK-Support]

sorry but I can't request the beta package due to company policy. I can't receive attachment from an external domain: it would not be received.
Considering this bug is a general one, not only related to my implementation, I'd ask to release the beta package on NuGet.org to let me test it (even if it's easily reproducible and no need to be tested from my side btw, hence I can't get why you don't want to release on NuGet).
Let me know if it's possible.

Then we are sorry, and you need to wait until we will release the new version. But our company policy do not allow to post a pre-version on the official page...
as you see - every company have its policy. Our proposal was that we send the *.nget file by e-mail or as download link from our secure trop box.
If you are not able to use one of this file sharing option, you need to wait until our developer team have made all needed tests and a release version is available.
I am wondering, because you are not registered with a company e.mail address, and you use a free available anonymous gmail address.
So why not be able to receive a simple attachment also on this address...

[Whitehouse112]

I can obviously receive an attachment on my personal, anonymous email address, but once it's received I'd need to forward to my company email address .
Anyway, thanks for the clarification, I'll wait for the release once available.

Regards

[Whitehouse112]

Hi,
is there any estimated time for new version to be released (weeks, months, ..)?

Thanks

[PEAK-Support]

We already offer you to download the pre-release version.
As release version must be validate, it could need some time.
Please use the pre-release if you could not wait.