-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
object-file: pass filename to fsync_or_die #1194
object-file: pass filename to fsync_or_die #1194
Conversation
If we die while trying to fsync a loose object file, pass the actual filename we're trying to sync. This is likely to be more helpful for a user trying to diagnose the cause of the failure than the former 'loose object file' string. It also sidesteps any concerns about translating the die message differently for loose objects versus something else that has a real path. Reported-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Neeraj Singh <neerajsi@microsoft.com>
/submit |
Submitted as pull.1194.git.1648664055986.gitgitgadget@gmail.com To fetch this version into
To fetch this version to local tag
|
This branch is now known as |
This patch series was integrated into seen via git@1c2d173. |
There was a status update in the "New Topics" section about the branch When creating a loose object file, we didn't report the exact filename of the file we failed to fsync, even though the information was readily available, which has been corrected. Will merge to 'next'. source: <pull.1194.git.1648664055986.gitgitgadget@gmail.com> |
This patch series was integrated into seen via git@26d1013. |
This patch series was integrated into next via git@9de1909. |
This patch series was integrated into seen via git@656a3cf. |
This patch series was integrated into seen via git@7f77b4d. |
This patch series was integrated into seen via git@98f6a3a. |
This patch series was integrated into master via git@98f6a3a. |
This patch series was integrated into next via git@98f6a3a. |
Closed via 98f6a3a. |
If we die while trying to fsync a loose object file, pass the actual
filename we're trying to sync. This is likely to be more helpful for a
user trying to diagnose the cause of the failure than the former
'loose object file' string. It also sidesteps any concerns about
translating the die message differently for loose objects versus
something else that has a real path.
Reported-by: Ævar Arnfjörð Bjarmason avarab@gmail.com
Signed-off-by: Neeraj Singh neerajsi@microsoft.com
This is in response to:
https://lore.kernel.org/git/220321.861qyv9rjr.gmgdl@evledraar.gmail.com/