thread problem

2016-01-13 Thread mt1957
L.s. I got the following error 'Tried to read() on a socket from outside its originating thread' This socket is created while in another thread using Promise and the object is retrieved using $promise.result. The weird thing is also that just a few lines before that the same socket is used fo

Re: thread problem

2016-01-13 Thread Will Coleda
Can you post the code that causes the issue? On Wed, Jan 13, 2016 at 4:00 AM, mt1957 wrote: > L.s. > > I got the following error > > 'Tried to read() on a socket from outside its originating thread' > > This socket is created while in another thread using Promise and the object > is retrieved usi

Re: thread problem

2016-01-13 Thread mt1957
On 01/13/2016 04:39 PM, Will Coleda wrote: Hi Will, First I must say that the code is still in development so it might look a bit messy. Now the test file uses the Client to get a MongoDB server using host and port info. This info can default to localhost and port 27017. The tests are using a

Re: thread problem

2016-01-14 Thread Timo Paulssen
I regret to inform you that we currently have that limitation. It's due to a design decision in libuv that we haven't found a good/the perfect work-around for in MoarVM. Instead of getting that error, you used to just get empty results, if I recall correctly. I haven't taken the time to read t