Status Update
No update yet.
Comments
il...@google.com
ap...@google.com
Hello,
This report does not contain any description as the Public Issue Tracker is for reproducible issues. If it was a mistake to leave it blank please open a new Public Issue Tracker report with the description of your issue and the steps to reproduce it. Thanks!
ni...@ansman.se
I'm not sure which steps you need to reproduce. NO endpoints on Vertex display a hardware configuration used to deploy the model.
jb...@google.com
Hello,
Thank you for reporting this issue.
Could you please confirm whether the issue is still persisting on your end or not?
ni...@hinge.co
Hello,
Thank you for your engagement regarding this issue. We haven’t heard back from you regarding this issue for sometime now. Hence, I'm going to close this issue which will no longer be monitored. However, if you have any new issues, Please don’t hesitate to create a new issue on the
ap...@google.com
The issue still exist. At least, when I open the GCP console I can't see any way to understand the hardware configuration of an endpoint.
jb...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
pr...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.fragment:fragment:1.5.7androidx.fragment:fragment:1.6.0-beta01
Description
Component used: Fragment
Version used:
1.5.6If you call
Fragment.postponeEnterTransitionwith a delay,Fragmentwill post a runnable on a Handler with the specified delay as the delay. This runnable is not removed when callingstartPostponedEnterTransitionhowever which means that if the fragment is destroyed it will be retained until the runnable finally runs.You can easily verify this with LeakCanary by having two fragments where in the first fragment you call
postponeEnterTransition(1, TimeUnit.HOURS)and then you navigate to the other fragment. When leak canary runs you can see that the initial fragment is retained.The solution should be to remove the runnable when calling
startPostponedEnterTransition. This might not be feasible in the case where you callpostponeEnterTransitionbefore the fragment is attached but it feels OK to ignore that case for now.