Skip to content
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

Automatic Network Downloading temporarily broken... #268

Open
featurecat opened this issue Jun 1, 2018 · 6 comments
Open

Automatic Network Downloading temporarily broken... #268

featurecat opened this issue Jun 1, 2018 · 6 comments
Labels
bug Something isn't working

Comments

@featurecat
Copy link
Owner

It looks like the page which I used for network detection (http://zero.sjeng.org/network-profiles) changed its syntax just as we released Lizzie 0.5. So currently, Lizzie cannot decipher the new format, so it can't detect when it needs to download a new network. This will be fixed for the next version of Lizzie...

@featurecat featurecat added the bug Something isn't working label Jun 1, 2018
@WYVYW
Copy link

WYVYW commented Jun 2, 2018

I doubt that they did this on purpose, but it would be great if we could support Leela more.
possible ways:

  • including autogtp while using lizzie as sort of screensaver instead of leela-watcher
  • asking to start autogtp (in background) when closing lizzie
  • or sort of nag-screen after closing (until autogtp is implemented)

@bittsitt
Copy link
Contributor

bittsitt commented Jun 2, 2018

Hmm.. Changing the config name from weights to network-file is not good. Should at least delete old unused parameters. Leelaz just crahsed on startup because network.gz was missing (but there is absolutely no warning, we need to add a warning in lizzie, I had to print debug to find out what was going on, a normal user is just stuck. My config file showed that weights pointed to the correct weights, so I didn't suspect that was the problem). If we change config param names, we should have a good reason to do so, and if we do, we should migrate the old (working) config file instead of replacing it with a non-working one. These kind of issues can really annoy a user. If we want to more users, we need to make everything smoother, not more difficult..

@roy7
Copy link

roy7 commented Jun 3, 2018

Whoops, could you post an issue on server github if something like this happens again? I don't think we had any idea you were using network-profiles for that.

Is there a way to just check things like timestamp and file size of best-network.gz for changes?

You can also use the http://zero.sjeng.org/best-network-hash endpoint to get the official best network hash at any time. If it doesn't match the hash of the best network you're currently using, then you know to download best-network.gz again.

@featurecat
Copy link
Owner Author

oh I didn't know we had a hash url. that's exactly what I wanted. thanks!

@roy7
Copy link

roy7 commented Jun 3, 2018

Cool then we're set. :) The network-profiles and various other web interface are all under construction atm and not 100% safe to use for unintended purposes. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants
@roy7 @featurecat @bittsitt @WYVYW and others