-
Notifications
You must be signed in to change notification settings - Fork 172
Issues: paritytech/jsonrpsee
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
deps: move to cargo workspace dependencies
good first issue
Good for newcomers
#1500
opened Dec 2, 2024 by
niklasad1
TransportReceiverT::receive
should return an Option to indicate a dropped connection
#1461
opened Sep 19, 2024 by
AArnott
server: wrapping
jsonrpsee:TowerService
is a new type pattern is not possible
#1383
opened May 30, 2024 by
niklasad1
Unable to set the
id_provider
when using RpcModule::raw_json_request
#1342
opened Apr 4, 2024 by
JamesHinshelwood
Would implementing a basic support for the JsonRPC 1.0 be useful on the client?
#1312
opened Mar 5, 2024 by
YaCodesDevelopment
RpcServiceT: remove
associated type Future
and replace with impl future
#1289
opened Feb 10, 2024 by
niklasad1
Response handling on the client is very slow comparing to server
#1189
opened Aug 18, 2023 by
nazar-pc
Subscriptions just returns None (no error) - manual tokio_tungstenite works fine
#1142
opened Jun 16, 2023 by
chikko80
Response implementation of
Deserialize
is not general enough
#1106
opened May 1, 2023 by
aniketfuryrocks
[client]: make batch request easiest to understand when a too large response occurs
#1104
opened Apr 27, 2023 by
niklasad1
proc macros: client API does only work
Result<T, E
and can't be used with custom return types
#1067
opened Apr 4, 2023 by
niklasad1
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.