You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can observe from this prediction input images is not being passed to workflow somehow. Result should be an inpainted version of the image with reverse alpha. But input and output doesnt align, it uses some previous input. I guess it can be some kind of cache issue since it reverts back to normal if i force reset cache. I might be completely wrong but i think i am sending the correct file lol.
Yeah sorry about that, i forgot replicate removes them after an hour lol. My input names are unique, i use time stamps in the name. But since we use "input.webp" as the file name maybe comfy thinks they are the same image. I dont know if does or check image hash or sth, if there is even such a thing.
Here are some new predictions run on replicate directly, without force_reset_cache:
As you can see, second one still uses the input from the previous one, even though i ve passed a new image with a unique name. I guess i will update the input image field directly with the url, i was sending them with via api.
https://replicate.com/p/va6v99b9qxrmc0cmpza88bsa98
As you can observe from this prediction input images is not being passed to workflow somehow. Result should be an inpainted version of the image with reverse alpha. But input and output doesnt align, it uses some previous input. I guess it can be some kind of cache issue since it reverts back to normal if i force reset cache. I might be completely wrong but i think i am sending the correct file lol.
Here is a correct prediction. https://replicate.com/p/9jar316q59rme0cmpzbscb6mb8 Only thing i did was sending the api request a couple more times.
The text was updated successfully, but these errors were encountered: