- Sort Score
- Result 10 results
- Languages All
Results 181 - 190 of 328 for Spec (0.42 sec)
-
src/cmd/api/main_test.go
} return true case *ast.GenDecl: if isDeprecated(n.Doc) { for _, spec := range n.Specs { switch spec := spec.(type) { case *ast.ValueSpec: for _, id := range spec.Names { mark(id) } case *ast.TypeSpec: mark(spec.Name) } } } return true // look at specs case *ast.FuncDecl:
Registered: Tue Dec 30 11:13:12 UTC 2025 - Last Modified: Thu Feb 20 03:25:33 UTC 2025 - 31.4K bytes - Viewed (0) -
src/main/webapp/WEB-INF/orig/view/login/newpassword.jsp
<%@page pageEncoding="UTF-8" contentType="text/html; charset=UTF-8"%><!DOCTYPE html> ${fe:html(true)} <head profile="http://a9.com/-/spec/opensearch/1.1/"> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <title><la:message key="labels.login.title" /></title> <link href="${fe:url('/css/admin/bootstrap.min.css')}" rel="stylesheet" type="text/css" />
Registered: Sat Dec 20 09:19:18 UTC 2025 - Last Modified: Sat Jan 18 12:09:07 UTC 2025 - 3.1K bytes - Viewed (0) -
docs/bucket/versioning/DESIGN.md
- ObjectType (default) - LegacyObjectType (preserves existing deployments and older xl.json format) - DeleteMarker (a versionId to capture the DELETE sequences implemented primarily for AWS spec compatibility) A sample msgpack-JSON `xl.meta`, you can debug the content inside `xl.meta` using [xl-meta.go](https://github.com/minio/minio/tree/master/docs/debugging#decoding-metadata) program. ```json {
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Jul 17 15:43:14 UTC 2022 - 5.8K bytes - Viewed (0) -
docs/es/docs/tutorial/request-forms.md
Por ejemplo, en una de las formas en las que se puede usar la especificación OAuth2 (llamada "password flow") se requiere enviar un `username` y `password` como campos de formulario. La <abbr title="specification – especificación">spec</abbr> requiere que los campos se llamen exactamente `username` y `password`, y que se envíen como campos de formulario, no JSON.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Tue Dec 16 16:33:45 UTC 2025 - 3.1K bytes - Viewed (0) -
docs/en/docs/tutorial/request-forms.md
For example, in one of the ways the OAuth2 specification can be used (called "password flow") it is required to send a `username` and `password` as form fields. The <abbr title="specification">spec</abbr> requires the fields to be exactly named `username` and `password`, and to be sent as form fields, not JSON.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 2.7K bytes - Viewed (0) -
docs/pt/docs/tutorial/request-forms.md
Por exemplo, em uma das maneiras que a especificação OAuth2 pode ser usada (chamada "fluxo de senha"), é necessário enviar um `username` e uma `password` como campos do formulário. A <abbr title="specification – especificação">spec</abbr> exige que os campos sejam exatamente nomeados como `username` e `password` e sejam enviados como campos de formulário, não JSON.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Nov 12 16:23:57 UTC 2025 - 3.1K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/connection/ConnectPlan.kt
val tlsEquipPlan = planWithCurrentOrInitialConnectionSpec(connectionSpecs, sslSocket) val connectionSpec = connectionSpecs[tlsEquipPlan.connectionSpecIndex] // Figure out the next connection spec in case we need a retry. retryTlsConnection = tlsEquipPlan.nextConnectionSpec(connectionSpecs, sslSocket) connectionSpec.apply(sslSocket, isFallback = tlsEquipPlan.isTlsFallback)Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Wed Oct 08 03:50:05 UTC 2025 - 19.3K bytes - Viewed (2) -
CHANGELOG/CHANGELOG-1.16.md
- `spec.scope` is no longer defaulted to `Namespaced` and must be explicitly specified - `spec.version` is removed in v1; use `spec.versions` instead - `spec.validation` is removed in v1; use `spec.versions[*].schema` instead - `spec.subresources` is removed in v1; use `spec.versions[*].subresources` instead - `spec.additionalPrinterColumns` is removed in v1; use `spec.versions[*].additionalPrinterColumns` instead
Registered: Fri Dec 26 09:05:12 UTC 2025 - Last Modified: Wed Oct 23 20:13:20 UTC 2024 - 345.2K bytes - Viewed (0) -
docs/de/docs/tutorial/request-forms.md
Zum Beispiel stellt eine der Möglichkeiten, die OAuth2-Spezifikation zu verwenden (genannt „password flow“), die Bedingung, einen `username` und ein `password` als Formularfelder zu senden. Die <abbr title="Specification – Spezifikation">Spec</abbr> erfordert, dass die Felder exakt `username` und `password` genannt werden und als Formularfelder, nicht JSON, gesendet werden.
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Sat Sep 20 15:10:09 UTC 2025 - 3.2K bytes - Viewed (0) -
android/guava-testlib/src/com/google/common/collect/testing/MinimalCollection.java
import org.jspecify.annotations.NonNull; import org.jspecify.annotations.NullMarked; import org.jspecify.annotations.Nullable; /** * A simplistic collection which implements only the bare minimum allowed by the spec, and throws * exceptions whenever it can. * * @author Kevin Bourrillion */ @GwtCompatible @NullMarked public class MinimalCollection<E extends @Nullable Object> extends AbstractCollection<E> {
Registered: Fri Dec 26 12:43:10 UTC 2025 - Last Modified: Sun Dec 22 03:38:46 UTC 2024 - 3.8K bytes - Viewed (0)