Status Update
No update yet.
Comments
ch...@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!
tc...@google.com
I'm not sure which steps you need to reproduce. NO endpoints on Vertex display a hardware configuration used to deploy the model.
an...@google.com
b9...@gmail.com
Hello,
Thank you for reporting this issue.
Could you please confirm whether the issue is still persisting on your end or not?
ap...@google.com
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
Description
1) We can do the whole recomposition when the items count changed as we can't change size without the recomposition
2) But we can react on item changes only for the currently visible items.
I prototyped how it can work from the compose side:
But it has quite a lot of todos where I am not sure what callbacks from Paging to be using to update the compose states. Could you please help with figuring it out?