if: github.event_name == 'schedule' || (github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v2')) # only if it is a scheduled nightly or tagged
        shell: bash

## Type annotation vs `Depends` { #type-annotation-vs-depends }

Notice how we write `CommonQueryParams` twice in the above code:

//// tab | Python 3.8+

```Python
commons: Annotated[CommonQueryParams, Depends(CommonQueryParams)]
```

////

//// tab | Python 3.8+ non-Annotated

/// tip

        // Act: call twice
        try (SmbTreeHandleImpl t1 = target.ensureTreeConnected(); SmbTreeHandleImpl t2 = target.ensureTreeConnected()) {
            assertSame(tree, t1);
            assertSame(tree, t2);
        }

        // Assert: pipe.ensureTreeConnected invoked once, acquire twice
        verify(pipe, times(1)).ensureTreeConnected();

			Owner:     "owner",
			Quorum:    &quorum,
		}
		ok, err := l.RLock(ctx, arg)
		if err != nil {
			t.Fatal(err)
		}
		if !ok {
			t.Fatal("did not get read lock")
		}
		// RLock twice
		ok, err = l.RLock(ctx, arg)
		if err != nil {
			t.Fatal(err)
		}
		if !ok {
			t.Fatal("did not get write lock")
		}

		rResources[i] = arg.Resources[0]
	}

        // Act
        assertTrue(itr.hasNext());
        SmbResource r = itr.next();

        // Assert: filter was invoked twice and we got the accepted one
        ArgumentCaptor<SmbResource> captor = ArgumentCaptor.forClass(SmbResource.class);
        verify(filter, times(2)).accept(captor.capture());
        assertNotNull(r);

        // Act: call methods, some multiple times
        String name = mockEntry.getName();
        int type1 = mockEntry.getType();
        int type2 = mockEntry.getType(); // called twice for interaction verification
        int attributes = mockEntry.getAttributes();
        long createTime = mockEntry.createTime();
        long lastModified = mockEntry.lastModified();

            System.clearProperty(Constants.FESS_CONFIG_PREFIX + testKey);
        }
    }

    // Test caching mechanism
    public void test_get_caching() {
        // Get property twice to test caching behavior
        String testKey = "domain.title";
        String value1 = fessConfig.get(testKey);
        String value2 = fessConfig.get(testKey);

        // Values should be the same

        JobNotFoundException exception = new JobNotFoundException(message);

        assertEquals(message, exception.getMessage());
        assertEquals(message, exception.getMessage()); // Call twice to verify consistency
        assertEquals(message, exception.getLocalizedMessage());
    }

    public void test_toString() {
        // Test toString method
        String message = "Test exception message";

on 16 drive MinIO deployment. If you use eight data and eight parity drives, the file space usage will be approximately twice, i.e. 100 MiB
file will take 200 MiB space. But, if you use ten data and six parity drives, same 100 MiB file takes around 160 MiB. If you use 14 data and
two parity drives, 100 MiB file takes only approximately 114 MiB.

        assertArrayEquals(new byte[] { 10, 20, 30, 40, 50 }, buffer);
        // Note: There appears to be a bug in the implementation where readFully
        // incorrectly updates the file pointer twice
        assertEquals(10, smbRandomAccessFile.getFilePointer());
    }