|Thread title||Replies||Last modified|
|Lambdas and 18.104.22.168||11||01:39, 18 September 2018|
22.214.171.124 has a known bug with lambdas which has already been fixed in 126.96.36.199
currently 188.8.131.52 is the only accepted roborumble and it gets
Got an error with e32.Omni: java.lang.ClassNotFoundException
You could use retrolambda to transpile lambdas as I do, or just avoid using lambdas until 184.108.40.206+ is accepted.
Ah, thanks for the heads up. I haven't explicitly used lambdas to my knowledge (though I'll check this weekend), but method references instead. I'm guessing those also cause this behavior.
Best I can tell is something happened during upload/download of this version. I've downgraded to 220.127.116.11 and 0.02 works just fine locally. I'll do some more testing and then maybe a version bump before I try again.
Maybe my manually curled version is just an empty file, since without -L it wouldn’t follow redirect and leave blank. If that’s the case, I would put 0.02 back since it’s totally fine.
Btw, can you try running your bot with robocode 18.104.22.168? And can you try running roborumble to see whether it can download your bot automatically or not?
Did you share the bot before releasing it? You can't download something from a dropbox link unless it is shared. I generally share it with myself and I haven't had any problems with Dropbox yet.
rumble client on all my machines from all over the world cannot download your bot as well, but manually run curl on the same machine is ok. I guess that’s dropbox restriction or some bug of rumble client.
If it's as simple as user vs. code, it may be that I made the link http rather than https in an attempt to mimic similar entries. Thanks for taking a look, but I'll re-submit after I've done ALL the homework next time. I'm still learning the build/deployment side of Java.