Unhandled exception in httpbeast

2020-11-25 Thread Peter
It seems that there is a workaround. If I put Jester behind http proxy (nginx) with a `localhost:5000` connection and do not use direct connections - everything works as expected, there is no exception. So, it seems to be a problem somewhere at Nim side working with 'real' network interfaces.

Unhandled exception in httpbeast

2020-11-23 Thread Peter
`events[i].errorCode` is 60 here

Unhandled exception in httpbeast

2020-11-22 Thread Peter
I'm testing my app on FreeBSD 13.0-CURRENT with NIM 1.4.0 (built from ports). After ~5 minutes of working, the web thread (Jester, communicating with web browser and some external modules) fails with the following error: /home/freebsd/Programming/noogest/noogest.nim(547) web /h

Kill thread?

2020-11-14 Thread Peter
I would like to know how can I kill a thread from the procedure that started it (NOT from the thread procedure itself). Something like `myThread.kill()`. I know I can use channels to pass a signal to the thread, so it can finish itself. But I would like to kill the thread from the 'main' routine

Deprecated operators for DateTime private members

2020-11-14 Thread Peter
**GULPF** , thanks for your answer. OK, I see the problem and I understand the solution implemented. I'm definitely not agree with it though. IMHO, the deprecation should be removed from these operators. The day you remove the assignment operators you'll break my application and I'll need to p

Deprecated operators for DateTime private members

2020-11-13 Thread Peter
**timothee** , your solution (and the alternative ways mentioned in the PR discussion) could be a solution. But the situation is more delicate here. These fields _were_ public, they passed to private in the patch I've mentioned. And the operators (deprecated!) were introduced to overcome the pot

Deprecated operators for DateTime private members

2020-11-12 Thread Peter
Thanks for you answer, **Hlaaftana**. The question is more wide that just using the assignment in the function I mentioned in my previous post. Even if I could try to use `initDateTime` in this function (if it works) - I have some other places when I use the assignments to modify the fields of `

Deprecated operators for DateTime private members

2020-11-11 Thread Peter
Hello, I see in some members of `DateTime` passed to private (for example, `second`) and the operators `=` were introduced to be able to assign

Type problem with 1.4.0

2020-11-11 Thread Peter
Indeed, `{.experimental: "implicitDeref".}` helps here. Thanks a lot for this hint. Where can I read the information about this behavior change between 1.0 and 1.4 versions?

Type problem with 1.4.0

2020-11-10 Thread Peter
Hello, I use some complex ref types as follows: type PTimeInfo = ref DateTime TimeInfoEvent = ref object of PTimeInfo channel : int command : string Run Then I use a variable of `TimeInfoEvent` in a function to initialize it: