Activities of "icoretchi"

• ABP Framework version: v7.4.0
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• • Tiered (for MVC) or Auth Server Separated (for Angular): microservices
• Exception message and full stack trace:
• Steps to reproduce the issue:

Hi,

I would like to mention about the following error that appears after abp generate-proxy. I noticed that this error appears when we regenerate client proxies and in the api there is a reference to LookupDto. This behavior appeared in version v.7.3.2

Cheers, Iulian

Hi,

Actually I've searched for date ranges DateMin and DateMax. For DateMin is not a problem because the 17.10.2023 is less than 18.10.2023, but for DateMax if I use 18.10.2023 then the api request will contain the interval between 17.10.2023 and 17.10.2023. That means that the records with date 18.10.2023 will not be returned. In such way filtering will not work properly.

Steps to reporduce:

• Add record with date 18.10.2023
• Select for DateMin 18.10.2023
• Select for DateMax 18.102023 Expected result:
• record will be in the list Actual result
• record is not in the list

I hope I am more explicit now.

Thanks

Hi,

What do you mean data result is correct? The problem is that I request wrong filtering conditions from the backend. On UI you see one date, but the backend results will be provided based on different dates.

• ABP Framework version: v7.4.0
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): microservices
• Exception message and full stack trace:
• Steps to reproduce the issue:

1. Generate crud form with abp suite with DateTime properties
2. The suite will generate Advanced Filters with DateTime Pickers
3. Select the date for instance 18.10.2023
4. But the request parameter in the api will be a different date. In my case is minus one date i.e. 17.10.2023

Hi Anjali,

It's not working as well. Actually the same error appier if you will generate a new project based on a microservice template with Blazor WASM by abp suite v7.4.0.

Cheers, Iulian

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, and please first use the search on the homepage. Provide us with the following info:

• ABP Framework version: v7.4.0
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): microservices
• Exception message and full stack trace:
• Steps to reproduce the issue:

I've migrated the project from 7.3.3 to 7.4.0 and received the following error:

Hi Anjali,

I am closing this issue, because I've found out that the problem was on kubernetes nginx ingress controller. By default the size is limited up to 1M. So the following annotation needs to be set: nginx.ingress.kubernetes.io/proxy-body-size.

Thanks, Yulian

Hi Anjali,

Storage size is set to 0 (i.e unlimited) in FileManagement settings and the provided link it wasn't very helpful.

Thanks & Regards, Yulian

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, and please first use the search on the homepage. Provide us with the following info:

• ABP Framework version: v7.3.3
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): microservice
• Exception message and full stack trace:
• Steps to reproduce the issue:

I am trying to upload a file with a size a little more than 1M in production (i.e. cloud kube cluster). I have to mention if the file is less than 1M is uploaded successfully. And also locally the files of any size can be uploaded successfully. I am using FileManagement module. I have tried to configure kestrel with the following options.Limits.MaxRequestBodySize = null; I've changed the ocelot gateway to yarp. Nothing helped. Can you suggest something?

*

Hi Angali,

Yes. It works. Thanks.