-
Notifications
You must be signed in to change notification settings - Fork 33
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
Fairy-Stockfish not working... Game aborted #136
Comments
Also another issue, it says Process Free and not Process Freed, and in the chat text messages, there is a 'b' in front of it |
Could you send me your logs after adding the -v tag? |
Has this issue been fixed? |
No, I also got the error
|
|
I don't think it is the same error, but here are a few things that could be fixed:
|
@TheYoBots I am very sorry as I am not free right now, going to sleep, will try to get back to you tomorrow morning but my schedule is pretty tight as I am busy |
@M-DinhHoangViet |
Thank you @TheYoBots , it's working properly
|
Could you send me your logs after adding the |
|
@M-DinhHoangViet |
Has this issue been fixed? I think the commits I have made take care of all the errors related to Fairy-Stockfish. |
Regarding this, it is an intentional change and I'd prefer to keep it that way.
It isn't a bug, since this client is taken from quite an old version of lichess-bot, it sends |
What if the user has concurrency on 2 or above? It will not sound right Also, I think a good change from latest lichess-bot would be the lichess bot auto logs folder, you should make that ASAP so bug reports are easier, and the user doesnt have to run the whole thing again with -v to get it |
I will work on auto-logging soon, but apart from that, I think it is extremely unlikely that both games end at the same time so I'm not sure whether I really need to change this. |
will check in 30 mins |
I opened up Lishogi-bot with Fairy-Stockfish, started my game and here is what it says:
Any idea on how to fix?
The text was updated successfully, but these errors were encountered: