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

stack update not run automatically after deleting/corrupting repo #2466

Closed
Blaisorblade opened this issue Aug 9, 2016 · 1 comment
Closed

stack update not run automatically after deleting/corrupting repo #2466

Blaisorblade opened this issue Aug 9, 2016 · 1 comment
Labels
type: bug
Milestone
P2: Should

Comments

@Blaisorblade
Copy link
Collaborator

From #2175 (comment)

I've just gotten Left ... after rm -rf ~/.stack/indices/Hackage/git-update—somehow, stack did not figure out it needed to refetch the repo.

This might relate to @rainbyte and @schell's Left ... messages in #2175, though those both mention Left ~/.stack/indices/Hackage/git-update/all-cabal-hashes/.git/objects/pack and are in Docker containers.
Can we get reproductions of the issue when passing -v to stack, to get better logs?
@mgsloan mgsloan added this to the P2: Should milestone Aug 9, 2016
@mgsloan
Copy link
Contributor

mgsloan commented Mar 18, 2017

These errors no longer get outputted, closing.

@mgsloan mgsloan closed this as completed Mar 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug
Projects
None yet
Milestone
P2: Should
Development

No branches or pull requests
2 participants
@mgsloan @Blaisorblade