- Sort Score
- Result 10 results
- Languages All
Results 271 - 280 of 376 for reflow (0.03 sec)
-
docs/en/docs/tutorial/bigger-applications.md
{!../../docs_src/bigger_applications/app/routers/items.py!} ``` #### How relative imports work { #how-relative-imports-work } /// tip If you know perfectly how imports work, continue to the next section below. /// A single dot `.`, like in: ```Python from .dependencies import get_token_header ``` would mean:
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 19.1K bytes - Viewed (0) -
helm-releases/minio-3.0.1.tgz
"ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Thu Sep 02 01:47:43 UTC 2021 - 13.8K bytes - Viewed (0) -
helm-releases/minio-3.0.2.tgz
"ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Sep 03 08:11:32 UTC 2021 - 13.8K bytes - Viewed (0) -
helm-releases/minio-3.1.0.tgz
"ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Sun Sep 12 18:19:27 UTC 2021 - 14.3K bytes - Viewed (0) -
src/main/java/jcifs/smb1/netbios/NbtAddress.java
* issue on the host. There's not much we can do about it. Just * to suppress NPEs that would result we can create a possibly bogus * address. Pretty sure the below cannot actually thrown a UHE tho. */ try { localInetAddress = InetAddress.getByName("127.0.0.1"); } catch (final UnknownHostException ignored) {}
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sat Aug 16 01:32:48 UTC 2025 - 31.7K bytes - Viewed (0) -
src/test/java/jcifs/internal/smb2/info/Smb2SetInfoRequestTest.java
// This method should always return 0 as the request doesn't read responses assertEquals(0, bytesRead); } @Test @DisplayName("Test complete flow with all setters") void testCompleteFlow() { request = new Smb2SetInfoRequest(mockConfig); // Set all fields byte[] newFileId = new byte[16]; for (int i = 0; i < 16; i++) {
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Thu Aug 14 05:31:44 UTC 2025 - 13.9K bytes - Viewed (0) -
src/test/java/jcifs/http/NtlmHttpURLConnectionTest.java
assertDoesNotThrow(() -> spiedConnection.getInputStream()); } /** * Test a successful NTLM authentication handshake. * This is a simplified test that verifies the basic flow without full NTLM protocol simulation. * @throws IOException * @throws SecurityException */ @Test void testSuccessfulHandshake() throws IOException, SecurityException {
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Thu Aug 14 07:14:38 UTC 2025 - 12.6K bytes - Viewed (0) -
helm-releases/minio-1.0.0.tgz
"ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 20 22:30:54 UTC 2021 - 13.5K bytes - Viewed (0) -
helm-releases/minio-1.0.1.tgz
"ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 20 22:32:29 UTC 2021 - 13.5K bytes - Viewed (0) -
helm-releases/minio-1.0.3.tgz
"ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 24 19:04:07 UTC 2021 - 13.6K bytes - Viewed (0)