Skip to content

fix(aci): make snuba query validator timeWindow in seconds #93656

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

Merged
merged 5 commits into from
Jun 17, 2025

Conversation

ameliahsu
Copy link
Member

@ameliahsu ameliahsu commented Jun 16, 2025

we store the timeWindow in seconds, so we should just have the validator accept seconds

unfortunately the alert rule endpoints also share this serializer and i don't want to change their behavior, so we have to pass in a timeWindowSeconds param

@ameliahsu ameliahsu requested review from a team as code owners June 16, 2025 20:51
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jun 16, 2025
Copy link

codecov bot commented Jun 16, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #93656      +/-   ##
==========================================
- Coverage   79.41%   79.19%   -0.22%     
==========================================
  Files       10324    10324              
  Lines      595767   595706      -61     
  Branches    23137    23132       -5     
==========================================
- Hits       473113   471793    -1320     
- Misses     122161   123420    +1259     
  Partials      493      493              

@ameliahsu ameliahsu enabled auto-merge (squash) June 17, 2025 17:40
@ameliahsu ameliahsu merged commit e27c7b0 into master Jun 17, 2025
63 checks passed
@ameliahsu ameliahsu deleted the mia/aci/time-window-seconds branch June 17, 2025 17:45
Copy link

sentry-io bot commented Jun 17, 2025

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

  • ‼️ ValidationError: {"inputChannelId":"inputChannelId collides with input_channel_id, please pass only one value"} sentry.integrations.slack.tasks.search_channel_... View Issue
  • ‼️ ValidationError: {"inputChannelId":"inputChannelId collides with input_channel_id, please pass only one value"} integrations:sentry.integrations.slack.tasks.se... View Issue
  • ‼️ ValidationError: {"inputChannelId":"inputChannelId collides with input_channel_id, please pass only one value"} sentry.integrations.slack.tasks.search_channel_... View Issue

Did you find this useful? React with a 👍 or 👎

andrewshie-sentry pushed a commit that referenced this pull request Jun 19, 2025
we store the timeWindow in seconds, so we should just have the validator
accept seconds

unfortunately the alert rule endpoints also share this serializer and i
don't want to change their behavior, so we have to pass in a
`timeWindowSeconds` param
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants