will read_reply() lost message in Pub/Sub?

I have write a Pub/Sub code in worker_init and work very well,thanks agentzh abundant issue support ,code under here:

local res, err = red:subscribe("nginx")
    while not ngx.worker.exiting() do
        repeat
            local key, err = red:read_reply()
            if not key then--here timeout
                ngx.log(ngx.INFO,"err is :",err)
                break
            end
            key = key[3]
            local value,err = red2:get(key)
            if value == nil or (type(value) == "boolean" and not value) then
                ngx.log(ngx.INFO,"value is null: ",value)
                break
            else
                ngx.log(ngx.INFO,"value is set to LRU: ",value)
                c:set(key,value)
            end
        until true
    end

Will red:read_reply() lost message when PUB command send in redis is between timeout or handle logic and next read_reply ?
As I know about epoll implemention, I think it will not lost in handle business logic,but I don't know about timeout error
if read_reply have timeout error,will PUB message lost?

Start with the worker_init loop shown in the issue and the lua-resty-redis read_reply() documentation or implementation. Trace how timeout errors and queued Pub/Sub replies are handled between calls, then verify whether a message can be lost during a timeout or between reads.