[Snyk] Upgrade @types/express from 4.17.7 to 4.17.13 #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade @types/express from 4.17.7 to 4.17.13. See this package in npm: https://www.npmjs.com/package/@types/express See this project in Snyk: https://app.snyk.io/org/maxmood96/project/45f16614-ea95-4982-af72-d21cb64ab6aa?utm_source=github&utm_medium=upgrade-pr
pull bot
pushed a commit
that referenced
this pull request
Jul 9, 2025
Not all PDFs come from content:// URIs. A FileDescriptor based API unblocks apps that download PDFs from web services or load PDFs from Files in their private storage from using the libary. Drive is such an app. This API still accepts a URI: 1) As a unique identifier. Bound services produce unique IBinders for unique Intents. It's critical we have some way to provide a unique Intent per document, and setting the data field is a good way to accomplish this. 2) PdfDocument exposes Uri in its API. This is potentially worth reconsidering, but it's not terrible to keep in place given #1. Relnote: Adds FileDescriptor API to PdfLoader Test: ./gradlew :pdf:pdf-document-service:cAT Change-Id: I60b8dfa37b4c3800392f2d14992375b9d2581f05
pull bot
pushed a commit
that referenced
this pull request
Jul 10, 2025
This CL adds native multi-window support to the uiautomator library primarily for enhancing large screen and desktop experience. It provides new APIs to improve window searchability and testability. Design: go/uiautomator-window-design Bug: 425372420 Test: ./gradlew :test:uiautomator:i:t:connectedAndroidTest (UiWindowTest on phone, tablet and desktop) Relnote: New APIs for desktop multi-window (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:951748bb9f202b98998a9b3e6f002a694cef3a62) Merged-In: I359c4b3c36b1c20af4c50ccc3d2e7dbfeb0cd15b Change-Id: I359c4b3c36b1c20af4c50ccc3d2e7dbfeb0cd15b
pull bot
pushed a commit
that referenced
this pull request
Sep 19, 2025
Deciding TalkBack whether it should intercept RSB movtion events to navigate a11y focus is based on the input focus. If the scrollable node fail to acquire input focus, TalkBack would treat it that RSB motion events could be used by the input focused node and then it doesn't intercept RSB movetion events. Therefore, if we want to navigate a11y focus by RSB, we need to request input focus to the scrollable node which has CollectionInfo. Node #1 at (l=0.0, t=0.0, r=119.0, b=456.0)px |-Node #2 at (l=0.0, t=0.0, r=119.0, b=456.0)px, Tag: 'scalingLazyColumn' |-Node #4 at (l=0.0, t=-22.0, r=119.0, b=478.0)px CollectionInfo = 'androidx.compose.ui.semantics.CollectionInfo@8d7827' Focused = 'true' ... Bug: b/445332360 Test: Run wear.compose.integration-tests.demos Change-Id: I6be3cd527a60eb95679889e4c86e8240530894b0
pull bot
pushed a commit
that referenced
this pull request
Jan 31, 2026
Fixed the issue where the accumulated scroll was erased because measure passes were triggered due to internal state tracking (bypassing the 'onScroll' method). **Details:** The fundamental cause of this bug is similar to b/452857486, though their effects differ: this bug results in the loss of accumulated scroll (leading to inaccurate scrolling during animations), while the other concerns performance. However, the root cause in both cases is the same: the 'List' tracks the 'pinnedIndex' state, which triggers extra recompositions. Here is a step-by-step explanation of the scenario: 1. During measure pass #1 some scroll distance is consumed (95 pixels), and some is accumulated for the next passes (let's assume 5 pixels). 2. A new item becomes focused. 3. The focused node automatically attempts to pin itself. 4. Pinning changes the 'pinnedIndex' state, which is tracked within the measure scope. 5. This change causes a recomposition with 0 input scroll. The final calculation results in: ``` applyMeasureResult( result = measureResult, consumedScroll = 0f, accumulatedScorll = 0f, // This overrides the previous value of 5 pixels! ) ``` Consequently, the 5 pixels are lost and overwritten with 0. This means that the list is scrolled by only 95 pixels instead of the requested 100, and those 5 pixels are never compensated. While this loss is not noticeable during manual user scrolling, it can cause issues when developers run precise animations (e.g., animateToIndex() or fling snap animation). Fix: 476377084 Test: Added new test cases, ran old tests. Change-Id: Ibb24ce6877d9df64fe12eaed107237ee8eb75acf
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade @types/express from 4.17.7 to 4.17.13.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: @types/express
-
4.17.13 - 2021-07-06
-
4.17.12 - 2021-05-25
-
4.17.11 - 2021-01-12
-
4.17.10 - 2021-01-11
-
4.17.9 - 2020-11-11
-
4.17.8 - 2020-09-01
-
4.17.7 - 2020-07-06
from @types/express GitHub release notesNote: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs