I tried your package.json
file locally and resolved compiler errors with the updated package file below just do yarn after deleting yarn.lock
file. My node version is v18.17.1
{
"name": "REAMApp",
"version": "0.0.0",
"scripts": {
"ng": "ng",
"start": "ng serve --open",
"build": "ng build",
"build:prod": "ng build --configuration production",
"watch": "ng build --watch --configuration development",
"test": "ng test",
"lint": "ng lint"
},
"private": true,
"dependencies": {
"@abp/ng.components": "~7.3.3",
"@abp/ng.core": "~7.3.3",
"@abp/ng.oauth": "~7.3.3",
"@abp/ng.setting-management": "~7.3.3",
"@abp/ng.theme.shared": "~7.3.3",
"@agm/core": "^3.0.0-beta.0",
"@angular/animations": "~16.0.0",
"@angular/common": "~16.0.0",
"@angular/compiler": "~16.0.0",
"@angular/core": "~16.0.0",
"@angular/forms": "~16.0.0",
"@angular/google-maps": "^14.2.7",
"@angular/localize": "~16.0.0",
"@angular/platform-browser": "~16.0.0",
"@angular/platform-browser-dynamic": "~16.0.0",
"@angular/router": "~16.0.0",
"@types/googlemaps": "^3.39.12",
"@volo/abp.commercial.ng.ui": "~7.3.3",
"@volo/abp.ng.account": "~7.3.3",
"@volo/abp.ng.audit-logging": "~7.3.3",
"@volo/abp.ng.gdpr": "~7.3.3",
"@volo/abp.ng.identity": "~7.3.3",
"@volo/abp.ng.language-management": "~7.3.3",
"@volo/abp.ng.openiddictpro": "~7.3.3",
"@volo/abp.ng.saas": "~7.3.3",
"@volo/abp.ng.text-template-management": "~7.3.3",
"@volosoft/abp.ng.theme.lepton-x": "^2.3.0",
"rxjs": "7.5.6",
"tslib": "^2.1.0",
"zone.js": "~0.13.0"
},
"devDependencies": {
"@abp/ng.schematics": "~7.3.3",
"@angular-devkit/build-angular": "~16.0.0",
"@angular-eslint/builder": "~16.0.0",
"@angular-eslint/eslint-plugin": "~16.0.0",
"@angular-eslint/eslint-plugin-template": "~16.0.0",
"@angular-eslint/schematics": "~16.0.0",
"@angular-eslint/template-parser": "~16.0.0",
"@angular/cli": "~16.0.0",
"@angular/compiler-cli": "~16.0.0",
"@angular/language-service": "~16.0.0",
"@types/jasmine": "~3.6.0",
"@types/node": "^12.11.1",
"@typescript-eslint/eslint-plugin": "^5.36.2",
"@typescript-eslint/parser": "^5.36.2",
"eslint": "^8.23.0",
"jasmine-core": "~4.0.0",
"karma": "~6.3.0",
"karma-chrome-launcher": "~3.1.0",
"karma-coverage": "~2.1.0",
"karma-jasmine": "~4.0.0",
"karma-jasmine-html-reporter": "^1.7.0",
"ng-packagr": "^16.0.1",
"typescript": "~5.0.4"
}
}
After deleting yarn.lock file please run yarn command then do npm start till that time I will try to run this configuration on my local.
Hello portx-dev,
Actually this is a performance issue try to optimize your queries and code. For Worker Busy Thread < Min Thread
I am providing some workaround please try this -
You need to change your Min Thread for that please refer this https://learn.microsoft.com/en-us/dotnet/core/runtime-config/threading
or try to add this code in Program.cs
of Host
System.Threading.ThreadPool.SetMinThreads(200, 200);
I have given here Min Thread value as 200 you can change it as per your requirement
Please do let me know if this helps you
Thank you, Anjali
Hi
If several messages published to the event bus in a short period, would the event handling process all the messages without loosing any message when doesn't use the Outbox? Please read more about RabbitMQ Reliability https://www.rabbitmq.com/reliability.html
Hi All the API instances will listen to those message but they have to be configure on the same channel https://github.com/abpframework/abp-samples/tree/master/RabbitMqEventBus You can try this easy sample
you can read https://docs.abp.io/en/abp/latest/Distributed-Event-Bus#outbox-inbox-for-transactional-events more about When should use outbox when shouldn't use outbox?
Hello icoretchi,
Can you go to feature UI of a tenant or host under file management you can configure file size there.
Also please check below discussion https://github.com/dotnet/aspnetcore/issues/49594
Thank you, Anjali
Hello mattw@agilenova.com
Have you checked this https://docs.abp.io/en/commercial/7.3/modules/payment
please do let me know if anything else needed
Thank you, Anjali
Hi csykes,
Can you share a screenshot from [dbo].[AbpPermissionGrants]
for this user only?
Thank you, Anjali
Hello Abdulaziz_Alsaffar Can you please try using yarn just delete yarn.lock file if present. Then do yarn after completion of that you can run npm start If still facing issue share package.json file I will try to run at my side locally. Thank you