I’ve submitted a few versions of my bot via the automated submission flow. If I look at the status on the player portal, the submission and build phases were successful, but all the matches failed. The bot logs and game runner logs are both empty.
Can anyone give me some insight into why this is happening? Is my bot broken somehow?
You changed the finalName in your pom.xml from JavaBot to BottyMcBotface. Thus changing the jar’s name that gets created by the maven build process. Which causes the error above
Thanks for the update. I tried to run it through the manual submission process last night, but I was getting timeouts trying to access the player portal.
Can I still compete in this tournament? I know the engine works differently this year, but my final JAR file name has been “BottyMcBotface.jar” for every challenge over the past couple of years. I don’t recall anything in the docs stating that the final JAR requires a specific name and that that won’t work anymore. It works fine if run the game engine locally, but I don’t use the Docker file - I just run it via the run.sh script.
So there are no limitations to what you can name your bot.jar if you can make it run on our infrastructure. i.e working with the Dockerfile.
And we don’t believe this needs to be outlined in the docs as it was mentioned that “playing around” with default configs will typically end up with erroneous responses.
The team feels there was ample time to resolve this issue before the deadline, so unfortunately your bot will not make it into the first tournament. However there we will be rolling out friendly tournaments soon and so you will have a chance to compete against other players ahead of tournament 2.
Thank you for still being a valued member of the Entelect Challenge.
I’ve tried to rectify the issue and I’ve submitted a new version of my bot. However, I can no longer see my submissions on the player portal. It seems to be coming back with an HTTP 500 response.
Riaan, since midnight on 1 May when I visit the submission page I only get the spinning hamster wheel. They probably closed it while the competition is running.
Good evening @marvijo. We did not forget about you. I did investigation into your bot and saw that your namespace is different from what the Dockerfile expects.
Your namespace is MarvijoBot.Galaxio, which will produce a MarvijoBot.Galaxio.dll when it’s built during the build process.
In your Dockerfile, the entrypoint is as follows: ENTRYPOINT ["dotnet", "ReferenceBot.dll"].
That command will look for a file called ReferenceBot.dll to run your bot. Since yours is called MarvijoBot.Galaxio.dll, it’s not finding the correct file.
To fix your submission, you will just need to change the entrypoint command from ENTRYPOINT ["dotnet", "ReferenceBot.dll"] to ENTRYPOINT ["dotnet", "MarvijoBot.Galaxio.dll"].
That will enable Docker to run the correct file to run your bot on our system.
Happy coding! And thank you for participating this year as well!
Something weird is happening on my submission again. Now that the issue with the game engine and Java bots has been fixed, I can run my bot locally.
As soon as I upload it to the portal and it runs a test match on there, it registers with the runner and then crashes. I’ve wrapped try/catch statements around my code to try and get an idea of what’s going wrong, but I can’t see anything more in the logs than the below.
{"date":"2021-06-02T19:16:51.559816Z","log":"[OkHttp http://192.168.17.55:5000/...] INFO com.microsoft.signalr.WebSocketTransport - WebSocket transport connected to: ws://192.168.17.55:5000/runnerhub?id=SgwH9tFXoB6nTVH3hoOj2A."}
{"date":"2021-06-02T19:16:51.619807Z","log":"[OkHttp http://192.168.17.55:5000/...] INFO com.microsoft.signalr.HubConnection - HubConnection started."}
{"date":"2021-06-02T19:16:52.626989Z","log":"Registering with the runner..."}
{"date":"2021-06-02T19:16:52.698220Z","log":"Registered with the runner 5e588483-5a04-4fb6-a11f-70f0f6bb4fab"}
{"date":"2021-06-02T19:22:55.998515Z","log":"[OkHttp http://192.168.17.55:5000/...] ERROR com.microsoft.signalr.OkHttpWebSocketWrapper - WebSocket closed from an error: null."}
{"date":"2021-06-02T19:22:55.998647Z","log":"[OkHttp http://192.168.17.55:5000/...] INFO com.microsoft.signalr.WebSocketTransport - WebSocket connection stopping with code null and reason 'null'."}
{"date":"2021-06-02T19:22:55.998718Z","log":"[OkHttp http://192.168.17.55:5000/...] INFO com.microsoft.signalr.HubConnection - HubConnection stopped."}