Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Error List - Description: Limited to 1000 lines?

Open
#441 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
desktop

Research direction

Start with the error list handling for XSD validation and reproduce the reported behavior using the 65,000-employee example and the 1,000,000-line, 42 MB file described here. Determine whether the 1,000-line result limit and the later full-path, zero-line entries are intentional; done means the behavior is either corrected or clearly communicated and covered by an appropriate regression check.

Written by the indexing model from the issue text.

Description

a)
I took "employee.xml" and made with copy&paste 65000 employees, then I created a lot of errors - Streetx instead of Street. "Test" instead of "Architect" ...

The "error list" , based on the XSD, gave me results only up to (xml-)line 5600, and with copy and paste I found that the error list contains 1001 lines. If that's intend I suggest to add a line like "List sopped on 1000 lines" or something else.

Edit:

b)
Another - or a similar? - topic:
I loaded a file with 1'000'000 lines and 42MB, the schema has 421 kb. I got this result

Image
There are approx. 290 lines with errors, one of them are 550 characters long.
The last "correct" entry is for line 436528, then it changed to "full path" (for the same file) and all lines and columns are 0.

Maybe the load is too heavy for a 32bit software?

Dominant language
C#
Stars
1.2k
Forks
240
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/XmlNotepad

All issues in microsoft/XmlNotepad

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.