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

Update/calculate hourly airqualitydata using bigqdata #4363

Conversation

NicholasTurner23
Copy link
Contributor

@NicholasTurner23 NicholasTurner23 commented Feb 5, 2025

Description

Just some clean up

Summary by CodeRabbit

  • Refactor
    • Improved how device network and category parameters are processed before making external data requests, ensuring proper format usage for reliable data retrieval.
    • Enhanced error handling to raise a RuntimeError when device data fetching fails, improving awareness of issues during data extraction.

Copy link
Contributor

coderabbitai bot commented Feb 5, 2025

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

This pull request updates the _fetch_devices_from_api method within the DataUtils class. The changes modify the method to convert the device_network and device_category parameters to their string representations using the .str attribute before passing them to the API call. Additionally, the error handling in the extract_devices_data method has been improved by raising a RuntimeError when device fetching fails, rather than returning an empty DataFrame. The overall structure and logic of the methods remain unchanged.

Changes

File Change Summary
src/.../airqo_etl_utils/datautils.py Updated _fetch_devices_from_api to convert device_network and device_category parameters to string representations before passing them to the API. Enhanced error handling in extract_devices_data to raise a RuntimeError on failure instead of returning an empty DataFrame.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant DataUtils
    participant AirQoApi

    Caller->>DataUtils: _fetch_devices_from_api(device_network, device_category)
    DataUtils->>DataUtils: Convert device_network using .str
    DataUtils->>DataUtils: Convert device_category using .str
    DataUtils->>AirQoApi: get_devices_by_network(device_network_str, device_category_str)
    AirQoApi-->>DataUtils: Return devices or error
    DataUtils-->>Caller: Return API response
Loading

Possibly related PRs

Suggested reviewers

  • Baalmart
  • Psalmz777

Poem

In lines of code, a change takes flight,
Converting types with newfound light.
Device networks now speak as strings,
API calls with fresh new wings.
Code refined, our dreams ignite! 🚀

Celebrate the shift, our code takes flight!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c4826bd and 52d5171.

📒 Files selected for processing (1)
  • src/workflows/airqo_etl_utils/datautils.py (2 hunks)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/workflows/airqo_etl_utils/datautils.py (1)

684-684: Refactor network-specific calculations.

The TODO comment suggests finding a better place for network-specific calculations. Consider extracting these calculations into a dedicated NetworkSpecificProcessor class.

Would you like me to propose a design for handling network-specific calculations?

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fc9dd79 and c4826bd.

📒 Files selected for processing (1)
  • src/workflows/airqo_etl_utils/datautils.py (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Analyze (python)
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (4)
src/workflows/airqo_etl_utils/datautils.py (4)

145-146: LGTM! Clean and consistent enum value handling.

The changes ensure consistent string representation of enum values by explicitly accessing the .str attribute. This is a good practice as it makes the code more robust against potential changes in enum string representations.


436-436: Consider moving parameter mappings to configuration.

The TODO comment suggests cleaning up the parameter mappings. Consider moving these mappings to a configuration file or constants module for better maintainability.

Would you like me to help create a configuration structure for these parameter mappings?


663-663: Implement structured data quality checks.

The TODO comment indicates a need for a more robust implementation of raw data quality checks. Consider implementing a dedicated data quality validation framework.

Would you like me to propose a structured approach for implementing data quality checks?


153-157: Well-implemented error handling.

The error handling throughout the file is robust, with:

  • Specific exception types
  • Detailed error messages
  • Proper logging with context
  • Appropriate fallback behavior

@Baalmart Baalmart merged commit c3790e6 into airqo-platform:staging Feb 5, 2025
45 checks passed
@Baalmart Baalmart mentioned this pull request Feb 5, 2025
1 task
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