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

Sentry issue fixes #1294

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Sentry issue fixes #1294

wants to merge 6 commits into from

Conversation

himanshudube97
Copy link
Contributor

No description provided.

Copy link

codecov bot commented Nov 5, 2024

Codecov Report

Attention: Patch coverage is 83.33333% with 1 line in your changes missing coverage. Please review.

Project coverage is 71.26%. Comparing base (09ca310) to head (d3fd5bf).

Files with missing lines Patch % Lines
...tor/Components/LowerSectionTabs/StatisticsPane.tsx 83.33% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1294      +/-   ##
==========================================
- Coverage   71.27%   71.26%   -0.01%     
==========================================
  Files          98       98              
  Lines        6788     6790       +2     
  Branches     1537     1534       -3     
==========================================
+ Hits         4838     4839       +1     
+ Misses       1921     1836      -85     
- Partials       29      115      +86     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@fatchat fatchat changed the title Sentery issue fixes Sentry issue fixes Nov 7, 2024
const count = await httpGet(session, `warehouse/table_count/${schema}/${table}`);
setRowCount(count.total_rows);
try {
const count = await httpGet(session, `warehouse/table_count/${schema}/${table}`);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but why are we asking for rows and columns of a table which doesn't exist

the error is in the backend, a try-catch here won't stop the error from happening

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants