Dusan K.

@rochdev For example I cannot even start my project with `--experimental-loader` hook. It just gets stuck. Other loaders work ok. Though this may be due to TypeScript 4.7.4, top level...

@rochdev There are no `dd-trace` startup logs when using standard Node ESM loader. When using experimental, there are logs, but service won't start. dd-trace: 3.3.1, Node: 16.17.0

@rochdev I can give you V8 profiling logs during startup of project. Raw log [v8-10-4-22_2-44-50-PM-.log](https://github.com/DataDog/dd-trace-js/files/9707244/v8-10-4-22_2-44-50-PM-.log) Parsed txt statistics [v8_statistics.txt](https://github.com/DataDog/dd-trace-js/files/9707246/v8_statistics.txt) Generally, sample project I made to try and demonstrate issue cannot...

@timocov Idea from @wolfram77's seems like feasible. For example TS AST representation of following is: ``` // CODE export * as R from "ramda"; // AST (node.forEachChild) SourceFile ExportDeclaration NamespaceExport...

@zerobig @skoruba @xmichaelx I had this issue with both login and logout. When using IdentityServer4 and ASP.NET Identity together. This happens as you already mentioned when running app over https...

Has this been added? I think that on newer devices path changed to /sys/devices/virtual/misc/wolfson_control If it hasn't I'll try to add sysfs paths to constants and add controls SoundFragment.java, but...

``` static struct miscdevice sound_dev = { .minor = MISC_DYNAMIC_MINOR, .name = "wolfson_control", }; ``` This is for code for sysfs in Wolfson Sound Control by AndreiLux. The first path...

@sfc-gh-hchaturvedi I have tried using `npm-force-resolutions` to force `requestretry` version to ^7.0.0; Here is relevant 'TRACE' log of `snowflake-sdk` with sensitive information hidden: > {"level":"DEBUG","message":"[10:45:11.4511 AM]: Contacting SF: /session/v1/login-request?requestId={*HIDDEN*}&databaseName={*HIDDEN*}&schemaName={*HIDDEN*}, (1/5)"}...

`requestretry` version `7.0.0` has this problem https://github.com/FGRibreau/node-request-retry/issues/140 That's what gave me error 390103 (explained in comment above). Versions `7.0.1` and `7.0.2` work good