You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
zef error message is Less Than Awesome. It shortly states what happened but gives absolutely no clue why it happened. --verbose and --debug options do not help.
Context and Actual Behaviour
zef fetch Data::MessagePack fails:
$ zef fetch Data::MessagePack
===> Searching for: Data::MessagePack
===> Fetching [FAIL]: Data::MessagePack:ver<0.1.2> from [email protected]:pierre-vigier/Perl6-Data-MessagePack.git
Aborting due to fetch failure: Data::MessagePack:ver<0.1.2> (use --force-fetch to override)
It could be Data::MessagePack problem — the module last update was 3 years ago. However, I am complaining on zef error message. It is very laconic: "Aborting due to fetch failure". Ok, I have got that fetching failed but then I want to know why fetching failed. It could be either network issue, or problem with github, or outdated module, or problem with the local system, e. g. one of external programs like curl, git, tar, unzipis not installed, out of disk space, whatever else. Hundreds of reasons to fail are possible. I want to know it in order to fix it and fetchData::MessagePack`.
Let's try verbose output first:
$ zef --verbose fetch Data::MessagePack
===> Searching for: Data::MessagePack
===> Found: Data::MessagePack:ver<0.1.2> [via Zef::Repository::Ecosystems<p6c>]
===> Fetching [FAIL]: Data::MessagePack:ver<0.1.2> from [email protected]:pierre-vigier/Perl6-Data-MessagePack.git
Aborting due to fetch failure: Data::MessagePack:ver<0.1.2> (use --force-fetch to override)
One more message "Found: Data…", but it does not make failure reason clear. Let's try --debug now:
$ zef --debug fetch Data::MessagePack
===> Searching for: Data::MessagePack
===> Found: Data::MessagePack:ver<0.1.2> [via Zef::Repository::Ecosystems<p6c>]
===> Fetching: Data::MessagePack
[Data::MessagePack] Fetching [email protected]:pierre-vigier/Perl6-Data-MessagePack.git with plugin: Zef::Service::Shell::git+{<anon|1>}
===> Fetching [FAIL]: Data::MessagePack:ver<0.1.2> from [email protected]:pierre-vigier/Perl6-Data-MessagePack.git
Aborting due to fetch failure: Data::MessagePack:ver<0.1.2> (use --force-fetch to override)
I see one more message "Fetching…", but it does not make failure reason clear. Let's try recommended --force-fetch option:
$ zef fetch --force-fetch Data::MessagePack
===> Searching for: Data::MessagePack
===> Fetching [FAIL]: Data::MessagePack:ver<0.1.2> from [email protected]:pierre-vigier/Perl6-Data-MessagePack.git
[Data::MessagePack] Failed to fetch, but continuing with --force-fetch
Cannot resolve caller parent(IO::Path:U: ); none of these signatures match:
(IO::Path:D: Int:D $depth is copy, *%_)
(IO::Path:D: *%_)
Oops. Reason for fetch failure is still unclear.
Probably I can find some clue somewhere in ~/.zef directory?
$ find ~/.zef/store -name '*MessagePack*'
~/.zef/store does not include any file or directory named *MessagePack*.
~/.zef/tmp has a few subdirectories but no files at all.
"Aborting due to fetch failure". That's all what I allowed to know.
Expected Behavior
I expect zef carefully writes interaction with the external world to a log file. Does zef run external commands, like curl or git? Let zef write complete command line to the log before executing it. Also copy the program output to the log, as well as the program exit status. In case of failure show the path to the log file to user, e. g.:
Aborting due to fetch failure. See ~/.zef/1616531467.151151.2434.4042001098987/zef.log for details.
zef error message is Less Than Awesome. It shortly states what happened but gives absolutely no clue why it happened.
--verbose
and--debug
options do not help.Context and Actual Behaviour
zef fetch Data::MessagePack
fails:It could be
Data::MessagePack
problem — the module last update was 3 years ago. However, I am complaining on zef error message. It is very laconic: "Aborting due to fetch failure". Ok, I have got that fetching failed but then I want to know why fetching failed. It could be either network issue, or problem with github, or outdated module, or problem with the local system, e. g. one of external programs likecurl
,git
,tar
, unzipis not installed, out of disk space, whatever else. Hundreds of reasons to fail are possible. I want to know it in order to fix it and fetch
Data::MessagePack`.Let's try verbose output first:
One more message "Found: Data…", but it does not make failure reason clear. Let's try
--debug
now:I see one more message "Fetching…", but it does not make failure reason clear. Let's try recommended
--force-fetch
option:Oops. Reason for fetch failure is still unclear.
Probably I can find some clue somewhere in
~/.zef
directory?~/.zef/store
does not include any file or directory named*MessagePack*
.~/.zef/tmp
has a few subdirectories but no files at all."Aborting due to fetch failure". That's all what I allowed to know.
Expected Behavior
I expect
zef
carefully writes interaction with the external world to a log file. Doeszef
run external commands, likecurl
orgit
? Letzef
write complete command line to the log before executing it. Also copy the program output to the log, as well as the program exit status. In case of failure show the path to the log file to user, e. g.:Steps to Reproduce
Your Environment
The text was updated successfully, but these errors were encountered: