-
Notifications
You must be signed in to change notification settings - Fork 132
-
Notifications
You must be signed in to change notification settings - Fork 132
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
jcli: Add a way to get fragment_id from a posted fragment #467
Comments
dkijania
changed the title
lack of corelation betweend tx_id and fragment_id
lack of correlation between tx_id and fragment_id
Jun 12, 2019
vincenthz
changed the title
lack of correlation between tx_id and fragment_id
jcli: Add a way to get fragment_id from a posted fragment
Jun 12, 2019
dkijania
added a commit
that referenced
this issue
Jun 13, 2019
Signed-off-by: dkijania <dariusz.kijania@iohk.io>
dkijania
added a commit
that referenced
this issue
Jun 13, 2019
Signed-off-by: dkijania <dariusz.kijania@iohk.io>
dkijania
added a commit
that referenced
this issue
Jun 17, 2019
Signed-off-by: dkijania <dariusz.kijania@iohk.io>
dkijania
added a commit
that referenced
this issue
Jun 17, 2019
Signed-off-by: dkijania <dariusz.kijania@iohk.io>
dkijania
added a commit
that referenced
this issue
Jun 18, 2019
Signed-off-by: dkijania <dariusz.kijania@iohk.io>
dkijania
added a commit
that referenced
this issue
Jun 19, 2019
Signed-off-by: dkijania <dariusz.kijania@iohk.io>
This has been addressed now. The fragment ID is displayed and there is no longer distinction between fragment ID and transaction ID |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem/context ? Please describe if applicable.
If we build a transaction with some id. and successfully send it to node (via jcli message post command). There is no way to correlate it to fragment id that is available with command (jcli message logs).
Example:
tx_id of posted transaction:
991a2739bdfb2a823041e9ae35f1bb18029bcc94bb36abcedbb9ea0b65586d57
Fragment:
Describe the solution you'd like
Either fragment has a field: source_tx_id or jcli will return fragment_id after we use
message post
commandThe text was updated successfully, but these errors were encountered: