-
Notifications
You must be signed in to change notification settings - Fork 168
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
[Resolves #86] error running db seed task #87
Conversation
rpbaltazar
commented
Jul 12, 2020
- ensure listed tenants are created before trying to migrate them or seed them
aa21143
to
83aa696
Compare
83aa696
to
4dc134e
Compare
Without being able to replicate the actual reported bug, this is the best i can do at the moment. I'll close the associated issue as well. If this is still a problem, then we'll need to investigate further how to find out the source of the problem |
09364b5
to
9a60f80
Compare
Hey! I was testing with the development branch, and I found that I wasn't able to migrate the tenants anymore. I narrowed it down to this PR. Here is the relevant result of running
I think |
Also not trying to bother, but just wondering, when will this be released? is there a schedule or something? jut wanted to be aware of the time frame. I know this is time you give from your own, so not pushing or anything like that. |
Prepare Release - 2.8.0 - Resolves #98 - Trying to generate an automatic changelog - #99 - Resolves #86 - Fixes seeding errors - #87 - Resolves #66 - Uses a transaction to create a tenant - #69 - Resolves #121 - Relaxes dependencies to allow rails 6.1 - #122 - Resolves #123 - When tests run in a transaction, new tenants in tests fail to create - #124 - Reverted unsafe initializer - #118