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

In the new JSON-RPC API, reaching the limit to number of subscriptions shouldn't lead to a JSON-RPC error #58

Closed
tomaka opened this issue Feb 9, 2023 · 1 comment
Closed

In the new JSON-RPC API, reaching the limit to number of subscriptions shouldn't lead to a JSON-RPC error #58

tomaka opened this issue Feb 9, 2023 · 1 comment

Comments

@tomaka
Copy link
Contributor

tomaka commented Feb 9, 2023

paritytech/smoldot#2773
@tomaka tomaka changed the title In the new JSONRPC API reaching the limit to number of subscriptions shouldnt lead to a JSONRPC error In the new JSON-RPC API, reaching the limit to number of subscriptions shouldnt lead to a JSON-RPC error Mar 29, 2023
@tomaka tomaka changed the title In the new JSON-RPC API, reaching the limit to number of subscriptions shouldnt lead to a JSON-RPC error In the new JSON-RPC API, reaching the limit to number of subscriptions shouldn't lead to a JSON-RPC error Mar 29, 2023
@tomaka
Copy link
Contributor Author

tomaka commented Aug 9, 2023

Closing as irrelevant after #966

@tomaka tomaka closed this as not planned Won't fix, can't repro, duplicate, stale Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomaka