[OpenSIPS-Devel] [OpenSIPS/opensips] 9ee8c0: evi: More verbose about which param caused crash

[Vlad Pătrașcu]

  Branch: refs/heads/master
  Home:   https://github.com/OpenSIPS/opensips
  Commit: 9ee8c06484dc8fa50a8c9ab44a6a9e7e7aa40e21
      https://github.com/OpenSIPS/opensips/commit/9ee8c06484dc8fa50a8c9ab44a6a9e7e7aa40e21
  Author: Peter Lemenkov <lemenkov at gmail.com>
  Date:   2020-09-01 (Tue, 01 Sep 2020)

  Changed paths:
    M evi/evi_transport.c
    M modules/event_datagram/event_datagram.c
    M modules/event_rabbitmq/event_rabbitmq.c
    M modules/event_stream/stream_send.c

  Log Message:
  -----------
  evi: More verbose about which param caused crash

When using evi interface sometimes we need to know exactly which
parameter led to failure. At least we need its name and event's name.

Signed-off-by: Peter Lemenkov <lemenkov at gmail.com>


  Commit: b801f04c4acc970e4c37bae736d0c0518ab0958b
      https://github.com/OpenSIPS/opensips/commit/b801f04c4acc970e4c37bae736d0c0518ab0958b
  Author: Peter Lemenkov <lemenkov at gmail.com>
  Date:   2020-09-01 (Tue, 01 Sep 2020)

  Changed paths:
    M evi/evi_transport.c

  Log Message:
  -----------
  evi: Str params can contain NULL values.

NULL value as a str param is totally fine according to JSON
specification. So let's not crash when adding str parameter with NULL
value.

Signed-off-by: Peter Lemenkov <lemenkov at gmail.com>


  Commit: bbcace7821d95cd52919c472398793c9cc9f51a3
      https://github.com/OpenSIPS/opensips/commit/bbcace7821d95cd52919c472398793c9cc9f51a3
  Author: Vlad Pătrașcu <vladp at opensips.org>
  Date:   2020-09-02 (Wed, 02 Sep 2020)

  Changed paths:
    M evi/evi_transport.c
    M modules/event_datagram/event_datagram.c
    M modules/event_rabbitmq/event_rabbitmq.c
    M modules/event_stream/stream_send.c

  Log Message:
  -----------
  Merge pull request #2212 from lemenkov/verbose_events

Fix NULL values for str params in EVI API


Compare: https://github.com/OpenSIPS/opensips/compare/488c56b4cafb...bbcace7821d9