Skip to content
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.

Sign up for GitHub

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

Jump to bottom

LTS-5.0 definition doesn't work #1702

Closed
phadej opened this issue Jan 26, 2016 · 8 comments
Closed

LTS-5.0 definition doesn't work #1702

phadej opened this issue Jan 26, 2016 · 8 comments

Comments

@phadej
Copy link
Collaborator

phadej commented Jan 26, 2016 

% stack --version
Version 1.0.3, Git revision 3ea8437e472bcc4c48a8a97285e1da6cb5ae9aa8 x86_64
% STACK_YAML=stack-lts-5.yaml stack build
Getting project config file from STACK_YAML environment
Downloaded lts-5.0 build plan.    
InvalidYaml (Just (YamlParseException {yamlProblem = "mapping values are not allowed in this context", yamlContext = "", yamlProblemMark = YamlMark {yamlIndex = 343, yamlLine = 12, yamlColumn = 14}}))
@alanz
Copy link
Contributor

alanz commented Jan 26, 2016

FIW I had that problem with nightly-2016-01-24 too

@sjakobi
Copy link
Member

sjakobi commented Jan 26, 2016

Could this be due to your versions of stack being built with that buggy version of aeson in lts-4?

Does the problem go away when you build stack with the provided stack-7.8.yaml or use e.g. stack-1.0.0?

@luigy
Copy link
Contributor

luigy commented Jan 26, 2016

Currently there is no verification that the buildplan file was not corrupted when downloading and it won't redownload if the file already exists.

In the meantime you can remove the following files to force the download to happen and hopefully it won't be corrupted
~/.stack/build-plan/lts-5.0.yaml -- I'm curious to see what this file looks like, though
~/.stack/build-plan-cache/x86_64-osx/lts-5.0.cache -- may vary according to you platform

@DanBurton
Copy link
Contributor

Is this a regression in stack-1.0.3? Or is it just an intermittent bug that happens when your download is corrupted? I'm using stack-1.0.2 and it seemed to download and parse the lts-5.0 build plan just fine.

@phadej
Copy link
Collaborator Author

phadej commented Jan 27, 2016 


<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
  <head>
    <title>503 backend read error</title>
  </head>
  <body>
    <h1>Error 503 backend read error</h1>
    <p>backend read error</p>
    <h3>Guru Mediation:</h3>
    <p>Details: cache-fra1224-FRA 1453811962 3734747786</p>
    <hr>
    <p>Varnish cache server</p>
  </body>
</html>

Was the content of my lts-5.0.yaml

@mgsloan
Copy link
Contributor

mgsloan commented Jan 27, 2016

Did it recover, or was this failure sticky? From the logic here, to me it seems like it ought to recover (as long as the server does send the right info)

@phadej
Copy link
Collaborator Author

phadej commented Jan 27, 2016

@mgsloan I had to remove the file manually

% stack --version                      
Version 1.0.3, Git revision 3ea8437e472bcc4c48a8a97285e1da6cb5ae9aa8 x86_64

mgsloan added a commit that referenced this issue Jan 27, 2016
@mgsloan
Redownload build plan if parsing fails #1702
0347cd1
@mgsloan
Copy link
Contributor

mgsloan commented Jan 27, 2016

@phadej Interesting! Looks like the code intended to handle this case, but used download instead of redownload, so the file didn't get overwritten. I've pushed a fix. Please re-open if this is still an issue.

@mgsloan mgsloan closed this as completed Jan 27, 2016
@phadej phadej mentioned this issue Jun 7, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@mgsloan @phadej @alanz @DanBurton @luigy @sjakobi