Azure Confidential Ledger TSP causes RUST emitter to fail
@heaths is already working on this.
Since Mar 2, 2026.
Assessment
This issue has not been assessed yet.
Description
The problem appears to be related to the content-type header when handling errors - the rust emitter believes that there are conflicting content-type headers requested on errors.
Q:/src/azure-sdk-for-rust/sdk/confidentialledger/{namespace}/TempTypeSpecFiles/Microsoft.CodeTransparency/main.tsp:41:4 - error @azure-tools/typespec-rust/InternalError: The emitter encountered an internal error during preprocessing. Please open an issue at https://github.com/Azure/typespec-rust/issues and include the complete error message.
method getTransparencyConfigCbor has conflicting content types
Error: method getTransparencyConfigCbor has conflicting content types
at getResponseFormat (file:///Q:/src/azure-sdk-for-rust/sdk/confidentialledger/%7Bnamespace%7D/TempTypeSpecFiles/node_modules/@azure-tools/typespec-rust/dist/src/tcgcadapter/adapter.js:1312:27)
at Adapter.adaptMethod (file:///Q:/src/azure-sdk-for-rust/sdk/confidentialledger/%7Bnamespace%7D/TempTypeSpecFiles/node_modules/@azure-tools/typespec-rust/dist/src/tcgcadapter/adapter.js:1366:32)
at Adapter.recursiveAdaptClient (file:///Q:/src/azure-sdk-for-rust/sdk/confidentialledger/%7Bnamespace%7D/TempTypeSpecFiles/node_modules/@azure-tools/typespec-rust/dist/src/tcgcadapter/adapter.js:1019:18)
at Adapter.adaptClients (file:///Q:/src/azure-sdk-for-rust/sdk/confidentialledger/%7Bnamespace%7D/TempTypeSpecFiles/node_modules/@azure-tools/typespec-rust/dist/src/tcgcadapter/adapter.js:786:22)
at Adapter.tcgcToCrate (file:///Q:/src/azure-sdk-for-rust/sdk/confidentialledger/%7Bnamespace%7D/TempTypeSpecFiles/node_modules/@azure-tools/typespec-rust/dist/src/tcgcadapter/adapter.js:76:14)
- Dominant language
- Rust
- Stars
- 8
- Forks
- 11
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read 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 Azure/typespec-rust
-
CodeGen rust
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Azure/typespec-rust#959 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
Azure/typespec-rust#1032 ·
-
CodeGen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/typespec-rust#1029 ·
-
CodeGen
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Azure/typespec-rust#1028 ·
-
CodeGen
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Azure/typespec-rust#1020 ·
All issues in Azure/typespec-rust
Similar issues
-
[Misdetection] `text/tab-separated-values` file misdetected as `text/tsv`Possibly taken @bact claimed this today. Openmisdetection needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
C-bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
vxc prints a debug line '[flat-codegen] emitted module via the flat path' on every compilePossibly taken @YodHeVauHe claimed this today. Opendevex good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
Unused dependenciesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day