Ilya Grigorik comments

Results 288 comments of


                                            Ilya Grigorik

FiberIterator not passing iterator to block, "call 'next' on nil" exception

We still need to fix the .next bug, but other then that.. Probably worth checking-in the spec + some docs on the gotcha's of using it between multiple fibers. :)

em_mysql2 should turn on strict mode

@dgutov sounds reasonable. willing to put together a quick pull? :)

em_mysql2 should turn on strict mode

Ah, fair enough. Should we close this and track it there then? p.s. thanks for your work on AR driver!

em_http_request 1.1.1 causes undefined method(@transaction not defined)

Hmm, are you sure you're not pulling in master? Have a suspicion that this is due to #168. /cc @jonigata

em_http_request 1.1.1 causes undefined method(@transaction not defined)

No, the other way around.. I think you're pulling master branch, not last release version (hence "em-synchrony-d775d5638cd1/" in your path). And I think commit in #168 is causing the problem.

em_http_request 1.1.1 causes undefined method(@transaction not defined)

@bhgames could you isolate the failure into a sample snippet / test case? That would go a long way to resolving this.

Using ConnectionPool with redis/ohm adds nil

I think the simplest "fix" is if Ohm returned the connection object when calling multi. Aka: ``` ruby redis.multi do |conn| conn.set 1, 1 conn.get 1 conn.set 2, 2 end...

Using ConnectionPool with redis/ohm adds nil

As a workaround for "a" issue, in the past I've simply aliased the method I want to target to a different name that doesn't clash.. Not a general solution, but...

Using ConnectionPool with redis/ohm adds nil

@dirkbolte with an increment in major version number, anything is possible.. :) ... That said, we're back to same issues raised in: https://github.com/igrigorik/em-synchrony/pull/72#issuecomment-2527164

method for getting ConnectionPool utilization

seems reasonable. patches welcome. :) info > status perhaps?