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.

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

Unable to get error when build fails on large content files #21

Open
patridge opened this issue May 6, 2023 · 0 comments
Open

Unable to get error when build fails on large content files #21

patridge opened this issue May 6, 2023 · 0 comments

Comments

@patridge
Copy link
Contributor

patridge commented May 6, 2023

While testing converting a site originally mirrored from…we'll say "bulky" WordPress HTML, I was getting an error that I could not see because the error was at the beginning of the output after which it dumps the entire input file in question.

By default, my PowerShell terminal buffer wasn't large enough to scroll back to the actual error message.

As an attempt to find the error itself, I tried chloroplast build | Out-File buildfail.txt, but that only contained the ASCII mountain logo and a few lines of initial output without the error or file.

...
Running Build command
Chloroplast.Core.Loaders.EcmaXml.Namespace
Chloroplast.Core.Loaders.EcmaXml.Namespace
Chloroplast.Core.Loaders.EcmaXml.Namespace

This all raises a few questions and feature requests:

  • Is the build calling out to another operation somehow that prevents logging the full output like that?
  • When an error occurs, can we display a smaller chunk relevant to the error itself instead of the full input?
  • Or, can we set it up to display just the error message and any line information to find it manually?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant