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

CLI renders table property keys and values as Rich markup without escaping

Open
#3,984 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start in pyiceberg/cli/output.py with RichOutput.describe_properties and inspect the other describe_* methods that render server-supplied strings. Trace the CLI output path and existing tests, if present. Done means property keys and values are rendered literally rather than interpreted as Rich markup across the affected methods.

Written by the indexing model from the issue text.

Description

bug

RichOutput.describe_properties in pyiceberg/cli/output.py adds property keys and values directly to a Rich table:

def describe_properties(self, properties: Properties) -> None:
    output_table = self._table
    for k, v in properties.items():
        output_table.add_row(k, v)
    Console().print(output_table)

Rich interprets console markup by default, so square-bracket sequences in a property key or value are treated as style tags rather than literal text. rich.markup.escape is not used anywhere in the CLI, and markup=False is not set.

The same pattern appears in the other describe_* methods that render server-supplied strings. The practical effect is that property content controls the styling of CLI output, and content with unbalanced or misleading tags can alter how surrounding rows render.


Issue investigation generated via claude, reviewed by Sung, Kevin, Fokko.

Dominant language
Python
Stars
1.1k
Forks
589
Avg merge
2d 2h
Merged PRs (30d)
70

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 apache/iceberg-python

All issues in apache/iceberg-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.