December 2024 - ghc-devs

openFile gives "file is locked" error on Linux when creating a non-existing file
by Harendra Kumar 07 Jul '25

07 Jul '25

Hi everyone, We have a long standing, elusive and intermittent test failure in streamly's file system event test suite. The code where the error emanates from looks like this: createFileWithParent :: FilePath -> FilePath -> IO () createFileWithParent file parent = do let filepath = parent </> file let dir = takeDirectory filepath putStrLn $ "createFileWithParent: file [" ++ file ++ "] dir [" ++ dir ++ "]" putStrLn $ "Ensuring dir: " ++ dir createDirectoryIfMissing True dir r <- doesDirectoryExist dir if r then do putStrLn $ "Ensured dir: " ++ dir when (not (null file)) $ do exists <- doesFileExist filepath if not exists then do putStrLn $ "Creating file: " ++ (parent </> file) openFile (parent </> file) WriteMode >>= hClose putStrLn $ "Created file: " ++ (parent </> file) else error $ "File exists: " ++ filepath else error $ "Could not create dir: " ++ dir The important thing in the code above is that we check that the file does not exist already, and we are creating it. Creating this new file intermittently fails with the following error messages, all of these are coming from prints in the above: createFileWithParent: file [file1] dir [/tmp/fsevent_dir-e1098325dc2b0880/watch-root] Ensuring dir: /tmp/fsevent_dir-e1098325dc2b0880/watch-root Ensured dir: /tmp/fsevent_dir-e1098325dc2b0880/watch-root Creating file: /tmp/fsevent_dir-e1098325dc2b0880/watch-root/file1 uncaught exception: IOException of type ResourceBusy /tmp/fsevent_dir-e1098325dc2b0880/watch-root/file1: openFile: resource busy (file is locked) How can a file that does not exist and being created be locked during creation? We see this only on Linux, the same tests always succeed on Windows and macOS. We are facing this in GHC 9.2.8, I am not sure if it is version specific because in the past I selectively disabled the tests for specific GHC versions and the error still surfaced in other GHC versions. Anything obvious that we may be missing here? Any pointers or more debug info to generate to debug this? I have not started looking into the openFile code yet, hoping someone else knowing it well might help here. Is this some other "resource busy" error which is being wrongly bucketed into "file is locked" error? Thanks, Harendra

4 20

Request for approval of account
by Mark Seemann 25 Jun '25

25 Jun '25

Hello I’d like to report a bug in GHC because an error message tells me to do so. In order to do that, I’m trying to follow the guidelines in https://gitlab.haskell.org/ghc/ghc/-/wikis/report-a-bug, so I’ve created an account. The next step, as I understand it, is to use this mailing list to request approval for he account. I’m hereby doing that. TIA Mark Seemann

2 1

Account request
by Vekhir 22 Dec '24

22 Dec '24

Good evening, After registering on gitlab.haskell.org, the site directed me to send an email to you, so you can approve the request. My focus is related to bringing new GHC releases to Arch Linux. Kind regards, Vekhir

2 1

Re: Feedback on potential change in boot library
by Andrew Lelechenko 22 Dec '24

22 Dec '24

On Thu, 28 Nov 2024 at 14:51, Andreas Klebinger via ghc-devs <ghc-devs(a)haskell.org> wrote: > For example we should probably not upgrade point releases from text-2.1.1 > to text-2.1.2 as the addition of `show` causes breakage and there seem to > be no bug fixes in the release, unless the library authors request us to do > so. There are quite a few bug fixes in text-2.1.2 actually, e. g., fixing the atomicity of putStrLn which is quite a significant improvement. I struggle to see how addition of `Data.Text.show` can break much, given that `Data.Text` is almost universally imported qualified. Returning to the original question, I’m in favour of bumping boot libraries aggressively. From the perspective of boot libraries maintainers other arrangements are both discouraging and detrimental for quality. If the only way to get feedback for a new release of, say, `bytestring` is to wait 6 months until the next major release of GHC and then wait until a new GHC gains a significant traction, then we are doomed to have bugs lurking forever. And it’s also hugely unsatisfying to spend lots of work on a new release, knowing that an average user would not benefit from it in the next few years. It could make sense to have a stricter policy when releasing a last-in-series GHC, where cost of introducing new bugs / incompatibilities is much higher (because it entails making an otherwise unplanned release). But for mid-series releases I’d recommend bumping minor versions of boot libraries as soon as possible. Best regards, Andrew

3 2

GHC 9.10.2 preparation
by Ben Gamari 21 Dec '24

21 Dec '24

Hi all, Preparations are currently underway on GHC 9.10.2. We currently have roughly 100 commits backported with another few dozen backport candidates. If you have a merge request which you want to be backported please do make sure it bears the ~"backport needed:9.10" label. Additionally, we plan on performing the following boot library version bumps: Cabal 3.12.0.0 -> 3.12.1.0 Cabal-syntax 3.12.0.0 -> 3.12.1.0 bytestring 0.12.1.0 -> 0.12.2.0 array 0.5.7.0 -> 0.5.8.0 deepseq 1.5.0.0 -> 1.5.1.0 directory 1.3.8.3 -> 1.3.9.0 filepath 1.5.2.0 -> 1.5.4.0 hpc 0.7.0.1 -> 0.7.0.2 process 1.6.19.0 -> 1.6.25.0 text 2.1.1 -> 2.1.2 unix 2.8.5.1 -> 2.8.6.0 exceptions 0.10.7 -> 0.10.9 Win32 2.14.0.0 -> 2.14.1.0 Naturally, if we find that any of these upgrades could cause significant ecosystem disruption then we may reconsider and notify the list. If things go according to plan, we expect that a prerelease will be ready by mid-January 2025, with a final release coming a few weeks later. Naturally, we will continue to report status updates on the tracking ticket [1] and will keep ghc-releases apprised if plans change. Cheers, - Ben [1] https://gitlab.haskell.org/ghc/ghc/-/issues/25433

1 0

Lift instance cause GHC build error: unknown symbol with CFFI
by Minh Le 21 Dec '24

21 Dec '24

Hi everyone, I’m building a floating-point library for Clash that uses FloPoCo. The library integrates with the MPFR library via the hmpfr Haskell bindings to perform accurate software simulations of floating-point operations. I’ve encountered build errors related to linking the MPFR library: Windows: unknown symbol 'mpfr_add' in Arithmetic.o. Linux: symbol lookup error: undefined symbol 'mpfr_custom_get_size_wrap'. Interestingly, cabal repl works as expected, but cabal build fails. This suggests a linking issue specific to the build process. Steps to Reproduce Clone the repository: https://github.com/yourcomrade/FloPoCoFloat. Install MPFR: Windows: pacman -S mingw-w64-clang-x86_64-mpfr Linux: sudo apt install libmpfr6 libmpfr-dev Check out the Error_branch. Build the project using cabal build. Expected Behavior The project should compile without errors. Notably, if cabal build fails, I would expect cabal repl to fail too, but that’s not the case. Additional Info OS: Windows 11, Ubuntu WSL 5.15 Tools: GHC 9.8.2, Cabal 3.10.3, GCC 11.4 Relevant discussion: Cabal issue: https://github.com/haskell/cabal/issues/10651 I have a discussion with Cabal maintainer and he suspects that is GHC linking issue. Does anyone have insights into resolving this issue? Any help would be appreciated. Kind regards, Minh

2 3

Using ghc-debug with ghc
by Matthew Pickering 20 Dec '24

20 Dec '24

Hi, If anyone needs to debug ghc with ghc-debug enabled I just updated the `wip/ghc-with-debug` branch. You can cherry-pick the commit from there onto your branch and the resulting compiler will have ghc-debug enabled. Thanks to Hannes and Rodrigo for contributing updates in the past which I have squashed and force pushed. Matt

1 0

posix_spawnp
by Simon Peyton Jones 20 Dec '24

20 Dec '24

When I do `./hadrian/build test` I get lots of these failures /home/simonpj/code/HEAD-20/_build/stage1/lib/../bin/ghc-iserv: createProcess: posix_spawnp: does not exist (No such file or directory) Any ideas of what might be causing this? It cripples my ability to locally test my build Thanks Simon

2 3

GitLab Account Approval Request
by Kazutaka Matsuda 19 Dec '24

19 Dec '24

Dear GHC developers, I am Kazutaka Matsuda. I would like to report an issue with type checking. Could you approve my request for a GitLab account (kztk)? Best regards, Kazutaka Matsuda

2 1

Feedback on potential change in boot library
by Ben Gamari 17 Dec '24

17 Dec '24

tl;dr. We propose that GHC more aggressively bump its boot library dependencies. Hello all, Historically, GHC minor releases have been quite conservative in bumping boot library versions, generally defaulting to retaining the versions used in the GHC-x.y.1 release unless * a request is made by a boot library maintainer, or * we discover an issue which warrants a bump The motivation for this policy is both to * minimize the potential for regressions in correctness and performance, and * reduce the potential for end-user breakage due to interface changes as even minor releases can result in considerable impact (e.g. #25411, #22633) While this policy has served us well, its conservative nature demands the vigilence of both GHC and upstream maintainers to ensure that bumps that are truly necessary do not fall through the cracks. As the flaws of this process have been more apparent recently (e.g. #24597), we have done a bit of reflection on how we might improve the status quo. Concretely, I would like feedback on the adopting the following policy going forward: > Unless guidance is provided otherwise by a library maintainer, a GHC > x.y.z release will attempt to ship the newest minor version of each > boot libray in the same major series shipped with GHC x.y.1. I believe this policy would leave less room for human error and open opportunities for automated checking. On the other hand, the more aggressive bumping of submodules may mean that users are hit with more (usually minor) compatibility issues when moving between minor GHC releases. How do others feel about this? We are particularly interested to hear from boot library maintainers but feedback from packagers and users is also very much welcome. Cheers, - Ben

9 12