Re: Interrupted system call

From: Santiago Torres Arias <santiago@nyu.edu>
Date: Jul 1, 2020, 14:22 UTC
Message-ID: <20200701142205.3gwltulmkrd6iljk@LykOS.localdomain>
In-Reply-To: <c8061cce-71e4-17bd-a56a-a5fed93804da@neanderfunk.de>

Hi,

Show 9 quoted lines

> Nevertheless, I am surprised to get such an "Interrupted system call" from
> Git. A long time ago I learnt that it is OK for many syscalls to get
> interrupted, so you have to loop around them. See here for more information:
> 
> https://urldefense.proofpoint.com/v2/url?u=http-3A__250bpm.com_blog-3A12&d=DwICaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=yZMPY-APGKyVIX7HgQFZJA&m=JwtG1XJ8aqvchYKsbjW23-PqEl4qm4xuOrYLaF8MOK4&s=k58MMdPdIRPl0kpuTohwZo_3GbW7elvojU1wjTil2GY&e=
> 
> As a result, users should never actually get an "Interrupted system call"
> error from any software, at least when no sockets or non-blocking I/O is
> involved.

I'm not sure if you can blame git right away (it could be an underlying library), and I'm also not convinced that "interrupted system call" is an error that should never exist for users (error handling is generally very nuanced).

I'd advice to use GIT_TRACE_FSMONITOR or just GIT_TRACE to figure out what component is the last one in place before things failed. You can read about these on the manpage on the "other" subsection of the "ENVIRONMENT VARIABLES" section.

I hope this helps! -Santiago