599 Internal Exception - no message #93
Comments
|
@zsan Could you update your perl-build in .plenv/plugins first? |
|
But i think i am with the latest perl-build, i've just clone perl-build few minutes ago. |
|
Just to update, I think it fails randomly |
|
|
|
|
|
I suspect this is just a network failure. |
Yes i am using docker -> |
|
Then, can you provide Dockerfile that reproduces this issue? |
|
|
@zsan Thanks. I have executed 1st 2nd (with appending 3rd (with appending I have not seen any failure. |
|
@skaji Thanks. Will dig more on this, hope can reproduce the issue |
|
@zsan Any news? |
|
@skaji Yes the issue is happening randomly, so i ended up with downloading the perl package manually. Also i manually create specific directory for the file, |
|
In case anyone else finds this, I'm also getting it just in my case its nearly every time. Happens on my Centos8 virtual machine (virtual box). I'm pretty sure that '599 Internal Exception ' is coming from HTTP::Tiny. Perl-Build uses HTTP::Tinyish which is a an API wrapper over LWP, HTTP-Tiny and a few other things (it chooses the first it can find which will often be HTTP-Tiny since you get that with most Perl installs. HTTP::Tiny documentation says that 599 Error happens when you timeout and the timeout threshold is like 60 seconds by default. One thing that might be a good addition is to have some way for Perl-Build to expose a few settings that get passed down to HTTP-Tinyish, such as timeout. Some of us on slow connections will find 60 seconds is too tight Could be other stuff, HTTP::Tiny docs say Exceptions from max_size, timeout or other errors will result in a pseudo-HTTP status code of 599 and a reason of "Internal Exception". The content field in the response will contain the text of the exception. Perhaps we could better expose the content field when there's an error so that we can debug this better. I could probably make a patch for some of this if people think its a good idea. IN the meantime I worked around by installing LWP which has a more generous 180 second timeout. That seemed to fix my issues most of the time. |
|
HTTP::Tinyish also sets timeout 60sec for LWP |
|
Perl-Build tries to dump the content if status code = 599. Line 137 in 9b20e91 |
|
When the backend is curl, this patch may give us error in more detail. |
@jjn1056 Could you provide Dockerfile or something? |
|
FYI: make sure that you did not clone the "latest" release (1.30) but the master branch if you want to install Perl > 5.30. In my case I had release 1.30 which only supports until v5.29. In this case you are getting this error: CPAN::Perl::Releases::perl_tarballs is not able to resolve the tarball name from the given version and exits. |
|
I've just released Perl-Build 1.31 https://metacpan.org/release/SKAJI/Perl-Build-1.31 @zsan Can you try |
|
Closing this issue because it has not had recent activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I am trying to
plenv installand i have this error message, i am not sure if this error because of my machine's environments or something else or network failure.Do you have any ideas ?
The text was updated successfully, but these errors were encountered: