Skip to content

Empty PR - #2302

Open
mary-georgiou wants to merge 1 commit into
masterfrom
empty-pr
Open

Empty PR#2302
mary-georgiou wants to merge 1 commit into
masterfrom
empty-pr

Conversation

@mary-georgiou

Copy link
Copy Markdown
Contributor

Empty PR (no changes).

@mary-georgiou

Copy link
Copy Markdown
Contributor Author

gitar auto apply:on

@mary-georgiou

Copy link
Copy Markdown
Contributor Author

gitar master CI is failing https://github.com/SonarSource/sonar-python/actions/runs/33827965343/job/100884577646 fix it

@gitar-bot

gitar-bot Bot commented Sep 4, 2026

Copy link
Copy Markdown

gitar auto apply:on

Got it — auto-apply is now on. I'll push fixes directly for future findings on this PR instead of just suggesting them.

(For future reference, the exact command is gitar auto-apply:on, with a hyphen.)

@gitar-bot

gitar-bot Bot commented Sep 4, 2026

Copy link
Copy Markdown

gitar master CI is failing https://github.com/SonarSource/sonar-python/actions/runs/33827965343/job/100884577646 fix it

That failing run is the scheduled build on master (triggered independently of this PR), not this PR's own CI — this PR currently has no CI failures.

The failure itself is in the python-frontend module's serializer-runner exec step (the typeshed stub serializer), which exits with code 1 before any Java compilation happens — the log doesn't show a Java/Maven compile error, just the external process failing.

Since this is a master-branch scheduled job and not something driven by this PR's diff, I don't have a change to make here without more detail from the serializer's own output (the log only surfaces the Maven wrapper's "Command execution failed" message, not the underlying Python traceback). Could you link the raw log for the serializer-runner step specifically, or confirm if this should be investigated/fixed on master directly rather than through this PR?

@mary-georgiou

Copy link
Copy Markdown
Contributor Author

gitar master CI is failing https://github.com/SonarSource/sonar-python/actions/runs/33827965343/job/100884577646 fix it in this PR.

@gitar-bot

gitar-bot Bot commented Sep 4, 2026

Copy link
Copy Markdown

Looked at the actual job log (not just the Maven wrapper message this time). The real failure is:

[ERROR] × Failed to download `mypy-extensions==1.1.0`
[ERROR] ├─▶ Failed to fetch:
[ERROR] │   https://repox.jfrog.io/artifactory/api/pypi/sonarsource-pypi/packages/.../mypy_extensions-1.1.0-py3-none-any.whl
[ERROR] ╰─▶ HTTP status client error (401) for url

uv can't authenticate to SonarSource's internal Artifactory PyPI mirror (repox.jfrog.io) to download the mypy-extensions dependency for the typeshed_serializer step. This is a 401 from the artifact registry, not a bug in this repo's code — there's nothing in python-frontend/typeshed_serializer to change that would fix an expired/misconfigured Artifactory credential in the master scheduled workflow's environment.

This also isn't something this PR (an empty PR against empty-pr) can fix — it's a credentials/secrets issue on the CI infrastructure side for the scheduled master build. It would need someone with access to the GitHub Actions secrets/Artifactory token for this repo to rotate or fix the repox.jfrog.io credentials used by that workflow.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant