- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 196 for peeking (0.04 sec)
-
guava-tests/test/com/google/common/collect/PeekingIteratorTest.java
"next() should still return first element after peeking", "A", peekingIterator.next()); assertEquals("Should be able to peek() at middle element", "B", peekingIterator.peek()); assertEquals( "Should be able to peek() middle element multiple times", "B", peekingIterator.peek()); assertEquals( "next() should still return middle element after peeking", "B", peekingIterator.next());
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Thu Aug 07 16:05:33 UTC 2025 - 8.6K bytes - Viewed (0) -
src/main/java/jcifs/internal/smb1/trans/TransPeekNamedPipe.java
*/ package jcifs.internal.smb1.trans; import jcifs.Configuration; import jcifs.internal.util.SMBUtil; /** * SMB1 transaction subcommand for peeking at data in a named pipe. * * This class implements the TRANS_PEEK_NAMED_PIPE transaction which allows * reading data from a pipe without removing it, useful for checking if data
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 3K bytes - Viewed (0) -
android/guava/src/com/google/common/collect/Iterators.java
// covariantly (and cannot be subclassed to add non-covariant uses). @SuppressWarnings("unchecked") PeekingImpl<T> peeking = (PeekingImpl<T>) iterator; return peeking; } return new PeekingImpl<>(iterator); } /** * Simply returns its argument. * * @deprecated no need to use this * @since 10.0 */
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Thu Aug 07 16:05:33 UTC 2025 - 50.5K bytes - Viewed (0) -
src/main/java/jcifs/internal/smb1/trans/SmbComTransaction.java
/** * Network server enumeration subcommand version 3 */ public static final byte NET_SERVER_ENUM3 = (byte) 0xD7; /** * Transaction subcommand for peeking data from a named pipe */ public static final byte TRANS_PEEK_NAMED_PIPE = (byte) 0x23; /** * Transaction subcommand for waiting on a named pipe */
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 17.3K bytes - Viewed (0) -
CONTRIBUTING.md
Contributing ============ Keeping the project small and stable limits our ability to accept new contributors. We are not seeking new committers at this time, but some small contributions are welcome. If you've found a security problem, please follow our [bug bounty][security] program. If you've found a bug, please contribute a failing test case so we can study and fix it. If you have a new feature idea, please build it in an external library. There are
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Tue Feb 14 08:26:50 UTC 2023 - 2K bytes - Viewed (0) -
docs/contribute/contributing.md
Contributing ============ Keeping the project small and stable limits our ability to accept new contributors. We are not seeking new committers at this time, but some small contributions are welcome. If you've found a security problem, please follow our [bug bounty][security] program. If you've found a bug, please contribute a failing test case so we can study and fix it. If you have a new feature idea, please build it in an external library. There are
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Tue Feb 14 08:26:50 UTC 2023 - 2K bytes - Viewed (0) -
docs/bucket/replication/README.md
encrypted on the server side, will be replicated if destination also supports encryption. Replication status can be seen in the metadata on the source and destination objects. On the source side, the `X-Amz-Replication-Status` changes from `PENDING` to `COMPLETED` or `FAILED` after replication attempt either succeeded or failed respectively. On the destination side, a `X-Amz-Replication-Status` status of `REPLICA` indicates that the object was replicated successfully. Any replication failures...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 18.3K bytes - Viewed (0) -
cmd/bucket-replication-utils_test.go
rs: ReplicationState{ReplicationStatusInternal: "arn1=PENDING;", Targets: map[string]replication.StatusType{"arn1": "PENDING"}}, expStatus: replication.Pending, }, { // 3. replication status for one target - incorrect format name: "replication status for one target", rs: ReplicationState{ReplicationStatusInternal: "arn1=PENDING"}, expStatus: replication.StatusType(""), },
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Wed Apr 09 14:28:39 UTC 2025 - 9.3K bytes - Viewed (0) -
cmd/bucket-replication_test.go
// 1: Pending replication name: "existing object replication on object in Pending replication status", info: ObjectInfo{ Size: 100, ReplicationStatusInternal: "arn1:PENDING;", ReplicationStatus: replication.Pending, VersionID: "a3348c34-c352-4498-82f0-1098e8b34df9", },
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Wed Apr 09 14:28:39 UTC 2025 - 12.1K bytes - Viewed (0) -
ci/official/README.md
2. Running the CI scripts locally, as explained below 3. **Google employees only**: Google employees can use an internal-only tool called "MLCI" that makes testing more convenient: it can execute any full CI job against a pending change. Search for "MLCI" internally to find it. You may invoke a CI script of your choice by following these instructions: ```bash cd tensorflow-git-dir
Registered: Tue Sep 09 12:39:10 UTC 2025 - Last Modified: Thu Feb 01 03:21:19 UTC 2024 - 8K bytes - Viewed (0)