name: TensorFlow Lite in Play Services issue
about: Use this template for issues with TensorFlow Lite in Google Play Services
labels: 'comp:lite-in-play-services'

---

**System information**
- Android Device information (use `adb shell getprop ro.build.fingerprint`
  if possible):
- TensorFlow Lite in Play Services SDK version (found in `build.gradle`):
- Google Play Services version
  (`Settings` > `Apps` > `Google Play Services` > `App details`):

Introduce a "UI" architecture module to the core platform, and move the user interaction services to this new module.

This includes:

- Logging and progress services.
- Problem generation services (aka the "problems API").
- User prompting services.
- Build options infrastructure.
- The console and CLI, as a specific implementation of these services.

 * to the Maven build process.
 * <p>
 * SPI services are typically registered in {@code META-INF/services/} files corresponding to
 * the specific service interface being implemented.
 * <p>
 * All SPI services should be annotated with {@link Consumer} to indicate they are meant to be
 * implemented by plugins and extensions rather than used by them.
 *
 * @since 4.0.0
 */
@Experimental
@Consumer

import org.apache.maven.api.annotations.ThreadSafe;

/**
 * Marker interface for all services provided by the {@link Session}.
 * <p>
 * Services can be retrieved from the session using the
 * {@link Session#getService(Class)} method.
 *
 * @since 4.0.0
 * @see Session#getService(Class)
 */
@Experimental
@ThreadSafe

  mysql:
    strategy:
      matrix:
        dbversion: ['mysql:9', 'mysql:8', 'mysql:5.7']
        go: ['stable', 'oldstable']
        platform: [ubuntu-latest]
    runs-on: ${{ matrix.platform }}

    services:
      mysql:
        image: ${{ matrix.dbversion }}
        env:
          MYSQL_DATABASE: gorm
          MYSQL_USER: gorm
          MYSQL_PASSWORD: gorm
          MYSQL_RANDOM_ROOT_PASSWORD: "yes"

                String.format(
                    Locale.ROOT,
                    "Projects %s and %s both claim all services from %s. This is not supported because it"
                        + " breaks running in parallel. Configure specific services in docker-compose.yml "
                        + "for each and add the service name to `useFixture`",
                    otherProject.get(),
                    this.project.getPath(),

 * under the License.
 */

/**
 * Provides XML-specific services for reading and writing Maven's configuration files
 * and descriptors. These services handle XML parsing, transformation, and serialization
 * while maintaining Maven's model integrity.
 *
 * @since 4.0.0
 */

	// TargetStrip > 0 we strip the left most TargetStrip labels from the
	// DNS name.
	TargetStrip int `json:"targetstrip,omitempty"`

	// Group is used to group (or *not* to group) different services
	// together. Services with an identical Group are returned in
	// the same answer.
	Group string `json:"group,omitempty"`

	// Key carries the original key used during Put().
	Key string `json:"-"`

- Some base services that are available to code hosted by the runtime. This varies by runtime.
- Additional constraints. For example, the CLI client runtimes limit the libraries that are available to the code in that runtime, for performance reasons. 

Other modules and platforms define the services that they contribute to the runtime.

* There are 4 minio distributed instances created by default. You can add more MinIO services (up to total 16) to your MinIO Compose deployment. To add a service
  * Replicate a service definition and change the name of the new service appropriately.
  * Update the command section in each service.
  * Add a new MinIO server instance to the upstream directive in the Nginx configuration file.