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

Meet invalid memory address or nil pointer dereference #41688

Closed
zeminzhou opened this issue Feb 23, 2023 · 1 comment · Fixed by #41692
Closed

Meet invalid memory address or nil pointer dereference #41688

zeminzhou opened this issue Feb 23, 2023 · 1 comment · Fixed by #41692
Labels
affects-6.5 component/metrics report/customer Customers have encountered this bug. severity/major type/bug The issue is confirmed as a bug.

Comments

@zeminzhou
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. start up TiDB cluseter by tiup
  2. import data
  3. exeute the flowing sql:
USE sample_data;
WITH starts_by_day AS
  (SELECT repo_name,
          date(created_at) AS DAY,
          COUNT(1) AS stars
   FROM github_events
   WHERE TYPE = 'WatchEvent'
   GROUP BY repo_name,
            DAY)
SELECT s.repo_name,
       max(s.stars) AS daily_stars,
       sum(s.stars) AS total_stars,
       sum(s.stars) / max(s.stars) AS rate
FROM starts_by_day AS s
GROUP BY repo_name
ORDER BY rate DESC
LIMIT 10;

2. What did you expect to see? (Required)

sql executed successfully

3. What did you see instead (Required)

runtime error: invalid memory address or nil pointer dereference

4. What is your TiDB version? (Required)

nightly

image

@seiya-annie
Copy link

/found customer

@ti-chi-bot ti-chi-bot bot added the report/customer Customers have encountered this bug. label Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.5 component/metrics report/customer Customers have encountered this bug. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants