Skip to content

Instantly share code, notes, and snippets.

@CarstVaartjes
Last active April 21, 2026 08:45
Show Gist options
  • Select an option

  • Save CarstVaartjes/8135a3ee7ffb6403d3da71a7c57ca0aa to your computer and use it in GitHub Desktop.

Select an option

Save CarstVaartjes/8135a3ee7ffb6403d3da71a7c57ca0aa to your computer and use it in GitHub Desktop.
FOUN-259 md-to-pdf font sizing PR assets

Font Size Test for Monospace

Context

This is a paragraph of regular body text to establish a baseline. It uses the default Avenir Next font at the configured body size. When inline code appears within this sentence, such as 400 or the string "There was an error parsing the body", the monospace font should blend naturally with surrounding text — not appear noticeably larger.

Multiple scheduled data pipelines across EU and AP production instances failed intermittently with a 400 error and "There was an error parsing the body" returned by a backend API service. Affected pipelines included Combined Trade Contract Accrual generation & output messaging, Trade Promotions Actualize Shipments / Ex-factory, and Process TTR Contract Accruals & Outbound Messaging.

Inline Code Variations

  • Short token: GIM-314
  • Variable name: user_id
  • File path: /var/log/app.log
  • HTTP status: 200 OK, 400 Bad Request, 500 Internal Server Error
  • Longer string: "There was an error parsing the body"

Code Block

def fetch_data(endpoint: str) -> dict:
    """Fetch data from the given endpoint."""
    response = requests.get(endpoint, timeout=30)
    response.raise_for_status()
    return response.json()
# Shell commands should also look proportional
curl -X POST https://api.example.com/v1/pipelines \
  -H "Content-Type: application/json" \
  -d '{"status": "running"}'

Table with Code

Status Meaning Example
200 Success Normal response
400 Bad request "There was an error parsing the body"
500 Server error Internal failure

Verdict

If inline code like GIM-314 looks roughly the same size as surrounding body text, the fix works as intended.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment