-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nil calls causing agents to become stranded #59
Open
system123
wants to merge
4
commits into
adhearsion:develop
Choose a base branch
from
system123:bugfix/nil-calls-in-queue
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
75f3ede
Merge pull request #2 from adhearsion/develop
system123 39b2094
Fixed nil calls in queue causing agents to become stranded when using…
89db809
Connect callback is trigered before the call is actually connected
7acad81
Moved notification out of handler
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any theory as to how objects in the queue became
nil
? This seems like a bandaid, and probably incomplete?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cannot reproduce the issue on a small scale, only when we have more than 50 agents. The outbound call is valid and active when it is queued but it seems that by the time the loop checking for connections pops that call off the queue the call is then nil. My only thought is that the call dies and becomes nil somewhere between it being queued and getting connection, yet the connection is happening before the call is removed.
My thinking for this is that call_waiting? returns true still meaning the queue has a nil object on it, rather than it being empty. I have been battling to find the exact cause. This bandaid does solve the issue, but I agree it is not an ideal solution.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The thing is that values in an array can't become
nil
. The call can end, the actor can die, the value can become useless, but the value itself can't magically change fromAdhearsion::Call
tonil
.I can only think of two ways that a
nil
object would be enqueued:nil
into the queue - perhaps this can happen when a call connection fails? Maybe a call variable gets cleared and anil
value is re-added to the queue for the next agent? Adding trace logging to the code that puts a failed-attempt call back into the queue array could reveal this