Activities of "roberto.fiocchi"

HI, sent you the email with the test projects

• ABP Framework version: v8.1.0
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes
• Steps to reproduce the issue:

1. Create a solution with Abp 8.1.0.rc.4
2. Add Entity “Book” with Id int, Code String 10 Required , Title String 100 Required
3. Open BookManager.cs add the following code in CreateAsync (only for test)

#region test InsertMany
var myBooks = new List< Book >();
for (var i = 0; i < 12000; i++)
{
	myBooks.Add(new Book(i.ToString(),$"Title-{i}"));
}
    
Stopwatch stopWatch = new Stopwatch();
stopWatch.Start();

await _bookRepository.InsertManyAsync(myBooks, true);

stopWatch.Stop();
TimeSpan ts = stopWatch.Elapsed;
Console.WriteLine(ts); 
#endregion

4. Lunch in Debug
5. Via Swagger Post a new Book
6. Track the time from console log o via breakpoint. On my Pc is 00:00:05.7310325
7. After that upgrade to Abp 8.1.0
8. Lunch in Debug
9. Via Swagger Post a new Book
10. Track the time from console log o via breakpoint. On my Pc is 00:05:05.4026061

It takes 60 times longer !!!

We use InsertMany in import jobs and execution times have now gone from a few seconds to many minutes and those that used to take a few minutes now take hours.

We cannot upgrade to 8.1.0 stable because it would block the application in production.

From the release logs there is no evidence of changes in this area.

What has changed?

When creating an entity with abp suite, in the appservice, use IReadOnlyRepository for lookup entities rather than IRepository so it wont be tracking the entity

I have downloaded Abp suite version 8.1.0 but i still can't create a property of type "DateOnly" and "TimeOnly" inside an entity. When will this feature be available?

Success again today with the release of Abp 8.1.0

I think the problem depends on this https://commercial.abp.io/releases/pr/16597

Thank you, I await your feedback

I recommend closing this topic and highlighting what is in the Roadmap and what is not so that we can vote on which feature we consider priority.

Now there are many proposals, but we don't know what you are working on.

Thanks

You did not understand the reported error. We don't need the temporary fix, but we need that when you release a new version it doesn't impact current projects. This error happens with every version release and blocks both the development and release pipelines.

This is a bug for me.

Thanks for your attention

• ABP Framework version: v8.1.0-rc.3
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace: Warning As Error: Detected package downgrade: Volo.Abp.AspNetCore.MultiTenancy from 8.1.0-rc.4 to 8.1.0-rc.3. Reference the package directly from the project to select a different version. Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX 3.1.0-rc.4 -> Volo.Abp.AspNetCore.Mvc.UI.MultiTenancy 8.1.0-rc.4 -> Volo.Abp.AspNetCore.MultiTenancy (>= 8.1.0-rc.4) Volo.Abp.AspNetCore.MultiTenancy (>= 8.1.0-rc.3)
• Steps to reproduce the issue:

• Create a new project using Blazor WASM version 8.1.0-rc.3
• Build the project
• Notice how it wont build and will output the error message mentioned

@EngincanV : do you have any news on this?