Skip to content

[typespec-go] probe: check whether Go CI already fails on main (DO NOT MERGE)#4962

Closed
msyyc wants to merge 1 commit into
Azure:mainfrom
msyyc:msyyc/check-go-ci-on-main
Closed

[typespec-go] probe: check whether Go CI already fails on main (DO NOT MERGE)#4962
msyyc wants to merge 1 commit into
Azure:mainfrom
msyyc:msyyc/check-go-ci-on-main

Conversation

@msyyc

@msyyc msyyc commented Jul 20, 2026

Copy link
Copy Markdown
Member

Draft / do-not-merge — diagnostic probe.

Purpose: confirm that Go CI already fails on main independently of #4874's downstream-CI wiring.

The Regenerate step (pnpm run tspcompile) is expected to fail with:

lropaging.tsp - error @azure-tools/typespec-go/InternalError
Error: paged method PostPagingLroWithBody has no synthesized response type

Root cause: the postPagingLroWithBody ARM scenario was added to packages/azure-http-specs/.../operation-templates/lropaging.tsp in #4632 (specs-only). The go emitter (autorest.go) doesn't support it yet. On main, ci-go.yml only triggers on packages/typespec-go/**, so #4632 never ran it and the break stayed latent.

This PR adds one inert file under packages/typespec-go/** to trigger ci-go.yml. If the Go / Mock API Tests job fails at Regenerate with the error above, it proves the failure is a pre-existing emitter bug, not a defect in #4874.

Will be closed once CI status is confirmed.

Draft-only. Adds an inert file under packages/typespec-go/** to trigger the
standalone ci-go.yml on main and confirm the "Regenerate" step fails on the
new ARM scenario postPagingLroWithBody (azure-http-specs Azure#4632), independent
of PR Azure#4874's downstream-CI wiring. To be closed/reverted.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 62793370-fd78-402e-b139-26588818aa1e
@microsoft-github-policy-service microsoft-github-policy-service Bot added the emitter:go Issues for @azure-tools/typespec-go emitter label Jul 20, 2026
@msyyc msyyc changed the title [typespec-go] probe: check whether Go CI already fails on main [typespec-go] probe: check whether Go CI already fails on main (DO NOT MERGE) Jul 20, 2026
@azure-sdk-automation

Copy link
Copy Markdown
Contributor

❌ There is undocummented changes. Run chronus add to add a changeset or click here.

The following packages have changes but are not documented.

  • @azure-tools/typespec-go
Show changes

@pkg-pr-new

pkg-pr-new Bot commented Jul 20, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@azure-tools/typespec-go@4962

commit: f77c40e

@msyyc msyyc closed this Jul 20, 2026
@msyyc
msyyc deleted the msyyc/check-go-ci-on-main branch July 20, 2026 09:29
@azure-sdk-automation

Copy link
Copy Markdown
Contributor

You can try these changes here

🛝 Playground 🌐 Website

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

Labels

emitter:go Issues for @azure-tools/typespec-go emitter

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant