adept/full-fledged-hledger

Error downloading lts-16.12 build plan

josephmturner opened this issue · 7 comments

On Ubuntu 20.04, I installed stack, ran export.sh, and got this error:

Downloading lts-16.12 build plan ...
RedownloadInvalidResponse Request {
  host                 = "raw.githubusercontent.com"
  port                 = 443
  secure               = True
  requestHeaders       = []
  path                 = "/fpco/lts-haskell/master//lts-16.12.yaml"
  queryString          = ""
  method               = "GET"
  proxy                = Nothing
  rawBody              = False
  redirectCount        = 10
  responseTimeout      = ResponseTimeoutDefault
  requestVersion       = HTTP/1.1
}
 "/home/paula/.stack/build-plan/lts-16.12.yaml" (Response {responseStatus = Status {statusCode = 404, statusMessage = "Not Found"}, responseVersion = HTTP/1.1, responseHeaders = [("Connection","keep-alive"),("Content-Length","14"),("Content-Security-Policy","default-src 'none'; style-src 'unsafe-inline'; sandbox"),("Strict-Transport-Security","max-age=31536000"),("X-Content-Type-Options","nosniff"),("X-Frame-Options","deny"),("X-XSS-Protection","1; mode=block"),("Content-Type","text/plain; charset=utf-8"),("X-GitHub-Request-Id","C380:7049:BD16A0:F3F35D:6046FBC0"),("Accept-Ranges","bytes"),("Date","Tue, 09 Mar 2021 04:38:24 GMT"),("Via","1.1 varnish"),("X-Served-By","cache-dfw18647-DFW"),("X-Cache","MISS"),("X-Cache-Hits","0"),("X-Timer","S1615264705.874195,VS0,VE86"),("Vary","Authorization,Accept-Encoding"),("Access-Control-Allow-Origin","*"),("X-Fastly-Request-ID","f2165773f2d8d36244d6e59bc70bb2a30d81d3a2"),("Expires","Tue, 09 Mar 2021 04:43:24 GMT"),("Source-Age","0")], responseBody = (), responseCookieJar = CJ {expose = []}, responseClose' = ResponseClose})
adept commented

Thanks, updated to more recent LTS resolver

Thank you! I am still getting an error on the same computer:

Downloading lts-16.31 build plan ...
RedownloadInvalidResponse Request {
  host                 = "raw.githubusercontent.com"
  port                 = 443
  secure               = True
  requestHeaders       = []
  path                 = "/fpco/lts-haskell/master//lts-16.31.yaml"
  queryString          = ""
  method               = "GET"
  proxy                = Nothing
  rawBody              = False
  redirectCount        = 10
  responseTimeout      = ResponseTimeoutDefault
  requestVersion       = HTTP/1.1
}
 "/home/paula/.stack/build-plan/lts-16.31.yaml" (Response {responseStatus = Status {statusCode = 404, statusMessage = "Not Found"}, responseVersion = HTTP/1.1, responseHeaders = [("Connection","keep-alive"),("Content-Length","14"),("Content-Security-Policy","default-src 'none'; style-src 'unsafe-inline'; sandbox"),("Strict-Transport-Security","max-age=31536000"),("X-Content-Type-Options","nosniff"),("X-Frame-Options","deny"),("X-XSS-Protection","1; mode=block"),("Content-Type","text/plain; charset=utf-8"),("X-GitHub-Request-Id","D33A:34CA:5612E:80F1E:606615BC"),("Accept-Ranges","bytes"),("Date","Thu, 01 Apr 2021 18:49:32 GMT"),("Via","1.1 varnish"),("X-Served-By","cache-lax10633-LGB"),("X-Cache","MISS"),("X-Cache-Hits","0"),("X-Timer","S1617302972.293461,VS0,VE144"),("Vary","Authorization,Accept-Encoding"),("Access-Control-Allow-Origin","*"),("X-Fastly-Request-ID","531a1e3e56249fe6803747ef209d52cf0e4c95c0"),("Expires","Thu, 01 Apr 2021 18:54:32 GMT"),("Source-Age","0")], responseBody = (), responseCookieJar = CJ {expose = []}, responseClose' = ResponseClose})

Perhaps there's something cached which I need to remove? This really is uncharted territory for me :)

adept commented

Sorry, I can't reproduce this locally, and from where I am sitting, lts-16.31 is definitely downloadable.

What exactly are you running, and in what environment?

Apologies for the late response :)

I am running Ubuntu 20.04.
Stack has been installed from the Ubuntu repo.
which runhaskell reveals /usr/bin/runhaskell
which stack reveals /usr/bin/stack
Running the export.sh script inside /path/to/full-fledged-ledger/01-getting-started/ yields the error I posted above.

I am happy to run any diagnostic commands you like! I'm not sure exactly what more I might tell you about my environment.

There are sometimes transient problems with stack's communications with the servers. Try running stack commands repeatedly and at different times to see how often you can reproduce (perhaps stack update and/or stack install --resolver lts-16.31 --dry-run).

adept commented

Yeah, my first suspicion would've been potentially dated version of stack packaged in ubuntyu. @josephmturner , what is the output of stack --version ?

Thank you - the issue was that I had an outdated version of stack. After upgrading stack, the issue went away!