-
Notifications
You must be signed in to change notification settings - Fork 503
Remove RequiresPreviewFeatures attribute for Lambda Response Streaming #2467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Changes from all commits
1b4d82a
92d4f08
df49879
93e49ad
093441b
cb305ec
d06e5f5
5a130d3
66be05c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,50 @@ | ||
| { | ||
| "Projects": [ | ||
| { | ||
| "Name": "Amazon.Lambda.Core", | ||
| "Type": "Minor", | ||
| "ChangelogMessages": [ | ||
| "Lambda response streaming is now available as GA. The RequiresPreviewFeatures attribute has been removed", | ||
| "The LambdaLogger.ConfigureStructuredLogging API has been deployed to the managed runtime. The RequiresPreviewFeatures attribute has been removed" | ||
| ] | ||
| }, | ||
| { | ||
| "Name": "Amazon.Lambda.Annotations", | ||
| "Type": "Minor", | ||
| "ChangelogMessages": [ | ||
| "Updated Amazon.Lambda.Core dependency to include Lambda Response Streaming support." | ||
| ] | ||
| }, | ||
| { | ||
| "Name": "Amazon.Lambda.AspNetCoreServer", | ||
| "Type": "Minor", | ||
| "ChangelogMessages": [ | ||
| "Removed RequiresPreviewFeatures attribute for Lambda Response Streaming.", | ||
| "Updated Amazon.Lambda.Core dependency to include Lambda Response Streaming support.", | ||
| "Updated the base class AbstractAspNetCoreFunction to implement IDisposable. This is mostly needed for unit tests. In the Lambda environment there will only be one instance of AbstractAspNetCoreFunction subclass created." | ||
| ] | ||
| }, | ||
| { | ||
| "Name": "Amazon.Lambda.AspNetCoreServer.Hosting", | ||
| "Type": "Minor", | ||
| "ChangelogMessages": [ | ||
| "Removed RequiresPreviewFeatures attribute for Lambda Response Streaming.", | ||
| "Updated Amazon.Lambda.Core dependency to include Lambda Response Streaming support." | ||
| ] | ||
| }, | ||
| { | ||
| "Name": "Amazon.Lambda.PowerShellHost", | ||
| "Type": "Minor", | ||
| "ChangelogMessages": [ | ||
| "Updated Amazon.Lambda.Core dependency to include Lambda Response Streaming support." | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. are you missing some csproj updates or somthing somewhere?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The csproj files have the project reference to Amazon.Lambda.Core. So when we do the release the project reference will cause the dependency version for the generated nuspec file to have the new version of Amazon.Lambda.Core. So there is nothing to change in the csproj file. If it was a package reference then you would see a csrpoj change. |
||
| ] | ||
| }, | ||
| { | ||
| "Name": "Amazon.Lambda.RuntimeSupport", | ||
| "Type": "Minor", | ||
| "ChangelogMessages": [ | ||
| "Updated Amazon.Lambda.Core dependency to include Lambda Response Streaming support." | ||
| ] | ||
| } | ||
| ] | ||
| } | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| <?xml version="1.0" encoding="utf-8"?> | ||
| <RunSettings> | ||
| <RunConfiguration> | ||
| <!-- | ||
| Force ASP.NET Core / Microsoft.Extensions configuration to use a polling file watcher instead of | ||
| the OS file-system watcher. On Linux the OS watcher is backed by inotify, and each host built via | ||
| Host.CreateDefaultBuilder / WebApplication registers several reloadOnChange watchers on appsettings*.json. | ||
| These tests construct many ASP.NET Core hosts and xUnit runs test classes in parallel; when this assembly | ||
| runs alongside Amazon.Lambda.AspNetCoreServer.Test in a single solution-wide test run, the concurrent number | ||
| of inotify instances exceeds the per-user limit (fs.inotify.max_user_instances, 128 by default on the CI | ||
| hosts), producing "The configured user limit (128) on the number of inotify instances has been reached". | ||
|
|
||
| The polling watcher uses a timer instead of inotify, so no inotify instances are consumed. VSTest sets | ||
| these variables before the test host process starts, so they take effect before any host is built. | ||
| --> | ||
| <EnvironmentVariables> | ||
| <DOTNET_USE_POLLING_FILE_WATCHER>1</DOTNET_USE_POLLING_FILE_WATCHER> | ||
| </EnvironmentVariables> | ||
| </RunConfiguration> | ||
| </RunSettings> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i dont see any annotation changes in this pr but i see it in the changefile?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The csproj files have the project reference to Amazon.Lambda.Core. So when we do the release the project reference will cause the dependency version for the generated nuspec file to have the new version of Amazon.Lambda.Core. So there is nothing to change in the csproj file. If it was a package reference then you would see a csrpoj change.