[ https://issues.apache.org/jira/browse/CURATOR-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kezhu Wang reassigned CURATOR-675: ---------------------------------- Assignee: Kezhu Wang > AsyncStage could stuck from completion due to framework level error listener > ---------------------------------------------------------------------------- > > Key: CURATOR-675 > URL: https://issues.apache.org/jira/browse/CURATOR-675 > Project: Apache Curator > Issue Type: Improvement > Components: Framework > Affects Versions: 5.5.0 > Reporter: Kezhu Wang > Assignee: Kezhu Wang > Priority: Major > Fix For: 5.6.0 > > > {{AsyncCuratorFrameworkDsl AsyncCuratorFramework.with(UnhandledErrorListener > listener)}} can be used to construct a new framework level object with a > global-like error listener. I may be ok for a operation level error > listener(e.g. {{ErrorListenerPathable}}) to swallow exception from > {{BackgroundCallback}} but it is too crude to swallow exceptions in global > level. > The call chain is similar to > {{async.with(listener).create().forPath("/foo")}}. From this, I don't think > we are binding an error listener for {{create()}} only. > Besides this, I think it is a good to complete {{CompletableFuture}} in all > cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)