Yes, that's right, LeptonX will be the default theme with version 6.0.0.rc-1. However, I would like to remind you that LeptonX is currently released with an rc version, and the new version to be released is the rc version. So there will be bugs but the purpose of these versions is to make them ready for a stable version.
If you want, you can stay in the stable version and use the Lepton theme and download the source code. For now, you can't do this with LeptonX, but as I said before, we are trying to find a suitable solution that will not upset our customers.
Hello,
We will not allow downloading Lepton-X for now, but we are trying to find a good solution that will not upset our customers, we will announce the necessary information when we allow downloading.
The tenant exists in the database but still we are getting this error. Step 1: The user is using the applicaiton for say 10 minutes. Step2 : After say 10 mins when trying to access the application we get this error, Tenant not found. Step 3: After clearing cache, it works. Need to know why this happens when tenant exists.
Then there is only one option left: examining incoming calls by putting a breakpoint on TenantStore's GetCacheItemAsync method. I think we will understand the problem by debugging.
To make this easier, you can override TenantStore's GetCacheItemAsync and call the base method.
Thanks for the information, I'm closing it now that the problem is solved.
Hello again, thank you very much for the information you provided. I tried again with 19064 records, but I couldn't reproduce it again. I'll add more records and try, but I have one more question.
What kind of result do you get when you run queries that cover the following situations on the database server? https://www.mongodb.com/docs/compass/current/query/skip/
{"skip": 0, "limit": 1, "batchSize": 2, "sort": { "Name": 1 }}
{"skip": 1, "limit": 1, "batchSize": 2, "sort": { "Name": 1 }}
{"skip": 2, "limit": 1, "batchSize": 2, "sort": { "Name": 1 }}
I need this answer to make sure the problem is not data related.
Hi, I've spent quite a bit of time on the problem but I'm having trouble reproducing it. I don't think the problem is related to static-proxy, but to confirm my assumption, I need to know if you are facing the same problem when you send a request to product-service via swagger. Also, I would appreciate it if you could provide a minimally reproducible example for healthier tests.
Yes, it may be enough to change the configuration so that it cannot access the Redis server.
The tenant exists in the database but still we are getting this error. Step 1: The user is using the applicaiton for say 10 minutes. Step2 : After say 10 mins when trying to access the application we get this error, Tenant not found. Step 3: After clearing cache ,it works.
Hello, can we just turn off Redis temporarily? I know the application will be very slow, but we will see if the problem is entirely with Redis.
I see an accepted answer so I'm closing this issue but if you have more questions about it feel free to reopen it.
Thanks for the PR @maliming.
I merged the relevant pull request, it will be available in the next version.
Thanks for the enhancement request @imranStem.
Closing the issue. Feel free to re-open, if you have any further questions on this topic.
