Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Rewrite 4.x] IPC Provider #4642

Closed
8 of 9 tasks
nazarhussain opened this issue Dec 17, 2021 · 5 comments
Closed
8 of 9 tasks

[Rewrite 4.x] IPC Provider #4642

nazarhussain opened this issue Dec 17, 2021 · 5 comments
Labels
4.x 4.0 related Epic

Comments

@nazarhussain
Copy link
Contributor

nazarhussain commented Dec 17, 2021 •
edited by mconnelly8
Loading

( This is Epic for 4.x Management )

IPC Provider

IPC Provider is used to send RPC calls over Unix Socket

Related Issues / Feature Requests / Discussion

Dependencies / Related Modules

Documentation

  • README ( overview, one code snippet example, .. )
  • IPC Provider documentation ( Integrated with BaseProvider, have an example snippet )

Related Issues

Test and add support of retry and auto reconnect features in IPC provider
@nazarhussain nazarhussain mentioned this issue Dec 17, 2021
Closed
@nazarhussain nazarhussain added the 4.x 4.0 related label Dec 17, 2021
@jdevcs
Copy link
Contributor

jdevcs commented Jan 4, 2022

For future if Epic is already there kindly use same Epic and update its description. @nazarhussain @mconnelly8
This saves time in zenhub as well.

@nazarhussain
Copy link
Contributor Author

@jdevcs Definitely, but creating such empty epics way earlier endup not knowing which of issues are already created and are in backlog. So for better time saving, we must create and plan the foreseeable future.

@mconnelly8 mconnelly8 reopened this Jan 10, 2022
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment.

@github-actions github-actions bot added the Stale Has not received enough activity label Mar 12, 2022
@jdevcs jdevcs removed the Stale Has not received enough activity label Mar 21, 2022
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment.

@github-actions github-actions bot added the Stale Has not received enough activity label May 21, 2022
@mconnelly8 mconnelly8 removed the Stale Has not received enough activity label May 24, 2022
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment.

@github-actions github-actions bot added the Stale Has not received enough activity label Jul 24, 2022
@mconnelly8 mconnelly8 removed the Stale Has not received enough activity label Jul 26, 2022
@jdevcs jdevcs closed this as completed Aug 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
4.x 4.0 related Epic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nazarhussain @jdevcs @mconnelly8