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

Centralize tool logging #9

Merged
merged 3 commits into from
Dec 13, 2020

Conversation

cpeel
Copy link
Member

@cpeel cpeel commented Dec 12, 2020

For each tool run, log information about the run into a single file in $workdir. Also output each command used and the command output. This simplifies debugging and troubleshooting.

This MR also removes outputting the pptext version on the input page (it's on the run output already) and ensures that the upload stops if the AV scanner fails to run correctly.

Testable in the central-tool-logging sandbox.

@cpeel cpeel self-assigned this Dec 12, 2020
@asylumcs
Copy link
Collaborator

Yes makes sense to me. Thank you.

ppsmq-action.php Outdated Show resolved Hide resolved
@srjfoo
Copy link
Member

srjfoo commented Dec 12, 2020

General question/comment -- and this may be for a different MR -- for pptext, under "Select wordlist language(s), is the implication that pptext should not be run if a text is in a language not listed? One of my test projects is in Dutch, which is not listed. Even if spellcheck is not possible because of a missing dictionary, I would think that some of the other checks (excluding jeebies) would be useful. Could an "Other non-English" option be added that would disable spellcheck unless a good words file is provided?

For each tool run, log information about the run into a single file
in $workdir. This simplifies debugging and troubleshooting.
If the virus scanner failed to run correctly, fail instead of silently
continuing.
@cpeel cpeel force-pushed the central-tool-logging branch from 911354a to edb4c3c Compare December 12, 2020 18:08
@cpeel
Copy link
Member Author

cpeel commented Dec 12, 2020

General question/comment -- and this may be for a different MR -- for pptext, under "Select wordlist language(s), is the implication that pptext should not be run if a text is in a language not listed? One of my test projects is in Dutch, which is not listed. Even if spellcheck is not possible because of a missing dictionary, I would think that some of the other checks (excluding jeebies) would be useful. Could an "Other non-English" option be added that would disable spellcheck unless a good words file is provided?

I'll defer that question to @asylumcs as I do not know the answer. We could make it such that the "you must pick a language" check only happens if the user does not check a language and selects spellcheck. IIRC pptext would be happy with that.

@asylumcs
Copy link
Collaborator

I think it's fine to run pptext if it's not a language on the list. Perhaps a user would not want to tick the "run spellcheck" box in some cases. And it's not really right to me to have a list anyway because there are perfectly good dictionaries loaded that do not have a checkbox. Wouldn't surprise me if Dutch were actually available. Back originally when pptext was in Python, I experimented with having the Natural Language Toolkit tell me the language so the user didn't have to chose from a list. I can't do that in Go.

@cpeel
Copy link
Member Author

cpeel commented Dec 12, 2020

I create #10 to address the pptext language selection issue that was raised.

Copy link
Contributor

@windymilla windymilla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All looks fine - good idea!

ppcomp-action.php Show resolved Hide resolved
pphtml-action.php Show resolved Hide resolved
ppsmq-action.php Show resolved Hide resolved
pptext-action.php Show resolved Hide resolved
@cpeel cpeel merged commit a1dbca6 into DistributedProofreaders:master Dec 13, 2020
@cpeel cpeel deleted the central-tool-logging branch December 13, 2020 02:02
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

Successfully merging this pull request may close these issues.

4 participants