Skip to content

4.3.116
Compare
Choose a tag to compare
@pklinus pklinus released this 18 Aug 15:18
· 102 commits to 4.3 since this release
4.3.116
72b235e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Generic badge

Changes for 4.3.116

Changes to branch 4.3 after version 4.3.115.

Commits

  • SUPP-8: read exisiting account document to get tree when importing enabled field - by icehess

    When trying to disable an account via the Account Manager app, the account is not disabled.

    This bug was introduce when account creation/deletion was moved to core.

    Before that move, we properly load and merge the request document with doc from database

    so we had the pvt_tree field when we were checking ig the requestor is in

    account's tree.

    But this got moved into after validation and in post/1,2 function and so we

    don't set enabled anymore.

  • Update teletype available macros list - by Harenson Henao

    Master: 2600hz/kazoo-teletype#8

  • HELP-15749: start kazoo_number_manager before kazoo_events - by James Aimonetti

    When blackhole runs stand-alone, it relies on kazoo_events for the

    kz_hooks when subscriptions for channel events are made. When the

    event is a CHANNEL_CREATE from offnet, and no account ID is

    associated, kz_hooks_util uses knm_number to lookup the account

    associated with the destination.

    kazoo_events.app did not list kazoo_number_manager as a dependency;

    thus knm was not started and number lookups failed since the knm cache

    wasn't started.

    Updating kazoo_events.app to its proper dependencies resolves the issue.

  • Improve handling of slow websocket clients - by James Aimonetti

    When a websocket client is having trouble reading messages off its

    socket, backpressure will cause the mailbox of the

    blackhole_socket_handler to start to fill up with {send_data, _}

    tuples from blackhole_data_emitter. This is due to the sending of data

    being stuck in prim_inet:send/3.

    We add two mechnisms to try to avoid the server being harshly impacted

    by slow clients:

    1. Reduce the send_timeout blackhole uses to more quickly terminate

    the socket in the event of slow sends

    1. Check the mailbox of blackhole_socket_handler from

    blackhole_data_emitter before sending the {send_data, _} tuple, opting

    to shed the load while waiting.

  • - DUPT-193: Make conference websocket events more granular - by John White

    This PR Addresses a bug where the newly introduced granular subscriptions were passing the legacy binding thru and rewriting into the newer binding string.

    Example:

    ...

auth_token: sessionStorage.getItem('auth_token'),

data: {

account_id: data.data.account_id,

binding: 'conference.event.b05d601a69718090248aec40ee8e049d.*'

}

    was rewriting to conference.event.b05d601a69718090248aec40ee8e049d.*.*

  • HELP-15556: correct classifiers before setting into accumulator - by James Aimonetti

    System classifiers missing 'friendly_name' would be "corrected" into

    the accumulator object instead of the classifier settings.

    Add classifier name as "friendly_name" into the classifier's settings

    object and set that updated object into the accumulator.

  • PISTON-1088: more DRY Makefile dialyze targets - by Daniel Finke

    • also make the output of check-dialyzer.escript consistently "nothing"

    whether using --bulk, --hard, or no flags at all

Assets 2
Loading