Fixed
Status Update
Comments
fi...@gmail.com <fi...@gmail.com> #2
mk...@google.com <mk...@google.com> #3
I have filed your feature request to our product team. However, there is no guarantee that this feature will be implemented, and the ETA cannot be provided. Rest assured that your feedback is always taken into account, as it allows us to improve the platform.
Any future updates to this feature will be posted here.
Any future updates to this feature will be posted here.
hq...@gmail.com <hq...@gmail.com> #4
Thank you very much!
mk...@google.com <mk...@google.com> #5
That is a pre-requirement to be able to switch from container-vm to COS on our side too.
hq...@gmail.com <hq...@gmail.com> #6
+1 show stopper.
xfs is officially recommended by MongoDB, Cassandra and Kafka:
https://docs.mongodb.com/manual/administration/production-notes/#kernel-and-file-systems
https://kafka.apache.org/documentation/#filesystems
http://docs.datastax.com/en/landing_page/doc/landing_page/planning/planningHardware.html#planningHardware__extened-file-sys
xfs is officially recommended by MongoDB, Cassandra and Kafka:
fi...@gmail.com <fi...@gmail.com> #7
+1
mk...@google.com <mk...@google.com> #8
+1 critical for production MongoDB
ap...@google.com <ap...@google.com> #9
+1 needed for GlusterFS & Heketi on GKE to provide dynamic provisioned persistent gluster storage (heketi uses XFS, and as it's mainly developed by Red Hat engineers & as it works fine on OpenShift, I can't see any reason for heketi to alter their code).
mk...@google.com <mk...@google.com> #11
There are no immediate plans to support XFS on COS. However, for GKE, we have an Ubuntu image available as an alpha feature, soon to be beta in the coming weeks. The Ubuntu image should have the XFS packages available. So please reach out to your support representative if you would like to be part of the alpha program.
fi...@gmail.com <fi...@gmail.com> #13
According to the docs on this page, it shows that COS does support xfs. Is that new or is that just inaccurate documentation?
https://cloud.google.com/kubernetes-engine/docs/node-images
mk...@google.com <mk...@google.com> #14
+1 for XFS support. Need this for glusterfs.
Description
I have been having an issue dealing with R8/obfuscation with an Android library written in Kotlin.
Below is the sample code
Similar to above, I've a public API method which is annotated with
@JvmStatic
and that method takes a Lambda as parameter.When I release the library without
minification
, everything is fine and calling code (from app side) written inJava
andKotlin
can call this method and works as expected.Now if I enable
minification
and call same method from a demo app then I get a crashing error with message similar to belowWhat have I tried ?
@Jvmstatic
resolves the issue but it created ugly Java calling code as I would have to call likeMyApi.INSTANCE.setCallback()
@Jvmstatic
but removedLambda
by converting Lambda into anInterface with one method
and everything is working fine. UnfortunatelySAM for Kotlin classes
is not there yet, so callingKotlin
code looks ugly thenR8
via setting these lines ingradle.properties
which forcefully enabledProguard
and then everything work with both@Jvmstatic
andLambda
So my last try confirms that this problem has something to do with
R8
.Would you please help me out with this ?
Whether it's something wrong on my side as incorrect use of
R8
or it's genuineR8
bug ? I don't know.I posted ahttps://stackoverflow.com/questions/62249685/dealing-with-r8-jvmstatic-annotation-lambda-in-public-api-for-android-librar
Stackoverflow
question with same details here: