-
Notifications
You must be signed in to change notification settings - Fork 618
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
sendAsync method result response formatted #3996
sendAsync method result response formatted #3996
Conversation
this.request(args, chain) | ||
.then((response) => callback(null, response)) | ||
.catch((error) => callback(error, undefined)); | ||
.then((response) => callback(null, formatJsonRpcResult(id, response))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.then((response) => callback(null, formatJsonRpcResult(id, response)))
Do we need to format the response here? Afaik all responses are already formatted as jsonRpcResult
by the responding client
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the client is not responding in a formatted manner
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ganchoradkov, Facing the same issue while running these test cases on the main branch, please check it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please make sure you run
npm i
in root to fetch new packagesnpm run reset
to rebuild the monorepo
for some reason the relay is rejecting your jwt and/or projectId
also your system's datetime as jwt is valid for 1 day so if you datetime is forward/back in time might cause it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @ganchoradkov, I tried that also and ran it in a local file but it gave the same error. For passing the test case there might be a change in the workflow file of the repo where it is not getting environment variables correctly.
If possible can I DM you on Discord or any other platform to resolve this issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@GanchoRadkov
on telegram
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ganchoradkov, can you please tell me where you set environment variables?
in workflow file:
https://github.com/WalletConnect/walletconnect-monorepo/actions/runs/7084385293/workflow?pr=3996
Because I run test cases locally and it's running properly. and facing issue here only.
In the universal provider's test file ( walletconnect-monorepo/providers/universal provider/test/shared/constant.ts), If I put my project ID and relay id directly, it passes all test cases. for getting the environment variable it failed test cases. This is run while I define my project ID directly to a constant file please check it @ganchoradkov |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for fixing @kr-nikunj 💯 🥇
Description
fixed JSON RPC response in specific format, issue: #3984
Type of change
How has this been tested?
Using manually testing of logs and and running the test file
Use this table template to show examples of your changes:
Checklist