[BUG] Server crashes with @tsed/seq
See original GitHub issueInformation Version: 6.35.1 Packages: @Tsed/Seq
Hello, I would like to use the tsed/seq package but once I’m importing it, the server crashs
Code
...
import "@tsed/seq"; // import seq Ts.ED module
export const webConfig: Partial<TsED.Configuration> = {
rootDir,
seq: {
url: "http://192.168.0.60:1234"
},
...
}
Error log
[2021-03-24T19:55:40.517] [ERROR] [Automatize -- Manager] - TypeError: Cannot read property 'Logger' of undefined
at SeqAppender.build (P:\own\desktop\cross-platform\automatize-github-docker\manager\back\node_modules\@tsed\logger-seq\src\SeqAppender.ts:20:29)
at new BaseAppender (P:\own\desktop\cross-platform\automatize-github-docker\manager\back\node_modules\@tsed\logger\src\appenders\class\BaseAppender.ts:68:20)
at new SeqAppender (P:\own\desktop\cross-platform\automatize-github-docker\manager\back\node_modules\@tsed\logger-seq\src\SeqAppender.ts:15:1)
at LoggerAppenders.set (P:\own\desktop\cross-platform\automatize-github-docker\manager\back\node_modules\@tsed\logger\src\logger\class\LoggerAppenders.ts:52:36)
at SeqModule.$afterRoutesInit (P:\own\desktop\cross-platform\automatize-github-docker\manager\back\node_modules\@tsed\seq\src\SeqModule.ts:18:38)
at Map.emit (P:\own\desktop\cross-platform\automatize-github-docker\manager\back\node_modules\@tsed\di\src\class\LocalsContainer.ts:15:34)
at PlatformExpress.callHook (P:\own\desktop\cross-platform\automatize-github-docker\manager\back\node_modules\@tsed\common\src\platform\builder\PlatformBuilder.ts:227:22)
at PlatformExpress.loadRoutes (P:\own\desktop\cross-platform\automatize-github-docker\manager\back\node_modules\@tsed\common\src\platform\builder\PlatformBuilder.ts:354:16)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at PlatformExpress.loadRoutes (P:\own\desktop\cross-platform\automatize-github-docker\manager\back\node_modules\@tsed\platform-express\src\components\PlatformExpress.ts:83:5)
at PlatformExpress.runLifecycle (P:\own\desktop\cross-platform\automatize-github-docker\manager\back\node_modules\@tsed\common\src\platform\builder\PlatformBuilder.ts:170:5)
at PlatformExpress.bootstrap (P:\own\desktop\cross-platform\automatize-github-docker\manager\back\node_modules\@tsed\common\src\platform\builder\PlatformBuilder.ts:315:5)
at bootstrap (P:\own\desktop\cross-platform\automatize-github-docker\manager\back\src\app.ts:18:26)
Acceptance criteria The app must not crash 😃
Sincerly
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
E-AS: How To Troubleshoot Application Server Crashes
There can be various reasons which cause Application Server processes to crash, like a PeopleTools issue, bad OS patches, insufficient user-limits on Unixes...
Read more >Server Down: What to Do When My Server Crashes?
Step 1: Identify the root cause · Actual error message: There are a number of error messages that could appear on the screen...
Read more >FIX: BizTalk Server crashes with error code 80131544 when ...
Fixes an issue in which BizTalk Server 2010 or 2013 crashes with the error code 80131544 when you have installed the .NET Framework...
Read more >Comp Server Crashes - Bug Report - Overwatch Forums
I've noticed an uptick in “server closed due to unexpected error” since the patch, 1 in 4 games or even 1 in 3....
Read more >New Warzone Bug Crashes Entire Server! - YouTube
Call of Duty Warzone has it's fair share of glitches that keep players from enjoying the intended experience, but a recently discovered ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
🎉 This issue has been resolved in version 6.37.0 🎉
The release is available on:
v6.37.0
Your semantic-release bot 📦🚀
Release is in progress for the logger.