Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

bundle is not fully broadcasted #2414

Closed
Thoralf-M opened this issue Dec 22, 2019 · 0 comments · Fixed by #2486
Closed

bundle is not fully broadcasted #2414

Thoralf-M opened this issue Dec 22, 2019 · 0 comments · Fixed by #2486
Assignees
Labels
T - Bug Type - Bug: Something isn't working

Comments

@Thoralf-M
Copy link
Member

Bug description

Trinity doesn't always broadcast the full bundle, I've seen this twice before with bundles from other people

Environment Specs

  • OS version: Win 10
  • Trinity version: v1.2.0

Steps To Reproduce

  1. Send a transaction
  2. ?

Expected behaviour

Trinity should rebroadcast the bundle or reattach it with the data stored in the state if I do a manual sync or click on retry

Actual behaviour

Bundle doesn't get fully broadcasted
https://thetangle.org/transaction/NWPKBHAKJDUMNRXBSEUVXJKCMDH9KFTJCSUIXXPSN9AAXLETNREANUZBG9HGPNSRMIUDXYSMBHBD99999

Manual sync, automatic node management and manual retry doesn't help

I sent the full bundle manually with the info in the exported state, that's why it's confirmed

Errors

Invalid Bundle provided
Transaction is inconsistent. Reason: tails are not solid (missing a referenced tx): NWPKBHAKJDUMNRXBSEUVXJKCMDH9KFTJCSUIXXPSN9AAXLETNREANUZBG9HGPNSRMIUDXYSMBHBD99999

@Thoralf-M Thoralf-M added the T - Bug Type - Bug: Something isn't working label Dec 22, 2019
cvarley100 pushed a commit that referenced this issue Jan 20, 2020
* hotfix: rebroadcast trytes if an error "Transaction is inconsistent" occurs

See: #2414 & https://github.com/iotaledger/iri/issues

* fix: ignore existing transaction hashes when transactions diff is computed

* hotfix: do not check consistency if tail is already above max depth
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
T - Bug Type - Bug: Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants