Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
tensorflow.Tensor has different methods depending on where you call it from. The documentation describes what it looks like from regular Python and asyncio events, but specifically from the dataset loading pipeline it has a completely different shape that isn't documented anywhere. The class is still called tensorflow.Tensor though.
-
@WildOrangutan I would agree, if the damn linter had found ONE error
-
@lorentz That's one of the many reasons I only use TF from C. Never from Python
Related Rants
It all makes sense now...
Here's the description of java.lang.NoSuchMethodError from https://developer.android.com/refer...
"...Normally, this error is caught by the compiler; this error can only occur at run time if the definition of a class has incompatibly changed."
Now, what are the chances of your app crashing on customer's device because of this, when calling an OS function, VibrationEffect.createPredefined(VibrationEffect.EFFECT_DOUBLE_CLICK)? In my case, it's 50/50. Lesson learned Google. try{}catch{} around every line of code from now on to deal with your stupidity.
rant
kotlin
wearos
android
google
java