Non-fatal build error in Runestone

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
build-system

Research direction

Start by reproducing the Runestone build that emits /tmptfmu08cu.xml:54:75 and inspect the source corresponding to that generated location. Determine why an image element appears where the validator rejects it; done means the build completes without this validation error.

Written by the indexing model from the issue text.

Description

/tmptfmu08cu.xml:54:75: error: element "image" not allowed here; expected the element end-tag, text or element "abbr", "acro", "ad", "alert", "am", "angles", "articletitle", "attr", "bc", "c", "ca", "cd", "chord", "copyleft", "copyright", "custom", "dataurl", "dblbrackets", "dblprime", "degree", "delete", "dl", "doubleflat", "doublesharp", "eg", "ellipsis", "em", "email", "etal", "etc", "fillin", "flat", "fn", "foreign", "icon", "idx", "ie", "init", "insert", "kbd", "langle", "latex", "ldblbracket", "lq", "lsq", "m", "md", "mdash", "midpoint", "minus", "n", "natural", "nb", "nbsp", "ndash", "notation", "obelus", "ol", "permille", "pf", "phonomark", "pilcrow", "plusminus", "pm", "prefigure", "pretext", "prime", "ps", "pubtitle", "q", "quantity", "rangle", "rdblbracket", "registered", "rq", "rsq", "scaledeg", "section-mark", "servicemark", "sharp", "solidus", "sq", "stale", "swungdash", "tag", "tage", "taxon", "term", "tex", "timeofday", "times", "timesignature", "today", "trademark", "ul", "url", "var", "viz", "vs", "webwork", "xelatex", "xetex" or "xref"

Dominant language
Python
Stars
28
Forks
42
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 RunestoneInteractive/java4python

All issues in RunestoneInteractive/java4python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.