Page MenuHomePhabricator

If daemon running-as-user setup check fails its query, don't bother with it
ClosedPublic

Authored by epriestley on Apr 3 2020, 11:12 PM.
Tags
None
Referenced Files
F15420257: D21057.diff
Fri, Mar 21, 12:36 PM
F15415222: D21057.diff
Thu, Mar 20, 4:55 AM
F15380922: D21057.diff
Fri, Mar 14, 5:00 AM
F15336171: D21057.id50168.diff
Sat, Mar 8, 6:20 PM
F15336170: D21057.id50167.diff
Sat, Mar 8, 6:20 PM
F15336169: D21057.id.diff
Sat, Mar 8, 6:20 PM
Unknown Object (File)
Mon, Mar 3, 4:38 AM
Unknown Object (File)
Feb 18 2025, 11:51 AM
Subscribers

Details

Summary

See https://discourse.phabricator-community.org/t/upgrade-from-sep-30-2016/3702/. A user performing an upgrade from 2016 to 2020 ran into an issue where this setup query is overheating.

This is likely caused by too many rows changing state during query execution, but the particulars aren't important since this setup check isn't too critical and will catch the issue eventually. It's fine to just move on if this query fails for any reason.

Test Plan

Forced the query to overheat, loaded setup issues, got overheating fatal. Applied patch, no more fatal.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Apr 3 2020, 11:19 PM
This revision was automatically updated to reflect the committed changes.
JoggerTech added inline comments.
src/applications/config/check/PhabricatorDaemonsSetupCheck.php
11

add try catch around this line to fix:
Exception
Query (of class “PhabricatorDaemonLogQuery”) overheated: examined more than 10 raw rows without finding 1 visible object