You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/02/25 03:56:44 UTC
[jira] [Commented] (MYNEWT-638) Cannot reset controller if
attempting to create a connection
[ https://issues.apache.org/jira/browse/MYNEWT-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884001#comment-15884001 ]
ASF subversion and git services commented on MYNEWT-638:
--------------------------------------------------------
Commit c5c9b6e2e3f8aea74efd5ff99f7ed4334166e1c7 in incubator-mynewt-core's branch refs/heads/develop from [~wes3]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=c5c9b6e ]
MYNEWT-638: Bug when resetting controller while creating connection
This fix should address the issue where the controller was reset
while attempting to create a connection. It should now be possible
to create a connection after the reset. The bug was that a
global variable was not getting cleared which prevented
acceptance of the conn create command.
> Cannot reset controller if attempting to create a connection
> ------------------------------------------------------------
>
> Key: MYNEWT-638
> URL: https://issues.apache.org/jira/browse/MYNEWT-638
> Project: Mynewt
> Issue Type: Bug
> Components: Nimble
> Affects Versions: v1_0_0_beta2
> Reporter: William San Filippo
> Assignee: William San Filippo
> Fix For: v1_0_0_rel
>
>
> Here is the issue: if the host tells the controller to create a connection and no connection gets created, and then tells the controller to reset, the controller resets but does completely clear state. If another attempt to create a connection happens by the host, the controller denies it because it thinks it is still trying to connect.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)