Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Database checks: ∞% reported as Failing when counter is zero; no way to acknowledge/mute a check

Aperta
  • Qualcosa non va?
#1,231 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
mariadb, php
Ambito
backend, databases

Direzione di ricerca

The issue describes the “Table lock contention” check using MariaDB’s Table_locks_waited counter, but does not name the implementation files or tests. Start by locating that check and tracing how it handles a zero denominator and reports its status. The second request needs per-check acknowledgement or muting, with a rule for when a muted finding should resurface; done means the zero-data case is not reported as failing and admins can dismiss a check as described.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

0. Needs triage bug
Setup
  • Nextcloud [your version]
  • MariaDB 10.11.18 on Debian 12, same VM as Nextcloud
1. Divide-by-zero shown as Failing

After FLUSH STATUS (or soon after a restart), "Table lock contention" (Table_locks_waited) shows ∞% of table locks had to wait and is marked Failing. When the denominator is zero the check should report "not enough data" or be skipped.

2. No way to acknowledge or mute a check

Some findings can't be resolved by the admin (e.g. #1224, or join/scan rates caused by Nextcloud core queries). Once investigated, there's no way to dismiss them, so they stay red indefinitely. Please consider a per-check acknowledge/mute option, ideally one that resurfaces if the value changes significantly.

Related: #1224

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.
Steps to reproduce
Expected behaviour

Tell us what should happen

Actual behaviour

Tell us what happens instead, if possible also add a screenshot

Server configuration

Web server: Apache/Nginx

Database: MySQL/Maria/SQLite/PostgreSQL

PHP version: 8.5/8.4/8.3

Nextcloud version: (see Nextcloud admin page)

List of activated apps 
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
Nextcloud configuration 
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
Browser

Browser name: Firefox/Chrome/Safari/…

Browser version: 124/125/…

Operating system: Windows/Ubuntu/Mac/…

Browser log 
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
Lingua principale
JavaScript
Stelle
133
Fork
67
Merge medio
22h 55m
PR unite (30g)
53

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nextcloud/serverinfo

Tutte le issue di nextcloud/serverinfo

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.