// code should be unreachable with correctly implemented Futures.
      // Cancel this future and return.
      // At this point, inputFuture is cancelled and outputFuture doesn't exist, so the value of
      // mayInterruptIfRunning is irrelevant.
      cancel(false);
      return;
    } catch (ExecutionException e) {
      // Set the cause of the exception as this future's exception.

        return new CopyOptions().exclude(propertyNames);
    }

    /**
     * Returns a {@link CopyOptions} that excludes properties with {@literal null} values from the operation.
     *
     * @return A {@link CopyOptions} that excludes properties with {@literal null} values from the operation.
     * @see CopyOptions#excludeNull()
     */
    public static CopyOptions excludeNull() {
        return new CopyOptions().excludeNull();

- The kubectl --dry-run flag now accepts the values 'client', 'server', and 'none', to support client-side and server-side dry-run strategies. The boolean and unset values for the --dry-run flag are deprecated and a value will be required in a future version. ([#87580](https://github.com/kubernetes/kubernetes/pull/87580), [@julianvmodesto](https://github.com/julianvmodesto)) [SIG CLI]...

 * </p>
 * <p>
 * If the source object is a {@link Date}, {@link Calendar}, or {@link java.sql.Date}, the converted object is created using the millisecond value of the source.
 * For other types, the converted object is created from the string representation of the source object.
 * </p>
 * <p>

            assertArrayEquals(expectedName, actualName);
            verify(request, times(1)).getName();
        }

        @Test
        @DisplayName("getName() should handle null return value")
        void testGetNameWithNull() {
            CreateContextRequest request = mock(CreateContextRequest.class);
            when(request.getName()).thenReturn(null);

            byte[] actualName = request.getName();

- The `TerminationGracePeriodSeconds` on pod specs and container probes should not be negative. Negative values of `TerminationGracePeriodSeconds` will be treated as the value `1s` on the delete path. Immutable field validation will be relaxed in order to update negative values. In a future release, negative values will not be permitted. ([#98866](https://github.com/kubernetes/kubernetes/pull/98866), [@wzshiming](https://github.com/wzshiming))

        assertEquals(((netdfs.DfsEnumArray1) info.e).s[0].entry_path, ((netdfs.DfsEnumArray1) decodedEnumEx.info.e).s[0].entry_path);
        assertEquals(totalentries.value, decodedEnumEx.totalentries.value);
    }

    @Test
    void testNetrDfsEnumEx_EncodeInDecodeOut_NullInfoAndTotalEntries() throws NdrException {
        String dfsName = "test_dfs_nulls";
        int level = 1;

The first change is that now we are declaring the OAuth2 security scheme with two available scopes, `me` and `items`.

The `scopes` parameter receives a `dict` with each scope as a key and the description as the value:

{* ../../docs_src/security/tutorial005_an_py310.py hl[63:66] *}

Because we are now declaring those scopes, they will show up in the API docs when you log-in/authorize.

    "id": 4,
    "name": "Mary",
    "joined": "2018-11-30",
}

my_second_user: User = User(**second_user_data)
```


/// info

`**second_user_data` 意思是:

將 `second_user_data` 字典直接作為 key-value 引數傳遞，等同於：`User(id=4, name="Mary", joined="2018-11-30")`

///

### 多種編輯器支援

整個框架的設計是為了讓使用變得簡單且直觀，在開始開發之前，所有決策都在多個編輯器上進行了測試，以確保提供最佳的開發體驗。

						<ant antfile="${basedir}/module.xml" target="install.modules">
							<property name="with.fess" value="true" />
							<property name="opensearch.version" value="${opensearch.version}" />
						</ant>
						<ant antfile="${basedir}/plugin.xml" target="install.plugins">
							<property name="with.fess" value="true" />
						</ant>
						<ant antfile="deps.xml" target="install.jars" />