I have the MaxWait setting set at 150, but from what I saw in the code is that it's only used to wait for the message. In my case the message seems to appear so I don't have any timeout error either. I though of handling the timeout myself but I'm affraid the Imagine process will keep running in the background and pile up some errors in the longterm since I don't have any way to cancel the Imagine promise.
Describe the bug
Describe the bug
Imagine doesn't throw an error in case of MidJourney failure, neither a timeout
Expected behavior
I'd expect client.Imagine(...) to throw an error if MidJourney failed on discord, or at least have some sort of timeout that would cancel the Imagine promise so I can't get a feedback on this error from Discord and handle it properly.
the code that reproduces this issue or a replay of the bug
Hello,
I use this package only for Image and Upscale. Most of the time, things a running smoothly, but I sometimes get a MidJourney error like the following:
The thing is that in this case the await Imagine(...) never returns anything and seems to stay stuck, not throwing any error:
I have the MaxWait setting set at 150, but from what I saw in the code is that it's only used to wait for the message. In my case the message seems to appear so I don't have any timeout error either. I though of handling the timeout myself but I'm affraid the Imagine process will keep running in the background and pile up some errors in the longterm since I don't have any way to cancel the Imagine promise.
Describe the bug
Describe the bug Imagine doesn't throw an error in case of MidJourney failure, neither a timeout
Expected behavior I'd expect client.Imagine(...) to throw an error if MidJourney failed on discord, or at least have some sort of timeout that would cancel the Imagine promise so I can't get a feedback on this error from Discord and handle it properly.
Screenshots
error log
No log since I don't get any error thrown