[ 
https://issues.apache.org/jira/browse/TS-4664?focusedWorklogId=25984&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25984
 ]

ASF GitHub Bot logged work on TS-4664:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Jul/16 19:12
            Start Date: 25/Jul/16 19:12
    Worklog Time Spent: 10m 
      Work Description: Github user shinrich commented on a diff in the pull 
request:

    https://github.com/apache/trafficserver/pull/801#discussion_r72125568
  
    --- Diff: configure.ac ---
    @@ -49,7 +49,7 @@ AM_INIT_AUTOMAKE([-Wall -Werror -Wno-portability 
tar-ustar foreign no-installinf
     AM_MAINTAINER_MODE([enable])
     
     # Enable a recursive "tidy" rule for clang-tidy.
    -AM_EXTRA_RECURSIVE_TARGETS([tidy])
    +#AM_EXTRA_RECURSIVE_TARGETS([tidy])
    --- End diff --
    
    Sorry snuck in.  My Centos image cannot deal with this one.


Issue Time Tracking
-------------------

    Worklog Id:     (was: 25984)
    Time Spent: 2h 10m  (was: 2h)

> Crash due to separate event handlers for IO events and plugin events for 
> ClientSession
> --------------------------------------------------------------------------------------
>
>                 Key: TS-4664
>                 URL: https://issues.apache.org/jira/browse/TS-4664
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Susan Hinrichs
>            Assignee: Susan Hinrichs
>             Fix For: 7.0.0
>
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Found while tracking TS-4507 and original fix on that branch.
> Cleaned up handling regular events at the same time as plugin events. The 
> original code relied on the subclasses overriding handle_api_event to handle 
> the regular events, but the handler only handled the TIMEOUT event. Changed 
> that to augment the subclasses' main event handler to call out to 
> state_api_callout in the event of the plugin events.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to