Skip to content
Please note that GitHub no longer supports Internet Explorer.

We recommend upgrading to the latest Microsoft Edge, Google Chrome, or Firefox.

Learn more
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

eth-watcher fail #2099

Closed
kennyrowe opened this issue Dec 14, 2019 · 18 comments
Closed

eth-watcher fail #2099

kennyrowe opened this issue Dec 14, 2019 · 18 comments

Comments

@kennyrowe
Copy link

@kennyrowe kennyrowe commented Dec 14, 2019

Getting eth-watcher failed when booting a new ship for the first time. Not able to connect to the network.

Using current version 0.10.1
%base-hash 0v1m.7thj6.bt9f0.kecmn.psn12.t5nic.mev4p.oe12v.erhcb.b9ddc.of4bg

eth-watcher failed; will retry
%build-thread-error
ford: %core on /~dalten/home/0/ted/eth-watcher/hoon failed:
%plan failed: 
ford: %core on /~dalten/home/0/lib/ethio/hoon failed:
ford: %plan failed: 
ford: %ride failed to compute type:
ford: %slim failed: 
nest-fail
/~dalten/home/0/lib/ethio/hoon::[231 5].[232 58]>
/~dalten/home/0/lib/ethio/hoon::[230 3].[234 54]>
/~dalten/home/0/lib/ethio/hoon::[229 3].[234 54]>
/~dalten/home/0/lib/ethio/hoon::[228 3].[234 54]>
/~dalten/home/0/lib/ethio/hoon::[227 3].[234 54]>
/~dalten/home/0/lib/ethio/hoon::[10 1].[235 3]>
/~dalten/home/0/lib/ethio/hoon::[7 1].[235 3]>
/~dalten/home/0/lib/ethio/hoon::[5 1].[235 3]>
/~dalten/home/0/lib/ethio/hoon::[4 1].[235 3]>
/~dalten/home/~2019.12.14..21.18.23..b533/sys/vane/ford:<[4.828 18].[4.828 59]>
@kennyrowe

This comment has been minimized.

Copy link
Author

@kennyrowe kennyrowe commented Dec 14, 2019

> +trouble
[ [%base-hash 0v1m.7thj6.bt9f0.kecmn.psn12.t5nic.mev4p.oe12v.erhcb.b9ddc.of4bg]
  [%home-hash 0v1m.7thj6.bt9f0.kecmn.psn12.t5nic.mev4p.oe12v.erhcb.b9ddc.of4bg]
  [%our ship=~dalten point='9632' life=[~ 1] rift=[~ 1]]
  [%sponsor ship=~ten point='160' life=[~ 4] rift=[~ 1]]
  [%dopzod ship=~dopzod point='4608' life=~ rift=~]
  "Compare lifes and rifts to values here:"
  "https://etherscan.io/address/azimuth.eth#readContract"
  "  life - getKeyRevisionNumber"
  "  rift - getContinuityNumber"
  ~
]
@pimato

This comment has been minimized.

Copy link

@pimato pimato commented Dec 14, 2019

@faso

This comment has been minimized.

Copy link

@faso faso commented Dec 14, 2019

Same thing here

@mclucario

This comment has been minimized.

Copy link

@mclucario mclucario commented Dec 15, 2019

Same here.

@ngzax

This comment has been minimized.

Copy link

@ngzax ngzax commented Dec 16, 2019

same. i am getting lots of eth-watcher fails on both my planet and star.

@vvisigoth

This comment has been minimized.

Copy link
Contributor

@vvisigoth vvisigoth commented Dec 16, 2019

@philipcmonk @belisarius222 do we need these piers or do we have a lead on this bug ?

@matildepark

This comment has been minimized.

Copy link
Member

@matildepark matildepark commented Dec 16, 2019

@kennyrowe

This comment has been minimized.

Copy link
Author

@kennyrowe kennyrowe commented Dec 16, 2019

I tried a few experiments trying to restore older versions of ethio.hoon and eth-watcher.hoon but that didn't work. Might try and just remove the last commit to eth-watcher that added a nonce function.

@philipcmonk

This comment has been minimized.

Copy link
Contributor

@philipcmonk philipcmonk commented Dec 16, 2019

This solves it for me: [edited]

|wipe-ford 100
|start %goad
:goad %go

I'll push a fixed pill soon which will fix this for new people. People who booted into this broken state should run the above two commands.

This is a ford cache problem. @belisarius222, why doesn't ford recognize that a change to zuse should invalidate its cache? Why doesn't it throw away it's cache when it gets reloaded? Also, why doesn't ford say that all apps depend on zuse/arvo/hoon?

@pimato

This comment has been minimized.

Copy link

@pimato pimato commented Dec 16, 2019

@philipcmonk

This comment has been minimized.

Copy link
Contributor

@philipcmonk philipcmonk commented Dec 16, 2019

whoops, needs a percent argument. How about this:

|wipe-ford 100
|start %goad
:goad %go
@kennyrowe kennyrowe closed this Dec 17, 2019
@belisarius222

This comment has been minimized.

Copy link
Contributor

@belisarius222 belisarius222 commented Dec 17, 2019

@philipcmonk

This comment has been minimized.

Copy link
Contributor

@philipcmonk philipcmonk commented Dec 17, 2019

has it ever been the case that changing zuse.hoon caused all your apps to reload? If that's supposed to have been happening, then it's been a bug this whole time

@belisarius222

This comment has been minimized.

Copy link
Contributor

@belisarius222 belisarius222 commented Dec 17, 2019

philipcmonk added a commit that referenced this issue Dec 17, 2019
See #2099.
@philipcmonk

This comment has been minimized.

Copy link
Contributor

@philipcmonk philipcmonk commented Dec 17, 2019

adding %wipe 100 to goad crashes in ford on line 1791, probably on rebuilding the apps. If I take away the !. in ++reduce, the crash is on the ?< in +apply-blocks.

@belisarius222

This comment has been minimized.

Copy link
Contributor

@belisarius222 belisarius222 commented Dec 17, 2019

@joemfb

This comment has been minimized.

Copy link
Member

@joemfb joemfb commented Dec 17, 2019

I think crashes in %drip updates from %clay invalidate those kinds of assumptions.

@belisarius222

This comment has been minimized.

Copy link
Contributor

@belisarius222 belisarius222 commented Dec 17, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
10 participants
You can’t perform that action at this time.