-
Notifications
You must be signed in to change notification settings - Fork 86
v8.1.1-rc.8 #4016
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v8.1.1-rc.8 #4016
Conversation
…or-tx Bump gas price on nonce issue
…ber-issue Remove unneeded toNumber
…update Fix setCompletedAndFinalizedRandomSamplingChallengeRecord parameters
…sk-query Add ASK timeout to blazgraph query
2efc19b
into
v6/prerelease/testnet
| ); | ||
| } | ||
|
|
||
| console.timeEnd(`BatchGetCommand [NETWORK]: ${operationId} ${uals.length}`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Debugging Code Leaks into Production
Extensive console.time() and console.timeEnd() calls, intended for temporary debugging and performance measurement, have been accidentally committed. These statements are present in BatchGetCommand, HandleBatchGetRequestCommand, and TripleStoreService methods (getAssertion, getAssertionsInBatch). They will pollute production logs with excessive timing information and should be removed.
Locations (3)
| result[ual] = results[index]; | ||
| } | ||
|
|
||
| endTimer(totalLabel); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Debugging Code in Production Methods
Unnecessary console.time and console.timeEnd calls for performance instrumentation were added to the getAssertion and getAssertionsInBatch methods. This debugging code should not be committed to production as it clutters console output.
No description provided.