Database Group Triage for week ending 2023-09-22

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.

Last week's issue

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 1 issues in need of triage, 5 issues without throughput labels, and 10 other database issues reviewed. <link to this issue>

Issues needing triage (Labeled databasetriage)

For each issue below:

1. If the issue needs further investigation, spend up to 1 hour of investigating or fixing the issue.
2. If the issue is a typebug, assign it one of severity1, severity2, severity3, or severity4
3. 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.
4. If the issue is incomplete, labeled ~"workflow::scheduled", and will take more than an hour to fix, remove databasetriage

• Seg fault in app/finders/members_finder.rb:80

Bugs needing Severity

For each issue below:

1. For each typebug, spend up to 1 hour investigating or fixing the issue.
2. Assign it one of severity1, severity2, severity3, or severity4
3. 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.

• Avoid host_list_disconnection logs when no LB hosts are disconnected

Issues with Undefined Type

For each issue below:

1. Assess if the issue is appropriately assigned to groupdatabase, if not add the correct group label.
2. 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

3. If the issue needs further investigation, add databasetriage and spend up to 1 hour of investigating the issue.
4. 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.

• Potential bug-risk: To redirect both stdout and stderr, 2>&1 must be last (or use '{ cmd > file; } 2>&1' to clarify)
• Audit required: Exposure of directory listing using net/http.FileServer
• Schema validation report
• why is 15.11.13 a required upgrade stop?
• error dumping the contents of table "merge_request_diff_files" failed PQgetResult failed

Recent issues labeled database

For each issue below:

1. If the issue has no group label, consider if it should be addressed by groupdatabase and if so label it.
2. 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

• groupsource code Design an efficient ClickHouse schema
• groupsource code Project level MR approval rules UI changes
• groupsource code Inherit rules from Group level to Project level
• groupthreat insights tmp_index_vulnerability_occurrences_uuid_cast synchronous database index(es) addition
• groupthreat insights Cleanup after vulnerability_occurrences.uuid type migration
• groupdistribution upgrade from 13.12.15 to 14.0.12 . error running gitlab-ctl reconfigure
• grouppipeline execution Remove ignore column rules for shared_runners_duration
• grouppipeline execution Remove trigger and old column shared_runners_duration
• grouppipeline execution Swap conversion columns for shared_runners_duration
• groupdistribution Docker upgrade to 16.3.2-ce.0 is error

Customer Issue Hand-offs

For each issue below:

1. If the item already has a back and forth, check in with the @jon_jenkins to see if what needs to be handed off
2. Consider if it's right for our team and if not, ask the support rep to follow up with the correct team.
3. If the item is right for our team, spend some time accessing it and trying to assist.
4. If you need help, and the request seems pressing, ask in the team channel if there's someone who can help dig into it.

• Questions regarding fine tuning PgBouncer connection pooling and PSQL max connections~"Help group::Database"

@alexives if @krasio isn't available this week, please reassign to @l.rosa cc @rogerwoo