return "", gcsToObjectError(err, gcs.Bucket, key)
	}

	return "", w.Close()
}

// FIXME: add support for remote version ID in GCS remote tier and remove this.
// Currently it's a no-op.
func (gcs *warmBackendGCS) Put(ctx context.Context, key string, data io.Reader, length int64) (remoteVersionID, error) {
	return gcs.PutWithMeta(ctx, key, data, length, map[string]string{})
}

  // Following are helper functions to assist integrating TFRT with current
  // TF eager runtime.
  // TODO(b/172877902): These helper functions are currently used to support
  // PyFuncOp on TFRT, and might be useful for ops that directly use low
  // level TF APIs. Remove/replace the following functions when TFRT native
  // ops are implemented.

         * @return the directory file
         */
        public SmbFile getDirectoryFile() {
            return directoryFile;
        }

        /**
         * Checks if directory change monitoring is currently active
         * @return true if watching is active
         */
        public boolean isActive() {
            return active;
        }

        /**
         * Set active status
         *

	// Indicates if we are using default storage class and there was problem loading config
	// if this header is set to "true"
	MinIOStorageClassDefaults = "x-minio-storage-class-defaults"

	// Reports number of drives currently healing
	MinIOHealingDrives = "x-minio-healing-drives"

	// Header indicates if the delete marker should be preserved by client
	MinIOSourceDeleteMarker = "x-minio-source-deletemarker"

   * element (the given list itself).
   *
   * <p>This method is safe to use even when {@code elements} is a synchronized or concurrent
   * collection that is currently being modified by another thread.
   *
   * @throws NullPointerException if {@code elements} contains a null element
   */
  public static <E> ImmutableList<E> copyOf(Collection<? extends E> elements) {

### Model sharing

If the multitenant design allows sharing models, make sure that tenants and
users are aware of the security risks detailed here and that they are going to
be practically running code provided by other users. Currently there are no good
ways to detect malicious models/graphs/checkpoints, so the recommended way to
mitigate the risk in this scenario is to sandbox the model execution.

### Hardware attacks

     *
     * @return total released regions
     */
    public long getTotalReleased() {
        return totalReleased.get();
    }

    /**
     * Get number of currently active regions
     *
     * @return active regions (allocated - released)
     */
    public long getActiveRegions() {
        return totalAllocated.get() - totalReleased.get();
    }

    /**

                        classes.push('off', 'disabled');

                    //highlight the currently selected start date
                    if (calendar[row][col].format('YYYY-MM-DD') == this.startDate.format('YYYY-MM-DD'))
                        classes.push('active', 'start-date');

                    //highlight the currently selected end date

 * elements' text contents. When possible, avoid manual escaping by using templating systems and
 * high-level APIs that provide autoescaping. For example, consider <a
 * href="http://www.xom.nu/">XOM</a>.
 *
 * <p><b>Note:</b> Currently the escapers provided by this class do not escape any characters
 * outside the ASCII character range. Unlike HTML escaping the XML escapers will not escape

            // Test parent of a server
            assertEquals("smb1://", new SmbFile("smb1://server/").getParent());
            // Test parent of root - currently throws NPE due to bug in SmbFile.getParent()
            // when authority is null. This is a known issue in the legacy implementation.
            // For now, we expect the NPE to maintain backward compatibility