• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

trufflesuite / ganache-core / 2093 / 3
83%
develop: 83%

Build:
DEFAULT BRANCH: develop
Ran 30 Apr 2019 09:18PM UTC
Files 34
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

30 Apr 2019 09:08PM UTC coverage: 81.719% (+0.02%) from 81.702%
2093.3

push

travis-ci

web-flow
Fix forked `debug_traceTransaction` (#420)

This fixes the following issues:

* Web3 treats block numbers stored as hex as block hashes.

* When tracing a transaction we need to make sure the forked trie is block-number aware.

* Ensure addresses and keys are encoded properly before sending to the main node, or we may get an error back if the hex representation needs to be padded with a 0..

* When tracing a transaction the VM may ask for block by passing in a Buffer of the number instead of a hex string. Handle both.

* Don't even let the vm try to flush the a traced transaction's block's internal _cache to the stateTrie. When forking, some of the data that the traced function may request will exist only on the main chain. Because we pretty much lie to the VM by telling it we DO have data in our Trie, when we really don't, it gets lost during the commit phase when it traverses the "borrowed" data's trie (as it may not have a valid root). Because this is a trace, and we don't need to commit the data, duck punching the flush method (the simplest method I could find) is fine. Remove this and you may see the infamous Uncaught TypeError: Cannot read property 'pop' of undefined error!

892 of 1236 branches covered (72.17%)

Branch coverage included in aggregate %.

2492 of 2905 relevant lines covered (85.78%)

950.31 hits per line

Source Files on job 2093.3
  • Tree
  • List 0
  • Changed 26
  • Source Changed 3
  • Coverage Changed 26
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 764
  • Travis Job 2093.3
  • 8ad1ab29 on github
  • Prev Job for on develop (#2076.1)
  • Next Job for on develop (#2095.2)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc