Skip to content
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

3.8 [Execution plan] start row Line connection is incorrect #711

Closed
liangliangc opened this issue Dec 13, 2023 · 0 comments · Fixed by #714
Closed

3.8 [Execution plan] start row Line connection is incorrect #711

liangliangc opened this issue Dec 13, 2023 · 0 comments · Fixed by #714
Assignees
Labels
affects/master PR/issue: this bug affects master version. process/done Process of bug severity/minor Severity of bug type/bug Type: something is unexpected

Comments

@liangliangc
Copy link

Describe the bug (must be provided)

A clear and concise description of what the bug is.

Your Environments (must be provided)

  • OS: Linux,Mac or Windows
  • Node-version: node --version
  • Studio-version: display in studio navBar

How To Reproduce(must be provided)

Steps to reproduce the behavior:

  1. Step 1
  2. Step 2
  3. Step 3

Expected behavior

A clear and concise description of what you expected to happen.

Additional context

Provide logs and configs, or any other context to trace the problem.

@liangliangc liangliangc added affects/master PR/issue: this bug affects master version. type/bug Type: something is unexpected severity/minor Severity of bug labels Dec 13, 2023
@github-actions github-actions bot added the process/fixed Process of bug label Dec 18, 2023
@liangliangc liangliangc added process/done Process of bug and removed process/fixed Process of bug labels Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects/master PR/issue: this bug affects master version. process/done Process of bug severity/minor Severity of bug type/bug Type: something is unexpected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants