-
Notifications
You must be signed in to change notification settings - Fork 501
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.
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
Test failure with Boost 1.77.0 (regress/BF3C1F82-2.test) #2075
Comments
Having the same problem. On a ledger file that was reconciled and balanced, I am seeing the following when doing ledger-reconcile:
Also have the problem of
|
54 tasks
Yep, this also breaks things like |
Same problem here.
|
ghost
mentioned this issue
Mar 9, 2022
tbm
pushed a commit
that referenced
this issue
Mar 9, 2022
Ensure the path of file to include in `instance_t::include_directive` is always an absolute path. Previously when the journal file is given through stdin, we prepend a "./" to the filename to include. However, in Boost >= 1.77, `path::normalize` strips the leading "./" [1]. Our `resolve_path` function calls `normalize` and thus now it returns "file" for "./file" instead of the previous "./file". This change causes a failing test regress/BF3C1F82-2 [2], and also breaks the `include` directive for stdin input: $ touch file-to-include $ echo "include file-to-include" | ledger -f - reg gives While parsing file "", line 1: Error: File to include was not found: "file-to-include" Therefore, we change to prepend the `context.current_directory` to make the filename absolute in this case as well. The test regress/BF3C1F82-2 is also updated to match the new output. Fixes #2075. [1] boostorg/filesystem@16bd89b [2] #2075
bcc32
added a commit
to bcc32/nixpkgs
that referenced
this issue
Dec 24, 2022
marsam
added a commit
to NixOS/nixpkgs
that referenced
this issue
Jan 3, 2023
ledger: Import patch to fix ledger/ledger#2075
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Doesn't seem too serious, but I'm not sure what's causing it (also fails with Boost 1.78.0, though 1.76.0 was fine):
The text was updated successfully, but these errors were encountered: