… a decorator to all Runnables executed on that executor.

PiperOrigin-RevId: 807916271

…. Triggers and logic are all the same as before, we're just doing everything through workflow files now to leverage caching.

PiperOrigin-RevId: 809159300

PiperOrigin-RevId: 809203260

…tLock.

This occurs because CallResourceReady only acquires 2/3 of the necessary locks to perform its runnable (SingleRequest.requestLock & EngineJob.this), and is missing the Engine.this lock.

In this change, I changed SingleRequest.requestLock to always be Engine.this.

Note that change only affects uses of SingleRequest built through RequestBuilder. Users of the public API SingleRequest.obtain are unaffected by this change.

If this fix works as intended, we can consider providing a new SingleRequest.obtain API with the requestLock param removed and deprecating the current SingleRequest.obtain.

PiperOrigin-RevId: 817821083

PiperOrigin-RevId: 818023760

…ttings.gradle` file in Kotlin DSL to kick off the process. Removed `git exec` command since we no longer have submodules.

PiperOrigin-RevId: 820305020

…rst time. Will be cleaning up the `apply` blocks once we move to Kotlin DSL.

PiperOrigin-RevId: 823192053

…. This will help with version management since everything is now in one place.

PiperOrigin-RevId: 823245115

PiperOrigin-RevId: 826616347

Robolectric's Util.readBytes is being removed.

PiperOrigin-RevId: 826666376

PiperOrigin-RevId: 829157965

When an app is moved to background, onTrimMemory() will be called, and LruBitmapPool/MemoryCache will be trimmed. However, the app could keep running and will new bitmaps will be retired to MemoryCache and LruBitmapPool. This change limits the sizes of LruBitmapPool/MemoryCache to zero when the app is in background, and restore the sizes to normal when it's moved out of background.

We introduce an experimental API `setMemoryCategoryInBackground(MemoryCategory)` for this purpose, as well as a new `MemoryCategory.ZERO` for no pooling/caching. App can use this API to set the MemoryCategory to limit the pool/cache size when the app is in background.

PiperOrigin-RevId: 852864309

PiperOrigin-RevId: 852944433

When an app is moved to background, onTrimMemory() will be called, and LruBitmapPool/MemoryCache will be trimmed. However, the app could keep running and will new bitmaps will be retired to MemoryCache and LruBitmapPool. This change limits the sizes of LruBitmapPool/MemoryCache to zero when the app is in background, and restore the sizes to normal when it's moved out of background.

We introduce an experimental API `setMemoryCategoryInBackground(MemoryCategory)` for this purpose, as well as a new `MemoryCategory.ZERO` for no pooling/caching. App can use this API to set the MemoryCategory to limit the pool/cache size when the app is in background.

PiperOrigin-RevId: 856285259

PiperOrigin-RevId: 872359811

… a state such as PROCESS_STATE_IMPORTANT_BACKGROUND, PROCESS_STATE_TRANSIENT_BACKGROUND, before the process goes to CACHED. And these are the some of the process states we don't want to apply the background MemoryCategory to.

This CL set the background memory category only when trim level is higher than TRIM_MEMORY_UI_HIDDEN.

PiperOrigin-RevId: 893789932

Motivation and Context
On Android R and above, Glide no longer appends the requireOriginal parameter when loading MediaStore URIs. Having the ACCESS_MEDIA_LOCATION permission does not always guarantee access to an unredacted file or location sharing. For example, unnecessarily adding requireOriginal to Android Photopicker URIs can cause apps to crash, as an UnsupportedOperationException may be thrown by the MediaProvider if the criteria to return an original unredacted file is not met by a PickerURI.

Furthermore, the previous approach of selectively ignoring Picker URIs from the requireOriginal appending caused an inconsistency in the expectations of Glide's clients. Clients could not reliably predict whether Glide would load the original or redacted file, as the behavior differed silently based on the specific type of URI being processed.

To provide a consistent and predictable API, the automatic appending behavior is removed entirely for Android R and above. If an app requires the original file, it should explicitly call and handle setRequireOriginal itself. (Note: The automatic appending behavior is preserved for Android Q to avoid regressions related to known OS bugs).

PiperOrigin-RevId: 895749372

Motivation and Context
Currently, isAndroidPickerUri only identifies URIs with an exact picker/ path segment. However, Android Photopicker URIs can also include variations such as picker_get_content/, picker_transcoded/, and modified versions with parameters like picker.location-true/.

PiperOrigin-RevId: 895768401

Bump ktx and compose versions to 1.0.0-beta09

In prep for 5.0.6.

Bumping gradle.properties and README.md