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

AWS S3 getconnectionschema handle empty table folders #2818

Merged
merged 2 commits into from
Oct 16, 2024

Conversation

alishakawaguchi
Copy link
Contributor

No description provided.

@alishakawaguchi alishakawaguchi added the bug Something isn't working label Oct 16, 2024
@alishakawaguchi alishakawaguchi self-assigned this Oct 16, 2024
Copy link

linear bot commented Oct 16, 2024

Copy link

vercel bot commented Oct 16, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
neosync-docs ⬜️ Ignored (Inspect) Visit Preview Oct 16, 2024 10:47pm

Copy link

codecov bot commented Oct 16, 2024

Codecov Report

Attention: Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.

Project coverage is 35.99%. Comparing base (c5d0157) to head (b7defcc).
Report is 3 commits behind head on main.

Files with missing lines Patch % Lines
...1alpha1/connection-data-service/connection-data.go 0.00% 4 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2818      +/-   ##
==========================================
- Coverage   36.01%   35.99%   -0.02%     
==========================================
  Files         295      295              
  Lines       28037    28041       +4     
==========================================
- Hits        10098    10094       -4     
- Misses      16574    16579       +5     
- Partials     1365     1368       +3     

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

@@ -627,7 +627,7 @@ func (s *Service) GetConnectionSchema(
return nil, err
}
if out == nil {
break
continue
Copy link
Member

Choose a reason for hiding this comment

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

maybe we should add a nice log statement here ? It might be nice if it's an edge case.

@@ -637,6 +637,9 @@ func (s *Service) GetConnectionSchema(
if err != nil {
return nil, err
}
if result.ContentLength == nil || *result.ContentLength == 0 {
continue
Copy link
Member

Choose a reason for hiding this comment

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

Same, is it worth adding a log statement here? It might be helpful for debugging if this is an edge case.

@alishakawaguchi alishakawaguchi merged commit b1667ed into main Oct 16, 2024
8 of 10 checks passed
@alishakawaguchi alishakawaguchi deleted the alisha/neos-1551-cli-bug branch October 16, 2024 22:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants