ReferenceError: weakly-referenced object no longer exists

[fafhrd91]

@asvetlov could you look at this exception, ClientReponse.del?

ERROR [asyncio] Exception in default exception handler
Traceback (most recent call last):
 File "/usr/lib/python3.4/asyncio/base_events.py", line 719, in call_exception_handler
   self.default_exception_handler(context)
 File "/usr/lib/python3.4/asyncio/base_events.py", line 696, in default_exception_handler
   log_lines.append('{}: {!r}'.format(key, context[key]))
 File "/usr/lib/python3.4/asyncio/tasks.py", line 164, in __repr__
   res = super().__repr__()
 File "/usr/lib/python3.4/asyncio/futures.py", line 157, in __repr__
   res += '<exception={!r}>'.format(self._exception)
 File "/opt/files/lib/python3.4/site-packages/aiohttp/client.py", line 576, in __repr__
   print(self.headers, file=out)
 File "/opt/files/lib/python3.4/site-packages/aiohttp/multidict.py", line 88, in __repr__
   return '<{} {!r}>'.format(self.__class__.__name__, self._items)
 File "/usr/lib/python3.4/reprlib.py", line 24, in wrapper
   result = user_function(self)
 File "/usr/lib/python3.4/collections/__init__.py", line 198, in __repr__
   return '%s(%r)' % (self.__class__.__name__, list(self.items()))
 File "/usr/lib/python3.4/_collections_abc.py", line 484, in __iter__
   for key in self._mapping:
 File "/usr/lib/python3.4/collections/__init__.py", line 87, in __iter__
   curr = root.next
ReferenceError: weakly-referenced object no longer exists

[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 notifications@github.com 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.