On 10/14/20 2:25 PM, Andre Pany wrote:
> On Wednesday, 14 October 2020 at 18:08:40 UTC, H. S. Teoh wrote:
>> On Wed, Oct 14, 2020 at 05:30:37PM +0000, Andre Pany via Digitalmars-d-learn wrote:
>>> On Wednesday, 14 October 2020 at 16:39:39 UTC, Imperatorn wrote:
>>> > On Wednesday, 14 October 2020 at 15:27:46 UTC, Andre Pany > wrote:
>> [...]
>>> > > [...]
>> [...]
>>> > Where is this documented?
>>>
>>> I dont know whether it is documented somewhere. It was asked multiple times in the forum therefore I remembered.
>>>
>>> Maybe it could be documented in the vibe.d github wiki or on the vibe.d website. But hopefully the bug is solved soon.
>> [...]
>>
>> Yeah, this is a problem.  Things like these need to be put in the docs in an easy-to-find way. Like collected in a Troubleshooting page or something.  If a bug isn't filed yet, I'd file a bug on vibe.d so that this will get resolved instead of forgotten, and then it will bite the next newcomer all over again.
>>
>>
>> T
> 
> https://github.com/search?q=VibeHighEventPriority&type=issues
> 
> It seems with eventcore 0.9.9 there was some fix, but I do not know whether this solves the bug or s.th. related to the bug.
> 

Is this the commit you are talking about?

https://github.com/vibe-d/eventcore/pull/122

I haven't tested turning the version definition off. But it probably should be easy enough to do a vanilla vibe-d install and see if it works.

I hope this is the fix, because this bug has been a huge problem, especially for people trying vibe for the first time.

-Steve

On Thursday, 15 October 2020 at 13:17:57 UTC, Steven Schveighoffer wrote:
> On 10/14/20 2:25 PM, Andre Pany wrote:
>> On Wednesday, 14 October 2020 at 18:08:40 UTC, H. S. Teoh wrote:
>>> On Wed, Oct 14, 2020 at 05:30:37PM +0000, Andre Pany via Digitalmars-d-learn wrote:
>>>> > > [...]
>>> [...]
>>>> > > [...]
>>> [...]
>>>> [...]
>>> [...]
>>>
>>> Yeah, this is a problem.  Things like these need to be put in the docs in an easy-to-find way. Like collected in a Troubleshooting page or something.  If a bug isn't filed yet, I'd file a bug on vibe.d so that this will get resolved instead of forgotten, and then it will bite the next newcomer all over again.
>>>
>>>
>>> T
>> 
>> https://github.com/search?q=VibeHighEventPriority&type=issues
>> 
>> It seems with eventcore 0.9.9 there was some fix, but I do not know whether this solves the bug or s.th. related to the bug.
>> 
>
> Is this the commit you are talking about?
>
> https://github.com/vibe-d/eventcore/pull/122
>
> I haven't tested turning the version definition off. But it probably should be easy enough to do a vanilla vibe-d install and see if it works.
>
> I hope this is the fix, because this bug has been a huge problem, especially for people trying vibe for the first time.
>
> -Steve

I meant this one:
https://github.com/vibe-d/eventcore/pull/154

I testing it at the moment, while there still "leaking" warnings, the ports are released after terminating the application with Ctrl+c. So far I was not able to reproduce the issue with vibe.d 0.9.2 (eventcore 0.9.9).

Kind regards
Andre

On 10/15/20 9:55 AM, Andre Pany wrote:

> 
> I meant this one:
> https://github.com/vibe-d/eventcore/pull/154
> 
> I testing it at the moment, while there still "leaking" warnings, the ports are released after terminating the application with Ctrl+c. So far I was not able to reproduce the issue with vibe.d 0.9.2 (eventcore 0.9.9).

Soo.... if you try to print a warning it keeps the process alive? I can't understand how this would fix it. It is still printing too, so how could that have fixed the problem?

-Steve

On 10/15/20 10:22 AM, Steven Schveighoffer wrote:
> On 10/15/20 9:55 AM, Andre Pany wrote:
> 
>>
>> I meant this one:
>> https://github.com/vibe-d/eventcore/pull/154
>>
>> I testing it at the moment, while there still "leaking" warnings, the ports are released after terminating the application with Ctrl+c. So far I was not able to reproduce the issue with vibe.d 0.9.2 (eventcore 0.9.9).
> 
> Soo.... if you try to print a warning it keeps the process alive? I can't understand how this would fix it. It is still printing too, so how could that have fixed the problem?
> 

Not fixed. I just did the same test (dub init -t vibe.d) and it fails to kill the process. Still have to kill with -9.

-Steve

On Thursday, 15 October 2020 at 14:26:37 UTC, Steven Schveighoffer wrote:
> On 10/15/20 10:22 AM, Steven Schveighoffer wrote:
>> On 10/15/20 9:55 AM, Andre Pany wrote:
>> 
>>>
>>> I meant this one:
>>> https://github.com/vibe-d/eventcore/pull/154
>>>
>>> I testing it at the moment, while there still "leaking" warnings, the ports are released after terminating the application with Ctrl+c. So far I was not able to reproduce the issue with vibe.d 0.9.2 (eventcore 0.9.9).
>> 
>> Soo.... if you try to print a warning it keeps the process alive? I can't understand how this would fix it. It is still printing too, so how could that have fixed the problem?
>> 
>
> Not fixed. I just did the same test (dub init -t vibe.d) and it fails to kill the process. Still have to kill with -9.
>
> -Steve

You are right, I only tested it on Windows. Here it is working (stopping with ctrl+c and starting again) except the warnings.

Kind regards
Andre