[Schema Inaccuracy] Example and schema mismatch for `#/paths/~1orgs~1{org}~1actions~1hosted-runners~1machine-sizes/get`

Open

#5,553 opened on Nov 3, 2025 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 55/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Stale
Tech stack: openapi
Domain: api

Research direction

Inspect the OpenAPI definition for #/paths/~~1orgs~~1{org}~~1actions~~1hosted-runners~1machine-sizes/get and the referenced example at #/components/examples/actions-hosted-runner-machine-spec/value. Compare the example with its schema, focusing on cpu_cores and machine_specs. Done means the schema and example describe the same structure.

Written by the indexing model from the issue text.

Description

feature

Schema Inaccuracy

This is the json ref for the example

#/components/examples/actions-hosted-runner-machine-spec/value

The field cpu_cores doesn't exist in the schema, but exists in the example. It should be nested under machine_specs

Here's a snippet

    1: {
>   2:   "cpu_cores" : 4,
    3:   "id" : "4-core",
    4:   "memory_gb" : 16,
    5:   "storage_gb" : 150
    6: }

Expected

The schema and example are in sync

Reproduction Steps

I could reproduce this in

fpt

Dominant language: No language data
Stars: 1.6k
Forks: 342
Avg merge: 2h 23m
Merged PRs (30d): 57

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

More from github/rest-api-description

[Schema Inaccuracy] Repository security advisory operations name `repository_advisories:read` / `repository_advisories:write` OAuth scopes that do not exist Open

feature

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

github/rest-api-description#7220 · Opened Sep 22, 2026
[Schema Inaccuracy] Missing Link header from org/security-advisories response description Open

feature

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

github/rest-api-description#7201 · Opened Sep 15, 2026
Runner deprecations: enterprise scope is in the changelog and the 404 handler but not in the description Open

feature

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

github/rest-api-description#7163 · Opened Sep 9, 2026
Runner deprecations: registration_deprecates_at is declared on the response but never returned Open

feature

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

github/rest-api-description#7162 · Opened Sep 9, 2026
configure-pages API endpoint yields anchor that doesn't exist in docs Open

feature

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

github/rest-api-description#7135 · Opened Sep 4, 2026

All issues in github/rest-api-description

Similar issues

Add full support for Excel and XML exports as email attachment Open

Area: Excel support

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

orbeon/orbeon-forms#7893 · Opened Sep 23, 2026
[essnmx] Fix typo in NXLauetof application definition Open

essnmx good first issue

Difficulty 1/5 Under an hour Newbie friendliness 95/100

scipp/ess#760 · Opened Sep 23, 2026
`IOCExtractor` always fails: `ioc_analyzer.build()` takes 1 argument but the agent dispatcher passes 2 Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

yeti-platform/yeti#1380 · Opened Sep 23, 2026
OAuth client scope handling breaks on comma-separated scope strings Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

modelcontextprotocol/python-sdk#3566 · Opened Sep 23, 2026
Bedrock: every OpenAI GPT-6 Sol/Luna call fails with 400 because the default temperature is always sent Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

griptape-ai/griptape#2353 · Opened Sep 23, 2026

More Backend & API Design issues

A short digest of beginner-friendly GitHub issues.