Associate log messages to instances (where possible)
Ignore nameko egg-info
Added logging around reply_event — very useful for diagnosing unresponsive consumer issues
Associate log messages to instances (where possible)
Initial working example, call ID is requested on entry points
Robust test checks how the call ID stack is built up
Stand-alone test for the OnceProvider
Note about full-stack vs parent-only
Test more specifically about stack instantiation
Use a constant for the call stack ID storage in context
Test that event dispatching uses the call ID stack
Remove traceback from remote errors
Only log the current call ID and the parent one
Polish test code
Mark as using fixture, rather than parameter
Merge branch 'master' into rpc-tracking-callid-829
Note about *rarely* failing test
Call ID and stack are now first class members of worker contexts
Move once module into testing
Test stack is decoded when present