-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fresh db cannot be configured #47
Comments
The assertion came from your self-made sink queue. Fixed that in 2fd0688 |
Please give a hint on how to reproduce. I ended up with this error instead:
While doing this:
What happens is that the config is empty, but the code assumes it's not. We can now either prevent a db with an invalid config is eligible as a target, which is confusing for users as to why it's not showing up. Or we prevent users from creating invalid db configs. Ideally, we had something that notifies users of the problem in a way unrelated to either process. I'd love to see a general dashboard able to list problems. |
Stuff like this
The text was updated successfully, but these errors were encountered: