forked from aptos-labs/aptos-core
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[address32]update create account move script and faucet
Closes: aptos-labs#352
- Loading branch information
Showing
62 changed files
with
298 additions
and
447 deletions.
There are no files selected for viewing
19 changes: 6 additions & 13 deletions
19
api/goldens/aptos_api::tests::accounts_test::test_account_modules.json
Large diffs are not rendered by default.
Oops, something went wrong.
19 changes: 6 additions & 13 deletions
19
api/goldens/aptos_api::tests::accounts_test::test_account_modules_structs.json
Large diffs are not rendered by default.
Oops, something went wrong.
19 changes: 6 additions & 13 deletions
19
api/goldens/aptos_api::tests::accounts_test::test_get_module_aptos_config.json
Large diffs are not rendered by default.
Oops, something went wrong.
19 changes: 6 additions & 13 deletions
19
api/goldens/aptos_api::tests::accounts_test::test_get_module_with_script_functions.json
Large diffs are not rendered by default.
Oops, something went wrong.
2 changes: 1 addition & 1 deletion
2
...alid_post_request_test::test_invalid_script_function_argument_hex_encoded_bytes_type.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
{ | ||
"code": 400, | ||
"message": "invalid request body: invalid UserTransactionRequest: parse arguments[1] failed, expect string<hex>, caused by error: invalid type: map, expected a string" | ||
"message": "invalid request body: invalid UserTransactionRequest: expected 1 arguments [string<address>], but got 2 ([String(\"0x00000000000000000000000001234567\"), Object({})])" | ||
} |
2 changes: 1 addition & 1 deletion
2
...::tests::invalid_post_request_test::test_invalid_script_function_argument_hex_string.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
{ | ||
"code": 400, | ||
"message": "invalid request body: invalid UserTransactionRequest: parse arguments[1] failed, expect string<hex>, caused by error: decode hex-encoded string(\"0xZZZ\") failed, caused by error: Odd number of digits" | ||
"message": "invalid request body: invalid UserTransactionRequest: expected 1 arguments [string<address>], but got 2 ([String(\"0x00000000000000000000000001234567\"), String(\"0xZZZ\")])" | ||
} |
2 changes: 1 addition & 1 deletion
2
...ptos_api::tests::invalid_post_request_test::test_invalid_script_function_function_id.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
{ | ||
"code": 400, | ||
"message": "Request body deserialize error: invalid script function id \"invalid\" at line 1 column 363" | ||
"message": "Request body deserialize error: invalid script function id \"invalid\" at line 1 column 294" | ||
} |
2 changes: 1 addition & 1 deletion
2
...ns/aptos_api::tests::invalid_post_request_test::test_invalid_type_argument_data_type.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
{ | ||
"code": 400, | ||
"message": "Request body deserialize error: deserialize Move type failed, invalid type: boolean `true`, expected a string at line 1 column 393" | ||
"message": "Request body deserialize error: deserialize Move type failed, invalid type: boolean `true`, expected a string at line 1 column 324" | ||
} |
2 changes: 1 addition & 1 deletion
2
.../aptos_api::tests::invalid_post_request_test::test_missing_script_function_arguments.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
{ | ||
"code": 400, | ||
"message": "invalid request body: invalid UserTransactionRequest: expected 2 arguments [string<address>, string<hex>], but got 1 ([String(\"0\")])" | ||
"message": "invalid request body: invalid UserTransactionRequest: parse arguments[0] failed, expect string<address>, caused by error: invalid account address \"0\"" | ||
} |
25 changes: 9 additions & 16 deletions
25
...ptos_api::tests::transactions_test::test_get_transactions_output_genesis_transaction.json
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
208 changes: 98 additions & 110 deletions
208
...ns_test::test_get_transactions_returns_last_page_when_start_version_is_not_specified.json
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.