oceanbase / oceanbase/seekdb

Test issue placeholder: no attention required

Open
#294 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

dima type: task
Dominant language
C++
Stars
2.9k
Forks
342
Avg merge
2d 14h
Merged PRs (30d)
53

Description

Environment

Please provide the output of bin/observer -V. If this test also involves a version change for OBProxy, please also provide the output of obproxy -V.

Is this a temporary version provided by RD?

No / Provided by xxx temporarily

Reproducibility

Consistent / Occasional / Uncertain / Other

Test Changes

Added xx test scenario / Changed to new machines / Ran xx new tool / Issue appeared after replacing with new version

Were there other anomalies or changes in the environment?

No / Clog disk was full / Manual operation performed (e.g., ...) / xx exception injected

Description / Steps to Reproduce (Required)

Please describe in detail: what workload was running on the environment, what actions were taken before the issue occurred, and if there were any test changes, etc.

Strongly discouraged: Only posting ERROR logs or only posting stack traces!

Environment Details

Please provide connection strings for the problematic tenant and the sys tenant, as well as deployment information.
Is the environment preserved for investigation?

Log Information

Other Notes

For issues reported from external business operations, please correctly select the "Work Item Type" on the right based on the actual situation:

  • Customer Service Feedback: Specifically refers to issues before production deployment or during POC, where a product bug is clearly identified and requires a fix and release.
  • Online Issue: An issue that occurred after production deployment, clearly identified as a product bug, but not classified as a fault.
  • Online Fault: An issue that occurred after production deployment, clearly identified as a product bug, which caused business errors or negative impact on the customer side (the classification as a fault is determined by the delivery service team).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The body is a report template and mentions bin/observer and obproxy only for version output. Confirm whether this is a real report first; no reproduction, affected behavior, file, test, or requested change is supplied, so there is no defined completion state.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
1/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.