Skip to content

Conversation

@nick863
Copy link
Member

@nick863 nick863 commented Nov 1, 2025

Contributing to the Azure SDK

Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.

For specific information about pull request etiquette and best practices, see this section.

@nick863 nick863 force-pushed the nirovins/fix_unit_tests branch from 70f9c17 to f7f0ed9 Compare November 3, 2025 19:20
Copy link
Member

@jsquire jsquire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Packages changes look good.

@github-actions
Copy link

github-actions bot commented Nov 3, 2025

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Azure.AI.Agents

@nick863 nick863 force-pushed the nirovins/fix_unit_tests branch from f7f0ed9 to 476a07a Compare November 3, 2025 19:40
newRequestWriter.Write("Content-Type: application/octet-stream\r\n");
}
newRequestWriter.WriteLine(line);
newRequestWriter.Write($"{line}\r\n");
Copy link
Member

@trrwilson trrwilson Nov 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it the case that Write is AOT-compatible and WriteLine isn't? That's so strange!!

I'd normally suggest that we should use Environment.NewLine instead of an explicit \r\n, but I have a sneaking suspicion that Environment.Newline resolution might be exactly why WriteLine doesn't work -- is that the case? newRequestWriter.Write(line).Write(Environment.NewLine) is "cleaner," but not if reproduces the same break!

Functionally, as long as this still works across platforms (which should be caught by SDK tests), I have no issue with the explicit \r\n there.

@nick863 nick863 force-pushed the nirovins/fix_unit_tests branch from 0f19b1e to e5b55d6 Compare November 4, 2025 17:52

<!-- TEMP: Overrides until central packages bumped, needed for new extensions -->
<PackageReference Include="Microsoft.Bcl.AsyncInterfaces" VersionOverride="8.0.0" />
<PackageReference Include="Microsoft.Bcl.AsyncInterfaces" VersionOverride="9.0.9" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ArthurMa1978 / @ArcturusZhang: We're not going to address it in this PR, but we should NOT be doing version overrides like this. Most of these are behind the central versions at this point. Please follow-up and remove these.

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.

4 participants