-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
PriceOracle: rippled returns inconsistent error codes with invalid inputs under different situations #4962
Comments
There are different levels of validation. Some validation happens by a low layer validation, before the feature (Transactor or API) receives the parameters and then another validation happens in the feature code. The first |
Rippled returns different error codes for invalid inputs under different situations. Following is the list of such fields:
OracleSet:
""
,1
,"Invalid"
,([{}])
,[{"PriceDataSeries": ""}]]
None
,([])
None
,0
,-1
,1
,1.2
,"Invalid"
None
,0
,-1
,1
,1.2
,"Invalid"
""
""
,"020382A62402D2357ABC020382A6240205"
None
,0
,-1
,1
,1.2
,"Invalid"
Oracle GET (using
ledger_entry
method call):""
,"Invalid"
,-1
None
,1.2
1.2
to int1
.Get Aggregate Price (using
get_aggregate_price
method call):""
,-1
,"abc"
None
The text was updated successfully, but these errors were encountered: