View source for Talk:Omni

1.9.2.5 has a known bug with lambdas which has already been fixed in 1.9.2.6

currently 1.9.2.5 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 1.9.2.6+ 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.

Yes, method references and lambdas are the same thing in JVM

Oops, it seems that roborumble client cannot download your bot, from all over the world. Maybe dropbox set the restriction, or there may be some bug in any of the ends.

And after downloading your bot manually, roborumble client throws exception and exits completely.

Best I can tell is something happened during upload/download of this version. I've downgraded to 1.9.2.5 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.

And if an emety file breaks roborumble/robocode engine completely , another bug fix is waiting...

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.

Then it should be roborumble bug. I will submit a pr later