I don't know it is issue or not proper command usage, when I stack ls snapshots,
it shows up with just hash-like strings.
10dd1c78b631dabebeb49aa1024132b3ca92b95c09c19191b52ba544d41c1ff9
2a4da67a2f9ad9907c1bf262af2f1f1fe07b30abc7830856f6adb768f65dad19
3252ed0865c05cddb15a0cc798e2d6c1eefa4195f466234060bbf9f34b6044fe
59c4dad5db614495606d330cdb42e1d0dda9a0502577cc9d2f25c48392c97c9f
714fd6975ca6ceafb81f1104f7acdd26328b2e9d3d1676f80d9424400816f497
7ea66f155cec685fc856492aac9e7c6858453bd623ec4a209ff847b74fee96ea
8b0a5993409dda60ec7f14938030cc6930d6ccd86afdec343f4237657b6d7454
d3f2b494585dd8c121faae4ca314be101416011924cdd1760c7b5fc7208e2714
(END)
Is it something wrong or just not proper command usage?
other things, which are, I think, basic, new, build, exec, run etc works fine.
stack ls dependencies works fine, too.
$ stack ls dependencies
array 0.5.4.0
base 4.13.0.0
containers 0.6.2.1
deepseq 1.4.4.0
ghc-prim 0.5.3
integer-gmp 1.0.2.0
parallel 3.2.2.0
rts 1.0
test-stack 0.1.0.0
$ stack --version
Version 2.3.1, Git revision de2a7b694f07de7e6cf17f8c92338c16286b2878 (8103 commits) x86_64 hpack-0.33.0
curl -sSL https://get.haskellstack.org/ | sh
That's definitely a bug. It behaviour should be like this: https://github.com/commercialhaskell/stack/pull/3252
@psibi unfortunately that behavior was broken by the main change introduced in Stack 2 - implicit snapshots, I'm not sure how old behavior of local snapshots command could be restored to the one that was there in version 1.
BTW remote snapshots are clearly broken as well:
$ stack ls snapshots remote
JSONParseException Request {
host = "www.stackage.org"
port = 443
secure = True
requestHeaders = [("Accept","application/json"),("Accept","application/json"),("User-Agent","The Haskell Stack")]
path = "/snapshots"
queryString = ""
method = "GET"
proxy = Nothing
rawBody = False
redirectCount = 10
responseTimeout = ResponseTimeoutDefault
requestVersion = HTTP/1.1
}
(Response {responseStatus = Status {statusCode = 200, statusMessage = "OK"}, responseVersion = HTTP/1.1, responseHeaders = [("Date","Sun, 07 Jun 2020 21:26:59 GMT"),("Content-Type","text/html; charset=utf-8"),("Transfer-Encoding","chunked"),("Connection","keep-alive"),("Set-Cookie","__cfduid=d5982a79017c2da2c674de5c08f322d231591565219; expires=Tue, 07-Jul-20 21:26:59 GMT; path=/; domain=.stackage.org; HttpOnly; SameSite=Lax; Secure"),("Vary","Accept, Accept-Language, Accept-Encoding"),("X-XSS-Protection","1; mode=block"),("Cache-Control","public, max-age=21600"),("Strict-Transport-Security","max-age=15724800; includeSubDomains"),("CF-Cache-Status","HIT"),("Age","1510"),("cf-request-id","0332470cff0000c3c54d036200000001"),("Expect-CT","max-age=604800, report-uri=\"https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct\""),("Server","cloudflare"),("CF-RAY","59fd745b3c53c3c5-LED"),("Content-Encoding","gzip")], responseBody = (), responseCookieJar = CJ {expose = [Cookie {cookie_name = "__cfduid", cookie_value = "d5982a79017c2da2c674de5c08f322d231591565219", cookie_expiry_time = 2020-07-07 21:26:59 UTC, cookie_domain = "stackage.org", cookie_path = "/", cookie_creation_time = 2020-06-07 21:26:59.100239285 UTC, cookie_last_access_time = 2020-06-07 21:26:59.100239285 UTC, cookie_persistent = True, cookie_host_only = False, cookie_secure_only = True, cookie_http_only = True}]}, responseClose' = ResponseClose}) (ParseError {errorContexts = [], errorMessage = "Failed reading: not a valid json value", errorPosition = 1:1 (0)})
@qrilka Thanks for the info. It seems with @snoyberg 's change here https://github.com/fpco/stackage-server/issues/292#issuecomment-641051503 , the remote snapshots has started to work again:
$ stack ls snapshots remote
a month ago
Resolver name: nightly-2020-05-10
Stackage Nightly 2020-05-10 (ghc-8.8.3)
Resolver name: nightly-2020-05-07
Stackage Nightly 2020-05-07 (ghc-8.8.3)
Resolver name: nightly-2020-05-06
Stackage Nightly 2020-05-06 (ghc-8.8.3)