Skip to content
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

updated icatx docs #148

Merged
merged 30 commits into from
Feb 8, 2024
Merged

updated icatx docs #148

merged 30 commits into from
Feb 8, 2024

Conversation

swelf19
Copy link
Contributor

@swelf19 swelf19 commented Jan 24, 2024

docs/neutron/modules/contract-manager/overview.md Outdated Show resolved Hide resolved
docs/neutron/modules/interchain-txs/overview.md Outdated Show resolved Hide resolved
docs/neutron/modules/interchain-txs/overview.md Outdated Show resolved Hide resolved
docs/neutron/modules/interchain-txs/overview.md Outdated Show resolved Hide resolved
docs/neutron/modules/interchain-txs/overview.md Outdated Show resolved Hide resolved

## Failed interchain txs

Not every interchaintx executes succesfully on a remote network. Some of them fails to execute with errors and then you get ibc acknowledgement with `Error` type. In this case, in order to get additional details about the transaction parameters as well as details about the error, you can use the commands `<binary> q interchain-accounts host packet-events <channel-id> <seq-id>`
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<binary> q interchain-accounts host packet-events <channel-id> <seq-id>

Let's say <binary> must be replaces with a binary of a remote chain

- `channel-id` is the id of the channel on the host side of the interchain accounts
- `seq-id` - seq of the ibc message received on the host

For example `gaiad q interchain-accounts host packet-events channel-736 1` is a transaction `fund community pool from neutron unclaimed airdrop` on `cosmoshub-4` chain. Because this command is just an alias for the transaction search functionality, it searches for the transaction using the following keys `recv_packet.packet_dst_channel = <channel-id> AND recv_packet.packet_dst_port = <port> AND recv_packet. packet_sequence = <seq-id>`. The node you are accessing may not have this transaction, due to the fact that it was included in the block a long time ago and it has already been removed by the pruning procedure.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it a real tx on a mainnet? Let's add an rpc here, so a user can copypast the command and that's it


For example `gaiad q interchain-accounts host packet-events channel-736 1` is a transaction `fund community pool from neutron unclaimed airdrop` on `cosmoshub-4` chain. Because this command is just an alias for the transaction search functionality, it searches for the transaction using the following keys `recv_packet.packet_dst_channel = <channel-id> AND recv_packet.packet_dst_port = <port> AND recv_packet. packet_sequence = <seq-id>`. The node you are accessing may not have this transaction, due to the fact that it was included in the block a long time ago and it has already been removed by the pruning procedure.

Unfortunately, to avoid the nondeterminism associated with error test generation, the error text is severely truncated by redact down to the error code without any additional details, before being saved to the state on the host interchain account side of the module.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the error text is severely truncated by redact down to the error code without any additional details

Please provide a link to the code here

docs/neutron/modules/contract-manager/client.md Outdated Show resolved Hide resolved
docs/neutron/modules/contract-manager/client.md Outdated Show resolved Hide resolved
docs/neutron/modules/contract-manager/client.md Outdated Show resolved Hide resolved
docs/neutron/modules/contract-manager/overview.md Outdated Show resolved Hide resolved
docs/neutron/modules/contract-manager/overview.md Outdated Show resolved Hide resolved
docs/neutron/modules/interchain-txs/overview.md Outdated Show resolved Hide resolved
docs/neutron/modules/interchain-txs/overview.md Outdated Show resolved Hide resolved
docs/neutron/modules/interchain-txs/overview.md Outdated Show resolved Hide resolved
docs/neutron/modules/interchain-txs/overview.md Outdated Show resolved Hide resolved
Copy link
Contributor

@sotnikov-s sotnikov-s left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changes are requested for the versioned docs. please reflect them in the current version as well

@pr0n00gler pr0n00gler merged commit 4354597 into main Feb 8, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants