You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
Expected behavior
OpenTelemerty plugin using Agent should not throw any undocumented exceptions.
Actual behavior
Using the OpenTelemerty plugin with Agent will throw some undocumented exceptions.
shardingsphere-agent-master-test-1 | 2024-10-29T07:25:38.816Z ERROR 1 --- [shardingsphere-agent-master-test] [ main] s.a.c.a.e.t.InstanceMethodAdviceExecutor : Failed to execute the pre-method of method `parse`in class `org.apache.shardingsphere.infra.parser.ShardingSphereSQLParserEngine`, Cannot invoke "org.apache.shardingsphere.shade.io.opentelemetry.context.ImplicitContextKeyed.storeInContext(org.apache.shardingsphere.shade.io.opentelemetry.context.Context)" because "value" is null.
shardingsphere-agent-master-test-1 | 2024-10-29T07:25:39.493Z ERROR 1 --- [shardingsphere-agent-master-test] [ main] s.a.c.a.e.t.InstanceMethodAdviceExecutor : Failed to execute the post-method of method `parse`in class `org.apache.shardingsphere.infra.parser.ShardingSphereSQLParserEngine`, Cannot invoke "org.apache.shardingsphere.shade.io.opentelemetry.api.trace.Span.setStatus(org.apache.shardingsphere.shade.io.opentelemetry.api.trace.StatusCode)" because "span" is null.
Reason analyze (If you can)
Not yet confirmed.
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
Execute the following commands on Ubuntu 22.04.4 WSL with Docker Engine and SDKMAN! installed.
Bug Report
For English only, other languages will not accept.
Before report a bug, make sure you have:
Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot reproduce it on current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Which version of ShardingSphere did you use?
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
Expected behavior
Actual behavior
Reason analyze (If you can)
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
Docker Engine
andSDKMAN!
installed.Example codes for reproduce this issue (such as a github link).
The text was updated successfully, but these errors were encountered: