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
Had a working demo using forge api, tried to drop in kobold for easier setup for a friend, no go. After much frustration trying to debug my side and looking for an error somewhere I finally just compared the network log of API requests. Totally my dumb fault for not sanitizing the variables going in. But if you want better parity with forge API, this would be nice. Or getting some error response would be helpful. As it is in the kobold console it says "Generate Image: The response could not be sent, maybe connection was terminated?", which is a bit misleading.
All working on my side now, so close if you think it's not worth your time, thanks for the great software.
The text was updated successfully, but these errors were encountered:
May I know how does Forge handle the unsanitized variables? Or rather, which were the fields in question? The error might be causing the generation process to be aborted which is why you see it like this.
My width, height, steps, and cfg_scale were all getting sent as strings, sloppy JavaScript. Just having them parse properly before sending corrected the problem, assume forge was doing that on the receiving side.
Had a working demo using forge api, tried to drop in kobold for easier setup for a friend, no go. After much frustration trying to debug my side and looking for an error somewhere I finally just compared the network log of API requests. Totally my dumb fault for not sanitizing the variables going in. But if you want better parity with forge API, this would be nice. Or getting some error response would be helpful. As it is in the kobold console it says "Generate Image: The response could not be sent, maybe connection was terminated?", which is a bit misleading.
All working on my side now, so close if you think it's not worth your time, thanks for the great software.
The text was updated successfully, but these errors were encountered: