-
Notifications
You must be signed in to change notification settings - Fork 155
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
The name of the database date can't be null #97
Comments
Hi @akema-trebla, Hard to say, but are some ideas:
|
Hi @JonPSmith `Tenant newTenant = null;
The error happens in this section of the Precisely this line Up until the above line, the tenant's |
Hi @akema-trebla, This sounds like the problem I had when I stored the sharding data in a json file. It turns out that the Because of this I changed over to using my Net.DistributedFileStoreCache in version 6 to overcome this limitation. You can see this in Example6. |
Hmm, I see. Would you be able to look at this sample with a repro of the issue to ascertain what's going wrong? Maybe I've missed something in the setup? I've put the sample code to sign up new tenant in the privacy navigation click in Example 6. |
Hi @akema-trebla, I have recreated your problem using Example7 and is my initial result is that This is a tentative evaluation, but I wanted to let you know I am looking at this. If you can update your Also, this error has shown errors in way the |
Hi @JonPSmith Thanks for the feedback. I'm using a hybrid sharding approach. |
Did you remove the |
Hi @JonPSmith I haven't tried your workaround yet. I'll do so tomorrow and give you feedback. Thanks |
Hi @JonPSmith BUT you need to delete "Sign up" entries in the CacheFileStore holding the ShardingEntries data and also delete any "Sign up" Tenant entries before you try again. Can you elaborate on this? I've even tried deleting everything in the cache. Same error happens. The tenant get's created, an error occurs trying to group the tenants using DatabaseInfoName since it's not set and then another error occurs while trying to delete the tenant because of the previous error. |
When I looked your "Sign up for a new tenant" (SignUp for short) with sharding problem I found that the current code doesn't always remove the
To do this you need to:
NOTE: I am working on a new release of AuthP where the SignIn service that uses a unique name for the |
Hi @akema-trebla, I have just released version 6.2.0 which is much better at telling what the Exception was. If you have something in your code you can find it more easily and if the user something wrong they can try again and/or provide a string to send to your support admin users to help them out. This release took so long because I completely changed code in the Let me know if helps or not. |
Hi @JonPSmith Thanks for looking into this. I have updated to version 6.20 and the error doesn't show up anymore. The tenant is also successfully created. However, the result property of the return type for SignUpNewTenantWithVersionAsync is null and so I have to make another database call to get the newly created tenant Id. Is that how it's supposed to be or you'll consider sending the newly create tenant info when the method returns like it used to previously? |
Hi @akema-trebla, It was a bug and I have fixed it (see new version 6.2.1). I the test that it works, but test uses stubs so could you check it and let me know. |
Hi @JonPSmith I can confirm that this issue is resolved. Thanks. |
Thanks for letting me know. I was pretty sure it would work because of the tests, but knowing it works in an application is great as the testing of this is very complex. |
Correct me if I'm wrong but I think previously the default databaseInfoName was used when you do not set one. Is that still the case?
I'm using the SignUpNewTenantWithVersionAsync method and the tenant gets created but no DatabaseInfoName is set and I get the following error
Failed to create a new tenant due to an internal error.
Any pointers? @JonPSmith
Thanks.
The text was updated successfully, but these errors were encountered: