assertTrue(str.contains(Constants.RUNNING));
    }

    private ScheduledJob createTestScheduledJob() {
        final ScheduledJob scheduledJob = new ScheduledJob();
        scheduledJob.setName("Test Job");
        scheduledJob.setScriptType("groovy");
        scheduledJob.setScriptData("println 'hello'");
        scheduledJob.setJobLogging(Constants.T);
        scheduledJob.setAvailable(Constants.T);

     * most common. This is the state information that would be retrieved from
     * WINS for example. Natrually it is not practical for every NbtAddress
     * to be populated will all state requiring a Node Status on every host
     * encountered. The below methods allow state to be populated when requested
     * in a lazy fashon.
     */

    void checkData() throws UnknownHostException {

                        "No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept."),
                Arguments.of(WinError.ERROR_BAD_PIPE, "The pipe state is invalid."),
                Arguments.of(WinError.ERROR_PIPE_BUSY, "All pipe instances are busy."),
                Arguments.of(WinError.ERROR_NO_DATA, "The pipe is being closed."),

 *
 *  * **Canceled:** the web socket connection failed. Messages that were successfully enqueued by
 *    either peer may not have been transmitted to the other.
 *
 * Note that the state progression is independent for each peer. Arriving at a gracefully-closed
 * state indicates that a peer has sent all of its outgoing messages and received all of its
 * incoming messages. But it does not guarantee that the other peer will successfully receive all of

            handshake();
        } catch (final IOException ex) {}
        return connection.getExpiration();
    }

    @Override
    public long getDate() {
        try {
            handshake();
        } catch (final IOException ex) {}
        return connection.getDate();
    }

    @Override
    public long getLastModified() {
        try {
            handshake();
        } catch (final IOException ex) {}

     */
    Class<T> getType();

    /**
     * Creates a copy of the data suitable for storage in the cache. The original data to store can be mutated after the
     * cache is populated but the state of the cache must not change so we need to make a copy.
     *
     * @param data The data to store in the cache, must not be {@code null}.
     * @return The data being stored in the cache, never {@code null}.
     */

            assertDoesNotThrow(() -> response.prepare(mockRequest));
        }
    }

    @Nested
    @DisplayName("State Management Tests")
    class StateManagementTests {

        @Test
        @DisplayName("Should reset state correctly")
        void testReset() {
            // Set initial state
            response.received();
            assertTrue(response.isReceived());

            // Reset

 *   <li>Manage repository configurations</li>
 *   <li>Handle project forking states</li>
 * </ul>
 *
 * The service maintains the mutable state of projects as they progress through
 * their build lifecycle, ensuring thread-safety and proper state management.
 * All implementations must be thread-safe as they may be accessed concurrently
 * during parallel builds.
 *
 * @since 4.0.0

    @Deprecated
    @Override
    public MavenMetadata setFile(File file) {
        return new VersionsMetadata(artifact, file.toPath(), timestamp);
    }

    @Override
    public MavenMetadata setPath(Path path) {
        return new VersionsMetadata(artifact, path, timestamp);
    }

    @Override
    public String getGroupId() {
        return artifact.getGroupId();
    }

    @Override

 *   <li>It is easy for the user to ensure that listeners are never invoked while holding locks.
 * </ul>
 *
 * The last point is subtle. Often the observable object will be managing its own internal state
 * using a lock, however it is dangerous to dispatch listeners while holding a lock because they
 * might run on the {@code directExecutor()} or be otherwise re-entrant (call back into your