[
https://issues.apache.org/jira/browse/TS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728646#comment-13728646
]
ASF subversion and git services commented on TS-2093:
-----------------------------------------------------
Commit 1bb12edf9cd9b0076eaf39b8665909846743ee73 in branch refs/heads/3.3.x from
[~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=1bb12ed ]
Merge branch 'master' into 3.3.x
* master: (295 commits)
TS-2081 Make the WCCP addr configuration LOCAL
TS-2093: Check bounds on plugin stat creation.
TS-2092 Use of uninitialized member in HdrHeap.
[TS-2052] ET_SSL thread spinning
TS-2090 Make proxy.config.allocator.enable_reclaim default based on build
instructions
TS-1006: adjust some reclaimable-freelist's default configuration
Updated newish tests to the gitignore
Fix autoconf checks for mcheck_pedantic()
Fix configure check for eventfd
TS-1330: Fix logging core at checkout_write()
add some standard extensions to ignore list
TS-1953: remove version check from stable plugins
TS-1953: Remove check_ts_version() from experimental plugins
TS-1953: remove check_ts_version() from examples
Added TS-2086.
TS-2086 Remove a few more unused configs
Added TS-1685
TS-1685 Remove TS_MICRO and fellas
Added Ts-1255
TS-1255 Fix the types for all overridable configs. This was actually a real
bug in the code, in that all float configurations were actually treated as
integer, rendering them useless
...
> Plugin API doesn't check stat bounds on creation which can cause assert to
> trigger
> ----------------------------------------------------------------------------------
>
> Key: TS-2093
> URL: https://issues.apache.org/jira/browse/TS-2093
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Phil Sorber
> Assignee: Phil Sorber
> Labels: C
> Fix For: 3.3.5
>
>
> The records created for stats for the API are limited by TS_MAX_API_STATS.
> Trying to create more than that causes an assert to trigger.
> This problem should be superseded by TS-454
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
