Hello Sraman,
Please do have look to this similar ticket https://support.abp.io/QA/Questions/3296/Integration-with-SendGrid
You just need to change email settings like https://docs.abp.io/en/abp/latest/Emailing#email-settings
Please do let me know if anything else needed
Thank you, Anjali
my node version is v20.5.1
Can you please try the LTS node version instead of Current one https://nodejs.org/en
And please refer below file of tsconfig.json
this one I am using
{
"compileOnSave": false,
"compilerOptions": {
"baseUrl": "./",
"outDir": "./dist/out-tsc",
"sourceMap": true,
"declaration": false,
"downlevelIteration": true,
"experimentalDecorators": true,
"moduleResolution": "node",
"importHelpers": true,
"target": "ES2022",
"module": "es2020",
"lib": [
"es2018",
"dom"
],
"paths": {
"@proxy": [
"src/app/proxy/index.ts"
],
"@proxy/*": [
"src/app/proxy/*"
]
},
"useDefineForClassFields": false
},
"angularCompilerOptions": {
"enableI18nLegacyMessageIdFormat": false
}
}
I tried your
package.json
file locally and resolved compiler errors with the updated package file below just do yarn after deletingyarn.lock
file. My node version isv18.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" } }
Please refer this only just make sure your node version is updated and you are using yarn.
The first error is gone that's fine but now I get list of errorss most of them on this path of theme
Error: node_modules/@volosoft/ngx-lepton-x/layouts/lib
I also face the same error while using your package.json
file. Then I updated file like the previous message then deleted yarn.lock
file and then did yarn
then npm start
my node version in v18.17.1.
Can you please try these steps.
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?