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

Fix: make fetch_data check for rows properly #19

Merged
merged 1 commit into from
Mar 13, 2023

Conversation

alexclavel-ocient
Copy link

SUMMARY

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

Copy link
Collaborator

@jwilliams-ocient jwilliams-ocient left a comment

Choose a reason for hiding this comment

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

Awesome - can you link a JIRA ticket here so we can track this? We should add a check in a system test for this. I wouldn't focus on that now though

@@ -256,7 +256,8 @@ def fetch_data(
]
raise exception

if len(rows) > 0 and type(rows[0]).__name__ == rows:
# TODO: Unsure if we need to verify that we are receiving rows:
Copy link
Collaborator

Choose a reason for hiding this comment

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

"here"

@alexclavel-ocient alexclavel-ocient merged commit c01ccda into master Mar 13, 2023
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