ReferenceError: weakly-referenced object no longer exists about aiohttp

[fafhrd91]

@asvetlov i saw this several times in production system.

[asvetlov]

@fafhrd91 I'll take a look.

[asvetlov]

@fafhrd91 Hmm, do you store weak references to ClientResponse in ordered dicts?
Or, maybe, do push response/connector/connection into http headers multidict?

[fafhrd91]

no, i don't. also response's headers object is immutable.

[fafhrd91]

i'll review my code

[asvetlov]

@fafhrd91 can we close the issue?

[fafhrd91]

i still see this problem in production

On Oct 16, 2014, at 5:51 PM, Andrew Svetlov [email protected] wrote:

@fafhrd91 https://github.com/fafhrd91 can we close the issue?

—
Reply to this email directly or view it on GitHub #86 (comment).

[asvetlov]

Hmm. Ok. Let's investigate it tomorrow.

[fafhrd91]

seems problem is resolved with new asyncio

[asvetlov]

Sounds good

[lock]

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.