Dan Finlay 2b7b1db851 Do not mark a retry tx failed that has been broadcast successfully ... Fixes #2115 If a tx has been braodcast, the only failures we should accept are: - Never mined - On chain failure We had a section of code that would mark a tx failed during any unknown error during a retry. Now no retry > 1 will ever mark a tx failed, since it has been broadcast, and may be mined.		2017-09-18 14:34:25 -07:00
..
migrator
auto-reload.js
buy-eth-url.js
config-manager.js
createLoggerMiddleware.js	metamask controller - move middleware into seperate files	2017-09-13 15:17:26 -07:00
createOriginMiddleware.js	createOriginMiddleware - fix var name	2017-09-13 15:29:44 -07:00
createProviderMiddleware.js	metamask controller - move middleware into seperate files	2017-09-13 15:17:26 -07:00
eth-store.js
hex-to-bn.js
inpage-provider.js	Merge branch 'master' of github.com:MetaMask/metamask-extension into filter-leak-fix	2017-09-11 14:21:09 -07:00
is-popup-or-notification.js
message-manager.js
nodeify.js
nonce-tracker.js
notification-manager.js
pending-tx-tracker.js	Do not mark a retry tx failed that has been broadcast successfully	2017-09-18 14:34:25 -07:00
personal-message-manager.js
port-stream.js
random-id.js
stream-utils.js
tx-state-history-helper.js
tx-utils.js
util.js