-
Notifications
You must be signed in to change notification settings - Fork 34
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: adhearsion/punchblock
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.7.4
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: adhearsion/punchblock
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.7.5
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 6 commits
- 5 files changed
- 1 contributor
Commits on Aug 27, 2015
-
Revert "Avoid race conditions in processing calls"
This reverts commit 14f6e76. Conflicts: CHANGELOG.md
Configuration menu - View commit details
-
Copy full SHA for 014bac8 - Browse repository at this point
Copy the full SHA 014bac8View commit details -
Avoid races in processing Asterisk 13 bridges
On Asterisk 13, BridgeEnter and BridgeLeave events do not include the opposite-channel ID, leaving us to track this using the sequential events. When processed by the Call object, these must call back out to the translator to store global state to correlate. In previous releases of Punchblock, this has encountered a race condition because the translator is accessed via its ActorProxy, raising the possibility of the second event being processed before the first is done. A previous attempt to fix this was 14f6e76, released in 2.7.4, but this resulted in a suspected memory leak and crashing under heavy load in one example application. This first attempt was rolled back and the release yanked. This second attempt eliminates the issue by other means, that is moving the correlation up into the translator itself, passing the correlated data down to the call itself.
Configuration menu - View commit details
-
Copy full SHA for fa062c6 - Browse repository at this point
Copy the full SHA fa062c6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9984af3 - Browse repository at this point
Copy the full SHA 9984af3View commit details -
Don't crash if a call can't be looked up by channel
These events may be fired for calls we are not tracking.
Configuration menu - View commit details
-
Copy full SHA for 9b08947 - Browse repository at this point
Copy the full SHA 9b08947View commit details -
Configuration menu - View commit details
-
Copy full SHA for c51d7e6 - Browse repository at this point
Copy the full SHA c51d7e6View commit details -
Configuration menu - View commit details
-
Copy full SHA for cebcea4 - Browse repository at this point
Copy the full SHA cebcea4View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v2.7.4...v2.7.5