-
Notifications
You must be signed in to change notification settings - Fork 123
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
Failed Curl Request in Cicero-server package #742
Comments
Thanks for the bug report - looks great. Would you like to submit a PR to fix the docs? |
Yes I would love to work. |
K-Kumar-01
added a commit
to K-Kumar-01/cicero
that referenced
this issue
May 25, 2022
Signed-off-by: Kushal Kumar <[email protected]>
5 tasks
mttrbrts
pushed a commit
that referenced
this issue
May 26, 2022
Signed-off-by: Kushal Kumar <[email protected]>
mehmettokgoz
pushed a commit
to mehmettokgoz/cicero
that referenced
this issue
Sep 24, 2022
… (accordproject#743) Signed-off-by: Kushal Kumar <[email protected]> Signed-off-by: Mehmet Tokgöz <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report 🐛
Currently, the request for
draft
andtrigger
mentioned in the documentation forcicero-server
is failing.Screenshots
Expected Behavior
The requests should pass without any error and result in a successful execution with status code 200.
Current Behavior
The error displayed in the above image is shown. Cross-checking with cicero-cli on same data gave the same error.
The data passed in the documentation seems to be incorrect.
Possible Solution
Update the documentation to use proper data.
Sample data for proper
draft
request.Steps to Reproduce
Context (Environment)
Desktop
Detailed Description
Data Passed:
Proposed Data:
Here, on seeing we find that
buyer
andseller
both are passed as objects in the former request and strings in the latter one.This is what is creating this issue.
Possible Implementation
Updating the documenation should work.
Would you like to work on the issue?
Yes
The text was updated successfully, but these errors were encountered: