apache / apache/infrastructure-pelican

GFM meta-data parser mishandles missing EOL after last entry

Open
#72 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
3
Forks
13
PR merge metrics
No merged PRs in 30d

Description

If the last meta-data item is not followed by an EOL, the parser treats the last line as both a meta-data item and part of the body content.

This is not worth fixing on its own, but should be fixed as part of any other related fixes

Contributor guide

No contributing guide indexed for this repository

Research direction

Locate the GFM metadata parser and reproduce the case described: a final metadata entry without a trailing EOL. Check how that line is classified between metadata and body content; done means the final entry is parsed as metadata without also appearing in the body, with a regression test covering the missing EOL.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.