-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.1.4 doesn't seem to allow generations #4
Comments
so is it broken? |
[CS Helpdesk #27663]
Think so :(
|
Okay I’m just confused because you closed the issue. Is there an error
message?
|
My bad,
My computer broke and I confused the email chains! I closed the issue because I am less confident that the cause of the problems may have been due to the update, I’ll get back to you!
… On 15 Sep 2022, at 18:48, Bryce Drennan ***@***.***> wrote:
Okay I’m just confused because you closed the issue. Is there an error
message?
On Thu, Sep 15, 2022 at 10:20 AM Aengus Lynch ***@***.***>
wrote:
> [CS Helpdesk #27663]
>
> Think so :(
>
> > On 15 Sep 2022, at 18:05, Bryce Drennan ***@***.***> wrote:
> >
> >
> > so is it broken?
> >
> > —
> > Reply to this email directly, view it on GitHub <
> #4 (comment)>,
> or unsubscribe <
> https://github.com/notifications/unsubscribe-auth/AI546UQ47AAEO7G2QJJUHNDV6NJMHANCNFSM6AAAAAAQNRXIUI
> >.
> > You are receiving this because you modified the open/close state.
> >
>
> —
> Reply to this email directly, view it on GitHub
> <#4 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAJJH67JYPQTENSGY3FDAYDV6NLFZANCNFSM6AAAAAAQNRXIUI>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
--
--
Bryce Drennan
—
Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI546UWEBZD4PCVOHECAH23V6NOOTANCNFSM6AAAAAAQNRXIUI>.
You are receiving this because you modified the open/close state.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey,
Thanks for repsonding to my previous issue!
I upgraded my imaginairy today to v1.1.4, and found the imagine command no longer worked. When i reduced the version to v1.1.2, it worked again.
The text was updated successfully, but these errors were encountered: