Database Group Triage for week ending 2023-06-30
About
This issue is used by groupdatabase to triage issues and make sure they get properly assigned and prioritized. Each week, a bot will look up the old issue, pick the next assignee in the list, and submit a new issue with a list of any issues that may need attention from the team.
Process
-
Review any issues identified for triage -
Review any issues with undefined types -
Post any questions or pressing issues to the database group meeting doc -
Post a comment on the database group status issue For triage this week there were 2 issues in need of triage, 5 issues without throughput labels, and 4 other database issues reviewed.
<link to this issue>
databasetriage)
Issues needing triage (LabeledFor each issue below:
- If the issue needs further investigation, spend up to 1 hour of investigating or fixing the issue.
- If the issue is a typebug, assign it one of severity1, severity2, severity3, or severity4
- Document any findings you make in a comment on the issue, and if the issue still needs additional work or refinement, consider looping in
@alexives
and@rogerwoo
to help with scheduling and priority. - If the issue is incomplete, labeled ~"workflow::scheduled", and will take more than an hour to fix, remove databasetriage
-
Database migration: warn when validating not null constraint on field that was backfilled via background migration -
Query Performance Investigation - [with_slack_integration service ping queries]
Issues with Undefined Type
For each issue below:
- Assess if the issue is appropriately assigned to groupdatabase, if not add the correct group label.
- Add the proper work type label, or if the issue is a request for support, redirect the user to our support resources with the following message:
Hey @author. Based on the information given, this request for support is out of the scope of the issue tracker (which is for new bug reports and feature proposals). Unfortunately, I won't be able to help get it resolved. However, for support requests we have several resources that you can use to find help and support from the Community, including: * [Technical Support for Paid Tiers](https://about.gitlab.com/support/) * [Community Forum](https://forum.gitlab.com/) * [Reference Documents and Videos](https://about.gitlab.com/get-help/#references) Please refer to our [Support page](https://about.gitlab.com/support/) for more information. If you believe this was closed in error, please feel free to re-open the issue. /label ~"support request" /close
- If the issue needs further investigation, add databasetriage and spend up to 1 hour of investigating the issue.
- Document any findings you make in a comment on the issue, and if the issue still needs additional work or refinement, consider looping in
@alexives
and@rogerwoo
to help with scheduling and priority.
-
Database Status Summary (Week ending - 2023-07-01) -
Write rake task to find and delete orphaned migration classes -
Failure in spec/migrations/cleanup_bigint_conversion_for_merge_request_metrics_for_self_hosts_spec.rb | CleanupBigintConversionForMergeRequestMetricsForSelfHosts#up when is a self-host customer with the temporary column already dropped does nothing -
Database migration: warn when validating not null constraint on field that was backfilled via background migration -
Query Performance Investigation - [with_slack_integration service ping queries]
database
Recent issues labeledFor each issue below:
- If the issue has no
group
label, consider if it should be addressed by groupdatabase and if so label it. - If the issue has a group, and you think they may need assistance from us:
- If the issue needs further investigation, add databasetriage and spend up to 1 hour of investigating the issue.
- Document any findings you make in a comment on the issue, and if the issue still needs additional work or refinement, consider looping in
@alexives
and/or@rogerwoo
-
groupthreat insights ActiveRecord::RecordNotUnique in MigrateVulnerabilitiesFeedbackToVulnerabilitiesState background migration -
groupproduct planning Update todos records that use WorkItem as the target_type value -
groupdistribution When I upgrade the gitlab version to 14.6.1, I have the following problem -
groupcode review Follow up to async migration adding prepared_at index to merge requests
@gitlab-org/database-team
Recent mentions of For each mention below:
- If the item already has an adequate response, move on to the next
- If the mention is from someone looking to provide feedback on database review, and nobody has responded yet, set up a coffee chat with them and make a note in the thread that you did. Record feedback in the feedback issue.
- If you know how to respond to the comment, post a response
- If you don't know how, redirect with a specific mention to someone who may be able to respond
-
@dfrazao-gitlab
mentioned the team on Database social event -
@l.rosa
mentioned the team on Basic logic for tracking projects/groups visits in the backend -
@bdenkovych
mentioned the team on [Feature flag] Rollout ofupdate_personal_access_token_usage_information_every_10_minutes
@alexives if @praba.m7n isn't available this week, please reassign to @stomlinson
cc @rogerwoo
Edited by Prabakaran Murugesan