After 7f07a6ef9ae90baee4281394d0dcf505b30c8fcb, building the ktls group doesn't work as it's not included in the #else statement. I don't have a need for ktlsa at this point.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3660
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3660(a)github.com>
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [x] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [x] PR should be backported to stable branches
- [ ] Tested changes locally
#### Description
If kamailio is in the shutdown phase proc timers should not be executed since memory objects are getting destroyed and cores could happen
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3649
-- Commit Summary --
* core: timer_proc don't execute timers on destroy_modules_phase
-- File Changes --
M src/core/timer_proc.c (19)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3649.patchhttps://github.com/kamailio/kamailio/pull/3649.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3649
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3649(a)github.com>
Module: kamailio
Branch: master
Commit: 9eeab4396d8ec57781244ab80c4a96539d7338ec
URL: https://github.com/kamailio/kamailio/commit/9eeab4396d8ec57781244ab80c4a965…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2023-11-28T10:20:41+01:00
jansson: docs updated for jansson_get_field()
---
Modified: src/modules/jansson/doc/jansson_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/9eeab4396d8ec57781244ab80c4a965…
Patch: https://github.com/kamailio/kamailio/commit/9eeab4396d8ec57781244ab80c4a965…
---
diff --git a/src/modules/jansson/doc/jansson_admin.xml b/src/modules/jansson/doc/jansson_admin.xml
index debc9cc5a19..daa5e9ea51e 100644
--- a/src/modules/jansson/doc/jansson_admin.xml
+++ b/src/modules/jansson/doc/jansson_admin.xml
@@ -56,10 +56,16 @@
<title>Functions</title>
<section id="jansson.f.jansson_get">
<title>
- <function moreinfo="none">jansson_get(key/path, src, dst)</function>
+ <function moreinfo="none">jansson_get(path, src, dst)</function>
</title>
<para>
- Copy the value at the location 'path' from the json object 'src' and store it in pvar 'dst'.
+ Copy the value at the location 'path' from the json object 'src'
+ and store it in variable 'dst'. The path can also be a simple field name
+ (a key), if it does not include any path separator. To retrieve the
+ value of a field that includes path separators in the name, use
+ jansson_get_field().
+ </para>
+ <para>
The 'src' can be a static string or a dynamic string with variables.
</para>
<para>
@@ -71,7 +77,7 @@
</para>
<para>
The function can put a string, integer, null, or new json string into destination.
- If the key/path can't be found in the JSON data structure, the pvar is not changed.
+ If the path can't be found in the JSON data structure, the pvar is not changed.
If it had a previous
value, that value remains unchanged.
</para>
@@ -280,22 +286,27 @@ jansson_xencode("a", "$var(js)");
</section>
<section id="jansson.f.jansson_get_field">
<title>
- <function moreinfo="none">jansson_get_field(src, field_name, dst)</function>
+ <function moreinfo="none">jansson_get_field(field_name, src, dst)</function>
</title>
<para>
- Copy field 'field_name' from json object 'src' and store it in pvar 'dst'.
+ Copy the value of the field 'field_name' from json object 'src'
+ and store it in pvar 'dst'. The field name is not evaluated as JSON
+ path, therefore it has a different behaviour than jansson_get() and
+ can be used when the field name contains path delimiters.
</para>
<para>
- <emphasis>This function is deprecated</emphasis> but kept for backwards compatibility.
- Right now it is just a wrapper around <function>jansson_get</function>, and its
- functionality is the same.
+ Note that till version 5.7.x, this function was similar to jansson_get(),
+ after that its behaviour changed to work as described above. Also,
+ the order of parameters changed.
</para>
<example>
<title><function>jansson_get_field</function> usage</title>
<programlisting format="linespecific">
...
-jansson_get_field("{'foo':'bar'}", "foo", "$var(foo)");
+jansson_get_field("foo", "{'foo':'bar'}", "$var(foo)");
xlog("foo is $var(foo)");
+jansson_get_field("foo.foz", "{'foo.foz':'bar.buz'}", "$var(foofoz)");
+xlog("foo.foz is $var(foofoz)");
...
</programlisting>
</example>