crossbario / crossbario/autobahn-python
self.publish doesn't work in an infinite loop
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 768
- PR merge metrics
- No merged PRs in 30d
Description
I have this code :
class MyComponent(ApplicationSession):
def onConnect(self):
self.join("realm1")
@inlineCallbacks
def onJoin(self, details):
for x in range(100):
yield self.publish('foo', 'bar')
And it works : I can read the event on all the clients.
Now if I do :
class MyComponent(ApplicationSession):
def onConnect(self):
self.join("realm1")
@inlineCallbacks
def onJoin(self, details):
while True:
yield self.publish('foo', 'bar')
I don't get any event on any client. Is it too fast and flooding the router ? In that case shouldn't find a way to handle it by processing them batch by batch ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior from ApplicationSession.onJoin with the self.publish call in a while True loop, then compare it with the bounded range(100) example. Trace how publish handles repeated events and check whether the router or clients receive any events. Done means continuous publishing no longer prevents event delivery or clearly reports the limiting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100