Skip to content

Fix human_size dropping trailing zeros from kilobyte sizes - #42

Closed
test-codeop wants to merge 2 commits into
doublebyte1:fix-workflowfrom
test-codeop:uncover-agent-2570134438
Closed

test-codeop wants to merge 2 commits into
doublebyte1:fix-workflowfrom
test-codeop:uncover-agent-2570134438

Conversation

@test-codeop

Copy link
Copy Markdown
Collaborator

The kilobyte branch stripped trailing zeros from an integer string, so 10240 bytes rendered as "1K" and 102400 bytes as "1K" in the STAC HTML templates. The rstrip is only needed for the decimal formats.

Overview

Related Issue / discussion

Additional information

Dependency policy (RFC2)

  • I have ensured that this PR meets RFC2 requirements

Updates to public demo

Contributions and licensing

(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)

  • I'd like to contribute [feature X|bugfix Y|docs|something else] to pygeoapi. I confirm that my contributions to pygeoapi will be compatible with the pygeoapi license guidelines at the time of contribution

  • I have already previously agreed to the pygeoapi Contributions and Licensing Guidelines

  • Original PR: Fix human_size dropping trailing zeros from kilobyte sizes geopython/pygeoapi#2416

  • Reproduced automatically by test_create_prs.py to exercise the Detect AI workflow.

@test-codeop test-codeop closed this by deleting the head repository Oct 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant