Starts in:
1 DAY
20 HRS
9 MIN
43 SEC
Starts in:
1 D
20 H
9 M
43 S

Activities of "icoretchi"

Also pay attention for the following errors as well:

  • ABP Framework version: v7.4.1
  • 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:
  • Generate entity with one-to-many relationship with abp suite v.7.4.1
  • See the errors on razor page.
Answer

Probably this is specific to my infrastructure configuration. I'll close the issue.

Hi,

Thanks for giving me a clue. I've probably understood where the mistake could be. Just after your suggestion, I've noticed that when adding a new microservice to the solution, in the file with the constants in my case AcquisitionServiceRemoteServiceConsts from the Application.Contracts project, the variable with the name of the module is not added, that is, the following declaration is missing public const string ModuleName = "acquisitionService"; And for this reason, the controllers do not appear in the api definition, because each controller has the [Area("acquisitionService")] attribute. So please check the generation of the files in case of the addition of the microservice to the solution.

Thanks Iulian

Answer

If you have not encountered such an error recently, then I will close the this issue.

Answer

Hi,

Apparently everything is fine with ElasticSearch. No log errors.

Cheers, Iulian

  • 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:

  • cd into HttpApi.Client project

  • run abp generate-proxy -t csharp -url https://localhost:44990 -m AcquisitionService --without-contracts

As result the command generate client static proxies only for sample entity not all the time, but very often. Any suggestion?

Question
  • 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):
  • Exception message and full stack trace:

Prometheus logs:

Prometheus dashboard

  • Steps to reproduce the issue:

My solution is based on microservices. I am running the solution in docker environment. It happends all the time when I run the solution. Any suggestions?

  • 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:
  • Generate CRUD pages for the entity by abp suite
  • The generated Submit button Form attribute for Blazor Edit Modal has reference for Create Modal Form - This minor error is for a long time.

Hi,

It's very simple. You can take any project you have or generate the entity with abp suite. It is important that the entity has a one-to-many relationship with another entity so that LookupDto appears in Api. Then generated as usual static proxy clients. For the entities that have Lookups, errors will appear, in the order of those in the image presented later.

Showing 51 to 60 of 87 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06