import org.jspecify.annotations.NullUnmarked;

/**
 * @author Kevin Bourrillion
 */
@GwtCompatible
@NullUnmarked
public class ImmutableDoubleArrayTest extends TestCase {
  // Test all creation paths very lazily: by assuming asList() works

  public void testOf0() {
    assertThat(ImmutableDoubleArray.of().asList()).isEmpty();
  }

  public void testOf1() {

   * </ul>
   *
   * <p>Note: The special implementation does not respect calls to {@link Throwable#setStackTrace
   * throwable.setStackTrace}. Instead, it always reflects the original stack trace from the
   * exception's creation.
   *
   * @since 19.0
   * @deprecated This method is equivalent to {@link Throwable#getStackTrace()} on JDK versions past
   *     JDK 8 and on all Android versions. Use {@link Throwable#getStackTrace()} directly, or where

            SMBUtil.writeInt2(SMB2_CLOSE_FLAG_POSTQUERY_ATTIB, buffer, bufferIndex + 2);
            // Reserved (4 bytes)
            SMBUtil.writeInt4(0, buffer, bufferIndex + 4);
            // Creation Time (8 bytes)
            long creationTime = System.currentTimeMillis() * 10000L + 116444736000000000L;
            SMBUtil.writeInt8(creationTime, buffer, bufferIndex + 8);
            // Last Access Time (8 bytes)

                Thread t = new Thread(r, "SecureKeyManager-Rotation");
                t.setDaemon(true);
                return t;
            });
    private java.util.concurrent.ScheduledFuture<?> rotationTask;

    /**
     * Configure key rotation interval
     *
     * @param intervalMillis rotation interval in milliseconds
     */
    public void configureKeyRotation(long intervalMillis) {

To create the packaging for a plugin a special Maven packaging would be created with an accompanying life-cycle in order to create the plugin metadata required and create an archive of the plugin that can be consumed at runtime.

h3. Creation of an isolated classloader

                            logger.info("Cleaned up stale operation: operation={}, previousOwner={}", operationName, ownerInstanceId);
                        }
                        // Retry creation
                        return tryStartOperation(operationName, data, remainingRetries - 1);
                    }
                }
            }
        } catch (final Exception e) {

Así que usamos un import relativo con `..` para las dependencias:

{* ../../docs_src/bigger_applications/app_an_py310/routers/items.py hl[3] title["app/routers/items.py"] *}

#### Cómo funcionan los imports relativos { #how-relative-imports-work }

/// tip | Consejo

- Fixed a bug in the TopologyManager. Previously, the TopologyManager would only guarantee alignment if container creation was serialized in some way. Alignment is now guaranteed under all scenarios of container creation. ([#87759](https://github.com/kubernetes/kubernetes/pull/87759), [@klueska](https://github.com/klueska)) [SIG Node]

我們需要從模組 `app.dependencies`（檔案 `app/dependencies.py`）取得相依性函式。

因此我們用 `..` 做相對匯入相依性：

{* ../../docs_src/bigger_applications/app_an_py310/routers/items.py hl[3] title["app/routers/items.py"] *}

#### 相對匯入如何運作 { #how-relative-imports-work }

/// tip | 提示

如果你對匯入的運作方式十分了解，可以直接跳到下一節。

///

單一的點號 `.`，如下：

```Python
from .dependencies import get_token_header
```

代表：

 *
 * <p><b>Key-grouped iteration.</b> All view collections follow the same iteration order. In all
 * current implementations, the iteration order always keeps multiple entries with the same key
 * together. Any creation method that would customarily respect insertion order (such as {@link
 * #copyOf(Multimap)}) instead preserves key-grouped order by inserting entries for an existing key
 * immediately after the last entry having that key.
 *