Avoid backtraces on expected failures when built with ghc 8; only use backtraces for unexpected errors.
ghc 8 added backtraces on uncaught errors. This is great, but git-annex was using error in many places for a error message targeted at the user, in some known problem case. A backtrace only confuses such a message, so omit it. Notably, commands like git annex drop that failed due to eg, numcopies, used to use error, so had a backtrace. This commit was sponsored by Ethan Aubin.
This commit is contained in:
parent
69915c6c9b
commit
0a4479b8ec
116 changed files with 287 additions and 270 deletions
|
@ -21,7 +21,7 @@ import qualified Upgrade.V4
|
|||
import qualified Upgrade.V5
|
||||
|
||||
checkUpgrade :: Version -> Annex ()
|
||||
checkUpgrade = maybe noop error <=< needsUpgrade
|
||||
checkUpgrade = maybe noop giveup <=< needsUpgrade
|
||||
|
||||
needsUpgrade :: Version -> Annex (Maybe String)
|
||||
needsUpgrade v
|
||||
|
@ -49,8 +49,8 @@ upgrade automatic destversion = do
|
|||
go (Just "0") = Upgrade.V0.upgrade
|
||||
go (Just "1") = Upgrade.V1.upgrade
|
||||
#else
|
||||
go (Just "0") = error "upgrade from v0 on Windows not supported"
|
||||
go (Just "1") = error "upgrade from v1 on Windows not supported"
|
||||
go (Just "0") = giveup "upgrade from v0 on Windows not supported"
|
||||
go (Just "1") = giveup "upgrade from v1 on Windows not supported"
|
||||
#endif
|
||||
go (Just "2") = Upgrade.V2.upgrade
|
||||
go (Just "3") = Upgrade.V3.upgrade automatic
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue