Include exit code of pre/post sync hooks when exiting? · OfflineIMAP/offlineimap#517

(2 留言) (2 反應) (0 負責人)Python (1,765 star) (373 fork)batch import

enhancementgood first issueneed contributor!

描述

General informations

system/distribution (with version): Red Hat Enterprise Linux Server release 7.4 (Maipo)
offlineimap version (offlineimap -V): offlineimap v7.1.4, imaplib2 v2.57 (bundled), Python v2.7.5, OpenSSL 1.0.1e-fips 11 Feb 2013
Python version: Python 2.7.5
server name or domain:
CLI options: timeout --foreground --signal=QUIT 4m
/path/to/offlineimap.git/offlineimap.py
-c /path/to/offlineimaprc

Steps to reproduce the error

No error as such, but I was wondering if there was some way for offlineimap to allow the exit code of presynchook or postsynchook to be returned by offlineimap itself? For example, I use a postsynchook which I've just noticed in my syslog is misbehaving, and exiting with error 127. However, offlineimap exists with zero indicating that everything is ok. Am I able to somehow make offlineimap include the exit value of the postsynchook when generating it's exit code upon exit? Or does the exit code of the pre/postsync hooks need to be managed separately (eg send result to a file for testing after offlineimap has exited)? Thanks! Matt (happy offlineimap user for many years)

貢獻者指南

技術棧: python
領域: cli
議題類型: feature
難度: 3
預計時間: half day
活動狀態: stale
清晰度: clear
前置要求: Pythonofflineimap hook mechanismexit code handling
新手友善度: 60
研究方向: Investigate the offlineimap source to locate where hooks are invoked and exit codes are collected. The main script likely contains the exit path. Also, review the offlineimap3 successor for any existing exit code handling. Since this repository is legacy, contributing to offlineimap3 may be more appropriate. Check issue comments for any prior discussion or maintainer input.