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(issue #31927): TimeGrain.WEEK_STARTING_MONDAY #32015

Merged
merged 2 commits into from
Jan 29, 2025

Conversation

AdrianMastronardi
Copy link
Contributor

SUMMARY

Fixes #31927

Time grain 'Week starting Monday' doesn't select the proper date time range. I also found that 'Week starting Sunday' didn't work either and I'm adding the fix for it too.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

  • Pre-fix 'Week starting Monday' with incorrect numbers:
    prefix-monday

  • Pre-fix 'Week ending Sunday' with correct numbers:
    prefix-sunday

  • Post-fix 'Week starting Monday' with correct numbers:
    postfix-monday

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

  • Has associated issue: #31927
  • 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

@korbit-ai korbit-ai bot left a comment

Choose a reason for hiding this comment

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

I've completed my review and didn't find any issues.

Files scanned
File Path Reviewed
superset/db_engine_specs/sqlite.py

Explore our documentation to understand the languages and file types we support and the files we ignore.

Need a new review? Comment /korbit-review on this PR and I'll review your latest changes.

Korbit Guide: Usage and Customization

Interacting with Korbit

  • You can manually ask Korbit to review your PR using the /korbit-review command in a comment at the root of your PR.
  • You can ask Korbit to generate a new PR description using the /korbit-generate-pr-description command in any comment on your PR.
  • Too many Korbit comments? I can resolve all my comment threads if you use the /korbit-resolve command in any comment on your PR.
  • Chat with Korbit on issues we post by tagging @korbit-ai in your reply.
  • Help train Korbit to improve your reviews by giving a 👍 or 👎 on the comments Korbit posts.

Customizing Korbit

  • Check out our docs on how you can make Korbit work best for you and your team.
  • Customize Korbit for your organization through the Korbit Console.

Current Korbit Configuration

General Settings
Setting Value
Review Schedule Automatic excluding drafts
Max Issue Count 10
Automatic PR Descriptions
Issue Categories
Category Enabled
Naming
Database Operations
Documentation
Logging
Error Handling
Systems and Environment
Objects and Data Structures
Readability and Maintainability
Asynchronous Processing
Design Patterns
Third-Party Libraries
Performance
Security
Functionality

Feedback and Support

Note

Korbit Pro is free for open source projects 🎉

Looking to add Korbit to your team? Get started with a free 2 week trial here

Copy link

codecov bot commented Jan 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.32%. Comparing base (76d897e) to head (68726de).
Report is 1379 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #32015       +/-   ##
===========================================
+ Coverage   60.48%   83.32%   +22.83%     
===========================================
  Files        1931      544     -1387     
  Lines       76236    38924    -37312     
  Branches     8568        0     -8568     
===========================================
- Hits        46114    32433    -13681     
+ Misses      28017     6491    -21526     
+ Partials     2105        0     -2105     
Flag Coverage Δ
hive 48.50% <ø> (-0.66%) ⬇️
javascript ?
mysql 75.85% <ø> (?)
postgres 75.92% <ø> (?)
presto 53.05% <ø> (-0.75%) ⬇️
python 83.32% <ø> (+19.83%) ⬆️
sqlite 75.43% <ø> (?)
unit 60.78% <ø> (+3.16%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Copy link
Member

@mistercrunch mistercrunch left a comment

Choose a reason for hiding this comment

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

LGTM

@mistercrunch
Copy link
Member

Oh looks like you need to run ruff format and/or install pre-commit.

https://superset.apache.org/docs/contributing/development/#git-hooks

@mistercrunch
Copy link
Member

Thanks for the contribution!

@mistercrunch mistercrunch merged commit a21f184 into apache:master Jan 29, 2025
44 checks passed
tmsjordan pushed a commit to tmsdevelopment/superset that referenced this pull request Feb 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Time Grain "Week starting Monday" doesn't select data correctly
2 participants