Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Chain connector plugin fails when no receivingChainAPIClient #8276

Closed
Tracked by #7210
ishantiw opened this issue Mar 20, 2023 · 0 comments · Fixed by #8281
Closed
Tracked by #7210

Chain connector plugin fails when no receivingChainAPIClient #8276

ishantiw opened this issue Mar 20, 2023 · 0 comments · Fixed by #8281
Assignees
@ishantiw
Labels
framework-plugins/chain_connector type: bug
Milestone
Sprint 91

Comments

@ishantiw
Copy link
Contributor

Expected behavior

Chain connector plugin should not fail and continue saving info on new block when receivingChainAPIClient is not working

Actual behavior

Chain connector plugin fails when receivingChainAPIClient is not working

Steps to reproduce

Run pos-mainchain with chain connector plugin enabled

Which version(s) does this affect? (Environment, OS, etc...)

v6.0.0-alpha.16
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ishantiw ishantiw

Labels
framework-plugins/chain_connector type: bug
Projects
None yet
Milestone
Sprint 91
Development

Successfully merging a pull request may close this issue.

Continue processing when apiClient is not working LiskArchive/lisk-sdk
1 participant
@ishantiw