[Bps-public-commit] app-wsgetmail branch add-quiet-mode-for-cron updated. 0.08-4-geef0d9a

[BPS Git Server]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "app-wsgetmail".

The branch, add-quiet-mode-for-cron has been updated
       via  eef0d9ad0c898b8cce3023ef7fd557b60f28e78d (commit)
      from  955ed853b2d0133b38dbae9633dca3c65409b232 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit eef0d9ad0c898b8cce3023ef7fd557b60f28e78d
Author: Brian Conry <bconry at bestpractical.com>
Date:   Mon Aug 28 16:13:22 2023 -0500

    Document the --quiet option and 503 error handling
    
    This adds documentation for the new option and behavior introduced in
    the prior two commits.  It also expands on the documentation of the
    existing --debug option.

diff --git a/lib/App/wsgetmail.pm b/lib/App/wsgetmail.pm
index c5cf7fd..18efbbf 100644
--- a/lib/App/wsgetmail.pm
+++ b/lib/App/wsgetmail.pm
@@ -451,6 +451,19 @@ Set this to 1 to preserve the temporary files after processing.
 
 When C<"debug"> is also set the filenames will be reported on STDERR.
 
+=item debug
+
+Set this to enable additional diagnostic and status messages.
+
+=item quiet
+
+Set this to put wsgetmail into C<quiet> mode. This mode intended for use in cron
+or other automation.
+
+When in C<quiet> mode wsgetmail produces no output unless there is an error, in
+which case the configuration filename and error messages will be printed to
+STDERR.
+
 =back
 
 =head1 TESTING AND DEPLOYMENT
@@ -508,8 +521,21 @@ configuration, just run wsgetmail with different configurations:
 
 Microsoft applies some limits to the amount of API requests allowed as
 documented in their L<Microsoft Graph throttling guidance|https://docs.microsoft.com/en-us/graph/throttling>.
-If you reach a limit, requests to the API will start failing for a period
-of time.
+If you reach a limit, requests to the API will start failing with HTTP status code 429 for a period of time.
+
+=head2 Office 365 API Errors
+
+Best Practical Solutions has observed that very rarely, less than one hundreth
+of a percent of the time, the Microsoft Graph API will return a 503 error code
+when attempting to list mail folder details.  The cause for this is currently
+unknown, except that it is not related to the API limits mentioned above.
+
+Despite the relative rarity, if you run wsgetmail often enough you can see this
+multiple times in a typical day.
+
+Therefore, when not running in C<debug> mode, if the API call to get the mail
+folder details returns a 503 then wsgetmail will treat it as if it received a
+success response with no messages in the folder.
 
 =head1 SEE ALSO
 

-----------------------------------------------------------------------

Summary of changes:
 lib/App/wsgetmail.pm | 30 ++++++++++++++++++++++++++++--
 1 file changed, 28 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
app-wsgetmail