Error reporting is worse/missing under ghc 9.12.2 (compared to 9.10.3)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- Medio día
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- haskell
- Área
- build-system
Línea de trabajo
The error is raised at src/Development/Shake/Internal/Rules/File.hs:179, and the issue links commit fc82eee7982cc54db8907892cd688bcd73d11d1e, which may already address this. Start by checking whether that commit is in the current master, then run the Example.hs script under GHC 9.12.2 to see whether the 'rule finished running but did not produce file' message appears. Done means the missing-output error is reported with its message and call site under 9.12.2, as it is under 9.10.3.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Hi - thanks for your work on shake. I noticed that the error reporting degraded somewhat under ghc 9.12.2:
In a Example.hs like:
#!/usr/bin/env cabal
{- cabal:
build-depends:
base
, shake
-}
import Development.Shake
main :: IO ()
main = shakeArgs shakeOptions $ do
want ["foo.txt"]
"*.txt" %> \out -> do
pure ()
Running this with ghc 9.10.3:
~
❮ ghcup set ghc 9.10.3
[ Info ] GHC 9.10.3 successfully set as default version
Gives a helpful error message:
~
↪ ./Example.hs
Error when running Shake build system:
at want, called at /path/to/Example.hs:14:3 in fake-package-0-inplace-script-Example.hs:Main
* Depends on: foo.txt
at error, called at src/Development/Shake/Internal/Rules/File.hs:179:58 in shake-0.19.8-488b5a5cc87df829ac1c6a3ebfeceebc03fee9a278623f5d982bfc78c9b4a532:Development.Shake.Internal.Rules.File
* Raised the exception:
Error, rule finished running but did not produce file:
foo.txt
But with ghc 9.12.2:
ghcup set ghc 9.12.2
It returns:
cabal-script-Example.hs: Uncaught exception ghc-internal:GHC.Internal.Exception.ErrorCall:
ErrorCallWithLocation has been deprecated in favour of ErrorCall (which does not have a location). Backtraces are now handled by the backtrace exception mechanisms exclusively.
HasCallStack backtrace:
error, called at libraries/ghc-internal/src/GHC/Internal/Exception.hs:184:68 in ghc-internal:GHC.Internal.Exception
Update: Looks like there were already some commits related to this (https://github.com/ndmitchell/shake/commit/fc82eee7982cc54db8907892cd688bcd73d11d1e). Is only a release missing?
- Lenguaje dominante
- Haskell
- Estrellas
- 802
- Forks
- 128
- Merge medio
- 3 d 5 h
- PR fusionados (30 d)
- 2
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ndmitchell/shake
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
ndmitchell/shake#858 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
ndmitchell/shake#843 ·
-
Support for Exception annotationAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 15/100
ndmitchell/shake#859 · 1 comentario ·
-
Dificultad 4/5 Más de una semana Aptitud para principiantes 15/100
ndmitchell/shake#856 · 1 comentario ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
ndmitchell/shake#854 ·
Todos los issues de ndmitchell/shake
Issues similares
-
MorphRule, DataizeRule and ContextualizeRule silently accept unknown YAML keys, unlike rewrite `Rule`Posiblemente ocupada @renyamamoto2026-cmyk la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
objectionary/phino#2107 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
tweag/tricorder#640 · 1 comentario ·
Los mantenedores suelen responder en 1 día