-
Notifications
You must be signed in to change notification settings - Fork 45
Cherry-pick in-memory cache implementation for release 23.1.1 Fixes AB#3444129 #2822
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
Cherry-pick in-memory cache implementation for release 23.1.1 Fixes AB#3444129 #2822
Conversation
…3.1.1 Co-authored-by: siddhijain <[email protected]>
|
✅ Work item link check complete. Description contains link AB#3417272 to an Azure Boards work item. |
Co-authored-by: siddhijain <[email protected]>
Updated version number and removed duplicate entry.
|
❌ Invalid work item number: AB#3417272,. Work item number must be a valid integer. Click here to learn more. |
|
❌ Invalid work item number: AB#3444129 Cherry-picks. Work item number must be a valid integer. Click here to learn more. |
|
❌ Invalid work item number: AB#3444129 Cherry-picks. Work item number must be a valid integer. Click here to learn more. |
mohitc1
left a comment
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.
![]()
|
✅ Work item link check complete. Description contains link AB#3444129 to an Azure Boards work item. |
Fixes AB#3444129
Cherry-picks two commits from dev to enable in-memory caching for accounts and credentials in the broker.
Commits
Changes
Core Implementation (
BrokerOAuth2TokenCache.java)ConcurrentHashMapto share in-memory cache instances acrossBrokerOAuth2TokenCacheinstancesFeature Flag (
CommonFlight.java)USE_IN_MEMORY_CACHE_FOR_ACCOUNTS_AND_CREDENTIALS(default: false)Telemetry (
AttributeName.java)in_memory_cache_used_for_accounts_and_credentialsattributeTests
BrokerOAuth2TokenCacheWithInMemoryCacheTest.java(1240 lines)BrokerOAuth2TokenCacheTest.javawith cache sharing testsConflicts Resolved
changelog.txthad conflicts due to version markers in the release branch. Resolved by adding entries under vNext:Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
dl.google.com/usr/lib/jvm/temurin-17-jdk-amd64/bin/java /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-opens=java.base/java.nio.charset=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED --add-opens=java.xml/javax.xml.namespace=ALL-UNNAMED -XX:MaxMetaspaceSize=1024m -XX:+HeapDumpOnOutOfMemoryError -Xmx3072m -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant(dns block)www.puppycrawl.com/opt/hostedtoolcache/CodeQL/2.23.3/x64/codeql/tools/linux64/java/bin/java /opt/hostedtoolcache/CodeQL/2.23.3/x64/codeql/tools/linux64/java/bin/java -jar /opt/hostedtoolcache/CodeQL/2.23.3/x64/codeql/xml/tools/xml-extractor.jar --fileList=/home/REDACTED/work/microsoft-authentication-library-common-for-android/.codeql-scratch/dbs/java/working/files-to-index2294403091429273239.list --sourceArchiveDir=/home/REDACTED/work/microsoft-authentication-library-common-for-android/.codeql-scratch/dbs/java/src --outputDir=/home/REDACTED/work/microsoft-authentication-library-common-for-android/.codeql-scratch/dbs/java/trap/java(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
This pull request was created as a result of the following prompt from Copilot chat.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.