[wp-trac] [WordPress Trac] #62029: Do not bloat Debug Log with Scraping home page… when auto upgrade is OK

[WordPress Trac]

#62029: Do not bloat Debug Log with Scraping home page… when auto upgrade is OK
-----------------------------+---------------------
 Reporter:  georgwordpress   |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  6.7
Component:  Upgrade/Install  |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:
-----------------------------+---------------------

Comment (by georgwordpress):

 And now I had seen the Rollback Auto Update function in action:
 I build a plugin with a unkown function => fatal error in the plugin init
 function.
 Now WP detect this buggy plugin update and made a rollback.

 So - the main issue is not the bloated debug log.

 If in some wp installations the Loopback request is redirected - there
 will be no error detection of the updated buggy plugin.

 Or the other way round:
 if the automatic wp updater did not find his needle ('######
 wp_scraping_result_start:') then this is only the result of the redirected
 loopback request - in this constellation it does not matter whether the
 update is buggy or not.

 As @stoyangeorgiev already mentioned:
 The PR is missleading https://github.com/WordPress/wordpress-
 develop/pull/7359/files

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62029#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform