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

Usfm parse error logging #191

Merged
merged 1 commit into from
Apr 22, 2024
Merged

Usfm parse error logging #191

merged 1 commit into from
Apr 22, 2024

Conversation

johnml1135
Copy link
Collaborator

@johnml1135 johnml1135 commented Apr 22, 2024

Fixes:
sillsdev/serval#376
sillsdev/serval#375


This change is Reviewable

@johnml1135 johnml1135 requested a review from ddaspit April 22, 2024 16:19
@codecov-commenter
Copy link

codecov-commenter commented Apr 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.15%. Comparing base (321c6e7) to head (067b83d).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #191      +/-   ##
==========================================
+ Coverage   67.12%   67.15%   +0.02%     
==========================================
  Files         441      441              
  Lines       34890    34890              
  Branches     4672     4672              
==========================================
+ Hits        23421    23430       +9     
+ Misses      10376    10368       -8     
+ Partials     1093     1092       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@ddaspit ddaspit left a comment

Choose a reason for hiding this comment

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

Reviewed 8 of 8 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @johnml1135)


src/SIL.Machine/Corpora/UsfmFileText.cs line 48 at r1 (raw file):

                }
            }
            // It's not in the file contents, let's just pull it from the filename

I don't believe that this will fix the issue. The crash is occurring in UsfmZipText. Also, this is not generic enough, since the file name in a PT project is configurable. We should use the file naming setting in the PT project settings to determine how to properly parse the file name. I think we should wait until we get more information before we submit a fix for this issue.

@johnml1135
Copy link
Collaborator Author

src/SIL.Machine/Corpora/UsfmFileText.cs line 48 at r1 (raw file):

Previously, ddaspit (Damien Daspit) wrote…

I don't believe that this will fix the issue. The crash is occurring in UsfmZipText. Also, this is not generic enough, since the file name in a PT project is configurable. We should use the file naming setting in the PT project settings to determine how to properly parse the file name. I think we should wait until we get more information before we submit a fix for this issue.

Fine enough - I reverted the fix. The other work is more important for today.

* \d recognized as "verseText" but when unloading the marker, as Non-Verse text.
* Add tests to verify it works
* Add test framework to parse any set of paratext projects
Copy link
Contributor

@ddaspit ddaspit left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @johnml1135)

@johnml1135 johnml1135 merged commit ae53a3c into master Apr 22, 2024
4 checks passed
@ddaspit ddaspit deleted the usfm_parse_error_logging branch April 23, 2024 15:20
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.

3 participants