-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Dependency package lru-cache has a new version available #20363
Comments
ghost
added
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Feb 14, 2022
Label prediction was below confidence level |
ramya-rao-a
added
Client
This issue points to a problem in the data-plane of the library.
Schema Registry
labels
Feb 14, 2022
ghost
removed
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Feb 14, 2022
azure-sdk
removed
Client
This issue points to a problem in the data-plane of the library.
Schema Registry
labels
Feb 28, 2022
3 tasks
deyaaeldeen
added a commit
that referenced
this issue
Mar 9, 2022
### Packages impacted by this PR @azure/schema-registry-avro ### Issues associated with this PR Fixes #20245 Fixes #20363 Fixes #20565 ### Describe the problem that is addressed by this PR Logging cache size so customers understands how it grows in their application ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? The proposed approach logs the length of all stringified schemas which I believe is consistent with what .NET does. What else could we log here that we should consider? ### Are there test cases added in this PR? _(If not, why?)_ N/A ### Provide a list of related PRs _(if any)_ N/A ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ### Checklists - [x] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [ ] Added a changelog (if necessary)
WeiJun428
pushed a commit
to WeiJun428/azure-sdk-for-js
that referenced
this issue
Mar 20, 2022
### Packages impacted by this PR @azure/schema-registry-avro ### Issues associated with this PR Fixes Azure#20245 Fixes Azure#20363 Fixes Azure#20565 ### Describe the problem that is addressed by this PR Logging cache size so customers understands how it grows in their application ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? The proposed approach logs the length of all stringified schemas which I believe is consistent with what .NET does. What else could we log here that we should consider? ### Are there test cases added in this PR? _(If not, why?)_ N/A ### Provide a list of related PRs _(if any)_ N/A ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ### Checklists - [x] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [ ] Added a changelog (if necessary)
WeiJun428
pushed a commit
to WeiJun428/azure-sdk-for-js
that referenced
this issue
Mar 20, 2022
### Packages impacted by this PR @azure/schema-registry-avro ### Issues associated with this PR Fixes Azure#20245 Fixes Azure#20363 Fixes Azure#20565 ### Describe the problem that is addressed by this PR Logging cache size so customers understands how it grows in their application ### What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen? The proposed approach logs the length of all stringified schemas which I believe is consistent with what .NET does. What else could we log here that we should consider? ### Are there test cases added in this PR? _(If not, why?)_ N/A ### Provide a list of related PRs _(if any)_ N/A ### Command used to generate this PR:**_(Applicable only to SDK release request PRs)_ ### Checklists - [x] Added impacted package name to the issue description - [ ] Does this PR needs any fixes in the SDK Generator?** _(If so, create an Issue in the [Autorest/typescript](https://github.com/Azure/autorest.typescript) repository and link it here)_ - [ ] Added a changelog (if necessary)
azure-sdk
pushed a commit
to azure-sdk/azure-sdk-for-js
that referenced
this issue
Nov 14, 2022
Users/prjayasw/agrifoodrp (Azure#20363) * Adds base for updating Microsoft.AgFoodPlatform from version preview/2020-05-12-preview to version 2021-09-01-preview * Adds base for updating Microsoft.AgFoodPlatform from version preview/2020-05-12-preview to version 2021-09-01-preview * Updates readme * Updates API version in new specs and examples * Private endpoint changes * updated examples * updated db update example * build fixes * changed common-types version * pr comments * minor update * Removed 202 response code from Put call * update examples * prettier fix * enum example fix * Incremental change of sensor feature * Adding support for operationResults api for farmbeats resource. * Making cosmetic changes to fix checks * Update readme.python.md pin the title for python SDK * Fixing one change * Rsolving comments * Updating Extension Create api and removing extension update api * Removing ApiProperties from required list and adding Extension_CreateOrUpdate.json * Adding examples/Extensions_Delete.json and removing examples/Extensions_Update.json. Also, adding few small changes to Extension apis * Fixing a small typo * Fixing failing checks * Fixing example for extension create or update * Fixing prettier error Co-authored-by: Prabhav Gupta <[email protected]> Co-authored-by: Prabhav Gupta <[email protected]> Co-authored-by: Priyanka Jayaswal <[email protected]> Co-authored-by: Yuchao Yan <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have identified a dependency on version 6.0.0 of lru-cache. A new version (7.4.1) is available for upgrade.
Following are the steps to upgrade package dependency.
Understand the breaking changes between the version being used and the version you want to upgrade to.
Identify all packages that take a dependency on this package.
Go to the root folder for each such package (/sdk/service-name/package-name) and update package.json to have the new version.
Run rush update to ensure the new version is pulled in.
Make relevant changes to absorb the breaking changes.
Repeat steps 3 to 5 for each of the packages that have a dependency on this package.
The text was updated successfully, but these errors were encountered: