Skip to content
This repository has been archived by the owner on Dec 26, 2022. It is now read-only.

feat(endpoint): Handling transaction when error occurred #574

Open
splasky opened this issue Apr 20, 2020 · 1 comment
Open

feat(endpoint): Handling transaction when error occurred #574

splasky opened this issue Apr 20, 2020 · 1 comment
Labels
A-endpoint Area - Endpoint of tangle-accelerator C-feature Category - feature P-high Priority - High, important issues or features

Comments

@splasky
Copy link
Contributor

splasky commented Apr 20, 2020 •
edited
Loading

The endpoint should handle the transaction error occurred.
The error may be occurred by the following:

  • Signal interrupt
  • Errors when connect to TA
  • Power down
  • Some other hardware errors
@splasky splasky added C-feature Category - feature A-endpoint Area - Endpoint of tangle-accelerator labels Apr 20, 2020
@splasky splasky mentioned this issue Apr 20, 2020
Closed
@splasky splasky added P-medium Priority - Medium, not hurry but needed P-high Priority - High, important issues or features and removed P-medium Priority - Medium, not hurry but needed labels May 15, 2020
@splasky splasky self-assigned this Jun 1, 2020
@splasky splasky changed the title feat(endpoint): Add data preprocessing function pointer feat(endpoint): Handling transaction when error occurred Aug 24, 2020
@splasky
Copy link
Contributor Author

splasky commented Aug 24, 2020

I think the message queue can solve this problem, the process show as following:
Untitled Diagram

@splasky splasky removed their assignment Sep 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
A-endpoint Area - Endpoint of tangle-accelerator C-feature Category - feature P-high Priority - High, important issues or features
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@splasky