TraceId is reused

[guoyunlong666]

When I restart the app, the new request will generate new TraceId, but after a few minutes, the new request will reuse a TraceId.

[ascrutae]

which version do you use?

[guoyunlong666]

Thank you for your reply, I am using version 1.0.0

[guoyunlong666]

The backend is 6.0.0-GA
When I install the agent, I first execute npm install skyapm-nodejs@latest --save in other directories. Then I copy the generated node_modules to the node_modules of the project, but during the copying process, the existing files are not forced to be overwritten. .

[guoyunlong666]

I just tried to force the content in node_modules to be overwritten, or the same problem.

[ascrutae]

Why do you do those actions?

[guoyunlong666]

Because we have some projects that refactor some of the contents of node_modules, so when I install, try not to affect our project.

[ascrutae]

OK, Got it, I will try to reproduce this issue and fixed it.

[guoyunlong666]

That's great, thank you

[guoyunlong666]

skyapm-nodejs version：1.1.0
node version：v8.11.4

hi,I am using the new version of the agent, and the same problem will still occur.
The new request reuses the same traceID and the response time is superimposed.

[ascrutae]

Could you give me an demo?

On Thu, Mar 28, 2019 at 10:06 AM guoyunlong666 ***@***.***> wrote: skyapm-nodejs version：1.1.0 node version：v8.11.4 hi,I am using the new version of the agent, and the same problem will still occur. The new request reuses the same traceID and the response time is superimposed. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#67 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AL3D3wN-nezQxGjRhxkY60c_No7PuQeXks5vbCO2gaJpZM4bzqov> .

-- Regards, Xin