Go to the source code of this file.
§ cbor_build_string()
Creates a new string and initializes it.
The val
will be copied to a newly allocated block
- Parameters
-
| val | A null-terminated UTF-8 string |
- Returns
- A new string with content
handle
. NULL
on malloc failure.
Definition at line 40 of file strings.c.
§ cbor_build_stringn()
| cbor_item_t* cbor_build_stringn |
( |
const char * |
val, |
|
|
size_t |
length |
|
) |
| |
Creates a new string and initializes it.
The handle
will be copied to a newly allocated block
- Parameters
-
| val | A UTF-8 string, at least length long (excluding the null byte) |
- Returns
- A new string with content
handle
. NULL
on malloc failure.
Definition at line 50 of file strings.c.
§ cbor_new_definite_string()
Creates a new definite string.
The handle is initialized to NULL
and length to 0
- Returns
- new definite string.
NULL
on malloc failure.
Definition at line 12 of file strings.c.
§ cbor_new_indefinite_string()
Creates a new indefinite string.
The chunks array is initialized to NULL
and chunkcount to 0
- Returns
- new indefinite string.
NULL
on malloc failure.
Definition at line 23 of file strings.c.
§ cbor_string_add_chunk()
Appends a chunk to the string.
Indefinite strings only.
May realloc the chunk storage.
- Parameters
-
| item[borrow] | An indefinite string |
| item[incref] | A definite string |
- Returns
- true on success. false on realloc failure. In that case, the refcount of
chunk
is not increased and the item
is left intact.
Definition at line 82 of file strings.c.
§ cbor_string_chunk_count()
| size_t cbor_string_chunk_count |
( |
const cbor_item_t * |
item | ) |
|
Get the number of chunks this string consist of.
- Parameters
-
| item[borrow] | A indefinite string |
- Returns
- The chunk count. 0 for freshly created items.
Definition at line 74 of file strings.c.
§ cbor_string_chunks_handle()
Get the handle to the array of chunks.
Manipulations with the memory block (e.g. sorting it) are allowed, but the validity and the number of chunks must be retained.
- Parameters
-
| item[borrow] | A indefinite string |
- Returns
- array of cbor_string_chunk_count definite strings
Definition at line 67 of file strings.c.
§ cbor_string_codepoint_count()
| size_t cbor_string_codepoint_count |
( |
const cbor_item_t * |
item | ) |
|
The number of codepoints in this string.
Might differ from length if there are multibyte ones
- Parameters
-
- Returns
- The number of codepoints in this string
Definition at line 118 of file strings.c.
§ cbor_string_handle()
Get the handle to the underlying string.
Definite items only. Modifying the data is allowed. In that case, the caller takes responsibility for the effect on items this item might be a part of
- Parameters
-
| item[borrow] | A definite string |
- Returns
- The address of the underlying string.
NULL
if no data have been assigned yet.
Definition at line 112 of file strings.c.
§ cbor_string_is_definite()
| bool cbor_string_is_definite |
( |
const cbor_item_t * |
item | ) |
|
Is the string definite?
- Parameters
-
- Returns
- Is the string definite?
Definition at line 124 of file strings.c.
§ cbor_string_is_indefinite()
| bool cbor_string_is_indefinite |
( |
const cbor_item_t * |
item | ) |
|
Is the string indefinite?
- Parameters
-
- Returns
- Is the string indefinite?
Definition at line 130 of file strings.c.
§ cbor_string_length()
Returns the length of the underlying string.
For definite strings only
- Parameters
-
| item[borrow] | a definite string |
- Returns
- length of the string. Zero if no chunk has been attached yet
Definition at line 106 of file strings.c.
§ cbor_string_set_handle()
Set the handle to the underlying string.
embed:rst:leading-asterisk
* .. warning:: Using a pointer to a stack allocated constant is a common mistake. Lifetime of the string will expire when it goes out of scope and the CBOR item will be left inconsistent.
*
- Parameters
-
| item[borrow] | A definite string |
| data | The memory block. The caller gives up the ownership of the block. libcbor will deallocate it when appropriate using its free function |
| length | Length of the data block |
Definition at line 59 of file strings.c.


crictl
Command-line for CRI-compatible container runtimes.
More information: home page
- List all kubernetes pods (Ready and NotReady):
crictl pods
- List all containers (Running and Exited):
crictl ps --all
- List all images:
crictl images
- Print information about specific containers:
crictl inspect container_id1 container_id2 ...
- Open a specific shell inside a running container:
crictl exec -it container_id sh
- Pull a specific image from a registry:
crictl pull image:tag
- Print and [f]ollow logs of a specific container:
crictl logs -f container_id
- Remove one or more images:
crictl rmi image_id1 image_id2 ...


---
layout: post
title: Perspective paths
date: '2017-02-19T05:00:25+01:00'
categories:
- Templates
picture_url: https://film-Storyboards.tumblr.com/post/157434994871/free-perspective-paths-for-adobe-photoshop-to
---
Free perspective paths for Adobe Photoshop to quickly build a 3 points perspective grid.
This will open as a blank file so make sure you are in Paths, not Layers. Move the perspective points in group or one by one with the Direct Selection Tool. Stroke the paths once you are happy with your settings. Use it in combination with Photoshop’s Vanishing Point filter to draw complex perspectives.


fetch_get_json
List of repositories in the GitHub mod-harbour organization:
Loading...
There was an error.


JQuery
It is built on top of
java script
Enables dragging and dropping
Enables Widget development.
Exciting plugins (auto-complete, slider etc)


Include function prototype for the UART console.
More...
#include <stdint.h>
Go to the source code of this file.
Include function prototype for the UART console.
§ DBG_Configure()
| void DBG_Configure |
( |
uint32_t |
baudrate, |
|
|
uint32_t |
masterClock |
|
) |
| |
Configures an USART peripheral with the specified parameters.
- Parameters
-
| baudrate | Baudrate at which the USART should operate (in Hz). |
| masterClock | Frequency of the system master clock (in Hz). |
§ DBG_DumpFrame()
| void DBG_DumpFrame |
( |
uint8_t * |
pucFrame, |
|
|
uint32_t |
dwSize |
|
) |
| |
Displays the content of the given frame on the UART0.
- Parameters
-
| pucFrame | Pointer to the frame to dump. |
| dwSize | Buffer size in bytes. |
§ DBG_DumpMemory()
| void DBG_DumpMemory |
( |
uint8_t * |
pucBuffer, |
|
|
uint32_t |
dwSize, |
|
|
uint32_t |
dwAddress |
|
) |
| |
Displays the content of the given buffer on the UART0.
- Parameters
-
| pucBuffer | Pointer to the buffer to dump. |
| dwSize | Buffer size in bytes. |
| dwAddress | Start address to display |
§ DBG_GetChar()
| uint32_t DBG_GetChar |
( |
void |
| ) |
|
Input a character from the UART line.
- Note
- This function is synchronous
- Returns
- character received.
§ DBG_GetHexa32()
| uint32_t DBG_GetHexa32 |
( |
uint32_t * |
pdwValue | ) |
|
Reads an hexadecimal number.
- Parameters
-
| pdwValue | Pointer to the uint32_t variable to contain the input value. |
§ DBG_GetInteger()
| uint32_t DBG_GetInteger |
( |
int32_t * |
pdwValue | ) |
|
Reads an integer.
- Parameters
-
| pdwValue | Pointer to a integer variable to contain the input value. |
- Returns
- success(1) or failure(0)
§ DBG_GetIntegerMinMax()
| uint32_t DBG_GetIntegerMinMax |
( |
int32_t * |
pdwValue, |
|
|
int32_t |
dwMin, |
|
|
int32_t |
dwMax |
|
) |
| |
Reads an integer and check the value.
- Parameters
-
| pdwValue | Pointer to a integer variable to contain the input value. |
| dwMin | Minimum value |
| dwMax | Maximum value |
- Returns
- success(1) or failure(0)
§ DBG_IsRxReady()
| uint32_t DBG_IsRxReady |
( |
void |
| ) |
|
Check if there is Input from UART line.
- Returns
- true if there is Input.
§ DBG_PutChar()
| void DBG_PutChar |
( |
uint8_t |
c | ) |
|
Outputs a character on the UART line.
- Note
- This function is synchronous (i.e. uses polling).
- Parameters
-


|
Xerces-C++
3.1.4
|
Default base class for SAX2 handlers. More...
Public Member Functions | |
| DefaultHandler () | |
| virtual | ~DefaultHandler () |
Default handlers for the DocumentHandler interface | |
| virtual void | characters (const XMLCh *const chars, const XMLSize_t length) |
| Receive notification of character data inside an element. More... | |
| virtual void | endDocument () |
| Receive notification of the end of the document. More... | |
| virtual void | endElement (const XMLCh *const uri, const XMLCh *const localname, const XMLCh *const qname) |
| Receive notification of the end of an element. More... | |
| virtual void | ignorableWhitespace (const XMLCh *const chars, const XMLSize_t length) |
| Receive notification of ignorable whitespace in element content. More... | |
| virtual void | processingInstruction (const XMLCh *const target, const XMLCh *const data) |
| Receive notification of a processing instruction. More... | |
| virtual void | resetDocument () |
| Reset the Document object on its reuse. More... | |
Default implementation of DocumentHandler interface | |
| virtual void | setDocumentLocator (const Locator *const locator) |
| Receive a Locator object for document events. More... | |
| virtual void | startDocument () |
| Receive notification of the beginning of the document. More... | |
| virtual void | startElement (const XMLCh *const uri, const XMLCh *const localname, const XMLCh *const qname, const Attributes &attrs) |
| Receive notification of the start of an element. More... | |
| virtual void | startPrefixMapping (const XMLCh *const prefix, const XMLCh *const uri) |
| Receive notification of the start of an namespace prefix mapping. More... | |
| virtual void | endPrefixMapping (const XMLCh *const prefix) |
| Receive notification of the end of an namespace prefix mapping. More... | |
| virtual void | skippedEntity (const XMLCh *const name) |
| Receive notification of a skipped entity. More... | |
Default implementation of the EntityResolver interface. | |
| virtual InputSource * | resolveEntity (const XMLCh *const publicId, const XMLCh *const systemId) |
| Resolve an external entity. More... | |
Default implementation of the ErrorHandler interface | |
| virtual void | error (const SAXParseException &exc) |
| Receive notification of a recoverable parser error. More... | |
| virtual void | fatalError (const SAXParseException &exc) |
| Report a fatal XML parsing error. More... | |
| virtual void | warning (const SAXParseException &exc) |
| Receive notification of a parser warning. More... | |
| virtual void | resetErrors () |
| Reset the Error handler object on its reuse. More... | |
Default implementation of DTDHandler interface. | |
| virtual void | notationDecl (const XMLCh *const name, const XMLCh *const publicId, const XMLCh *const systemId) |
| Receive notification of a notation declaration. More... | |
| virtual void | resetDocType () |
| Reset the DTD object on its reuse. More... | |
| virtual void | unparsedEntityDecl (const XMLCh *const name, const XMLCh *const publicId, const XMLCh *const systemId, const XMLCh *const notationName) |
| Receive notification of an unparsed entity declaration. More... | |
Default implementation of LexicalHandler interface. | |
| virtual void | comment (const XMLCh *const chars, const XMLSize_t length) |
| Receive notification of comments. More... | |
| virtual void | endCDATA () |
| Receive notification of the end of a CDATA section. More... | |
| virtual void | endDTD () |
| Receive notification of the end of the DTD declarations. More... | |
| virtual void | endEntity (const XMLCh *const name) |
| Receive notification of the end of an entity. More... | |
| virtual void | startCDATA () |
| Receive notification of the start of a CDATA section. More... | |
| virtual void | startDTD (const XMLCh *const name, const XMLCh *const publicId, const XMLCh *const systemId) |
| Receive notification of the start of the DTD declarations. More... | |
| virtual void | startEntity (const XMLCh *const name) |
| Receive notification of the start of an entity. More... | |
Default implementation of DeclHandler interface. | |
| virtual void | elementDecl (const XMLCh *const name, const XMLCh *const model) |
| Report an element type declaration. More... | |
| virtual void | attributeDecl (const XMLCh *const eName, const XMLCh *const aName, const XMLCh *const type, const XMLCh *const mode, const XMLCh *const value) |
| Report an attribute type declaration. More... | |
| virtual void | internalEntityDecl (const XMLCh *const name, const XMLCh *const value) |
| Report an internal entity declaration. More... | |
| virtual void | externalEntityDecl (const XMLCh *const name, const XMLCh *const publicId, const XMLCh *const systemId) |
| Report a parsed external entity declaration. More... | |
| Public Member Functions inherited from EntityResolver | |
| EntityResolver () | |
| Default Constructor. More... | |
| virtual | ~EntityResolver () |
| Destructor. More... | |
| Public Member Functions inherited from DTDHandler | |
| DTDHandler () | |
| Default Constructor. More... | |
| virtual | ~DTDHandler () |
| Destructor. More... | |
| Public Member Functions inherited from ContentHandler | |
| ContentHandler () | |
| Default constructor. More... | |
| virtual | ~ContentHandler () |
| Destructor. More... | |
| Public Member Functions inherited from ErrorHandler | |
| ErrorHandler () | |
| Default constructor. More... | |
| virtual | ~ErrorHandler () |
| Destructor. More... | |
| Public Member Functions inherited from LexicalHandler | |
| LexicalHandler () | |
| Default constructor. More... | |
| virtual | ~LexicalHandler () |
| Destructor. More... | |
| Public Member Functions inherited from DeclHandler | |
| DeclHandler () | |
| Default constructor. More... | |
| virtual | ~DeclHandler () |
| Destructor. More... | |
Default base class for SAX2 handlers.
This class implements the default behaviour for SAX2 interfaces: EntityResolver, DTDHandler, ContentHandler, ErrorHandler, LexicalHandler, and DeclHandler.
Application writers can extend this class when they need to implement only part of an interface; parser writers can instantiate this class to provide default handlers when the application has not supplied its own.
Note that the use of this class is optional.
| DefaultHandler::DefaultHandler | ( | ) |
|
virtual |
|
virtual |
Report an attribute type declaration.
Only the effective (first) declaration for an attribute will be reported.
| eName | The name of the associated element. |
| aName | The name of the attribute. |
| type | A string representing the attribute type. |
| mode | A string representing the attribute defaulting mode ("#IMPLIED", "#REQUIRED", or "#FIXED") or null if none of these applies. |
| value | A string representing the attribute's default value, or null if there is none. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements DeclHandler.
Receive notification of character data inside an element.
By default, do nothing. Application writers may override this method to take specific actions for each chunk of character data (such as adding the data to a node or buffer, or printing it to a file).
| chars | The characters. |
| length | The number of characters to use from the character array. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ContentHandler.
Receive notification of comments.
The Parser will call this method to report each occurrence of a comment in the XML document.
The application must not attempt to read from the array outside of the specified range.
| chars | The characters from the XML document. |
| length | The number of characters to read from the array. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements LexicalHandler.
Report an element type declaration.
The content model will consist of the string "EMPTY", the string "ANY", or a parenthesised group, optionally followed by an occurrence indicator. The model will be normalized so that all parameter entities are fully resolved and all whitespace is removed,and will include the enclosing parentheses. Other normalization (such as removing redundant parentheses or simplifying occurrence indicators) is at the discretion of the parser.
| name | The element type name. |
| model | The content model as a normalized string. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements DeclHandler.
|
virtual |
Receive notification of the end of a CDATA section.
The SAX parser will invoke this method at the end of each CDATA parsed.
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements LexicalHandler.
|
virtual |
Receive notification of the end of the document.
By default, do nothing. Application writers may override this method in a subclass to take specific actions at the beginning of a document (such as finalising a tree or closing an output file).
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ContentHandler.
|
virtual |
Receive notification of the end of the DTD declarations.
The SAX parser will invoke this method at the end of the DTD
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements LexicalHandler.
|
virtual |
Receive notification of the end of an element.
By default, do nothing. Application writers may override this method in a subclass to take specific actions at the end of each element (such as finalising a tree node or writing output to a file).
| uri | The URI of the associated namespace for this element |
| localname | The local part of the element name |
| qname | The QName of this element |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ContentHandler.
|
virtual |
Receive notification of the end of an entity.
The SAX parser will invoke this method at the end of an entity
| name | The name of the entity that is ending. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements LexicalHandler.
|
virtual |
Receive notification of the end of an namespace prefix mapping.
By default, do nothing. Application writers may override this method in a subclass to take specific actions at the end of each namespace prefix mapping.
| prefix | The namespace prefix used |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ContentHandler.
|
virtual |
Receive notification of a recoverable parser error.
The default implementation does nothing. Application writers may override this method in a subclass to take specific actions for each error, such as inserting the message in a log file or printing it to the console.
| exc | The warning information encoded as an exception. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ErrorHandler.
|
virtual |
Report a parsed external entity declaration.
Only the effective (first) declaration for each entity will be reported.
| name | The name of the entity. If it is a parameter entity, the name will begin with ''. |
| publicId | The The declared public identifier of the entity, or null if none was declared. |
| systemId | The declared system identifier of the entity. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements DeclHandler.
|
virtual |
Report a fatal XML parsing error.
The default implementation throws a SAXParseException. Application writers may override this method in a subclass if they need to take specific actions for each fatal error (such as collecting all of the errors into a single report): in any case, the application must stop all regular processing when this method is invoked, since the document is no longer reliable, and the parser may no longer report parsing events.
| exc | The error information encoded as an exception. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ErrorHandler.
|
virtual |
Receive notification of ignorable whitespace in element content.
By default, do nothing. Application writers may override this method to take specific actions for each chunk of ignorable whitespace (such as adding data to a node or buffer, or printing it to a file).
| chars | The whitespace characters. |
| length | The number of characters to use from the character array. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ContentHandler.
|
virtual |
Report an internal entity declaration.
Only the effective (first) declaration for each entity will be reported. All parameter entities in the value will be expanded, but general entities will not.
| name | The name of the entity. If it is a parameter entity, the name will begin with ''. |
| value | The replacement text of the entity. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements DeclHandler.
|
virtual |
Receive notification of a notation declaration.
By default, do nothing. Application writers may override this method in a subclass if they wish to keep track of the notations declared in a document.
| name | The notation name. |
| publicId | The notation public identifier, or null if not available. |
| systemId | The notation system identifier. |
Implements DTDHandler.
|
virtual |
Receive notification of a processing instruction.
By default, do nothing. Application writers may override this method in a subclass to take specific actions for each processing instruction, such as setting status variables or invoking other methods.
| target | The processing instruction target. |
| data | The processing instruction data, or null if none is supplied. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ContentHandler.
|
virtual |
|
virtual |
Reset the Document object on its reuse.
|
virtual |
Reset the Error handler object on its reuse.
Implements ErrorHandler.
|
virtual |
Resolve an external entity.
Always return null, so that the parser will use the system identifier provided in the XML document. This method implements the SAX default behaviour: application writers can override it in a subclass to do special translations such as catalog lookups or URI redirection.
| publicId | The public identifier, or null if none is available. |
| systemId | The system identifier provided in the XML document. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements EntityResolver.
|
virtual |
Receive a Locator object for document events.
By default, do nothing. Application writers may override this method in a subclass if they wish to store the locator for use with other document events.
| locator | A locator for all SAX document events. |
Implements ContentHandler.
|
virtual |
Receive notification of a skipped entity.
The parser will invoke this method once for each entity skipped. All processors may skip external entities, depending on the values of the features:
http://xml.org/sax/features/external-general-entities
http://xml.org/sax/features/external-parameter-entities
Introduced with SAX2
| name | The name of the skipped entity. If it is a parameter entity, the name will begin with %, and if it is the external DTD subset, it will be the string [dtd]. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ContentHandler.
|
virtual |
Receive notification of the start of a CDATA section.
The SAX parser will invoke this method at the start of each CDATA parsed.
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements LexicalHandler.
|
virtual |
Receive notification of the beginning of the document.
By default, do nothing. Application writers may override this method in a subclass to take specific actions at the beginning of a document (such as allocating the root node of a tree or creating an output file).
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ContentHandler.
|
virtual |
Receive notification of the start of the DTD declarations.
The SAX parser will invoke this method at the start of the DTD
| name | The document type name. |
| publicId | The declared public identifier for the external DTD subset, or null if none was declared. |
| systemId | The declared system identifier for the external DTD subset, or null if none was declared. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements LexicalHandler.
|
virtual |
Receive notification of the start of an element.
By default, do nothing. Application writers may override this method in a subclass to take specific actions at the start of each element (such as allocating a new tree node or writing output to a file).
| uri | The URI of the associated namespace for this element |
| localname | the local part of the element name |
| qname | the QName of this element |
| attrs | The specified or defaulted attributes. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ContentHandler.
|
virtual |
Receive notification of the start of an entity.
The SAX parser will invoke this method at the start of an entity
| name | The name of the entity that is starting. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements LexicalHandler.
|
virtual |
Receive notification of the start of an namespace prefix mapping.
By default, do nothing. Application writers may override this method in a subclass to take specific actions at the start of each namespace prefix mapping.
| prefix | The namespace prefix used |
| uri | The namespace URI used. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ContentHandler.
|
virtual |
Receive notification of an unparsed entity declaration.
By default, do nothing. Application writers may override this method in a subclass to keep track of the unparsed entities declared in a document.
| name | The entity name. |
| publicId | The entity public identifier, or null if not available. |
| systemId | The entity system identifier. |
| notationName | The name of the associated notation. |
Implements DTDHandler.
|
virtual |
Receive notification of a parser warning.
The default implementation does nothing. Application writers may override this method in a subclass to take specific actions for each warning, such as inserting the message in a log file or printing it to the console.
| exc | The warning information encoded as an exception. |
| SAXException | Any SAX exception, possibly wrapping another exception. |
Implements ErrorHandler.


API specification
Packages:
networking.x-k8s.io/v1alpha1
Package v1alpha1 contains API Schema definitions for the networking v1alpha1 API group
Resource Types:
Gateway
Gateway represents an instantiation of a service-traffic handling infrastructure by binding Listeners to a set of IP addresses.
| Field | Description | ||||||
|---|---|---|---|---|---|---|---|
apiVersion
string |
networking.x-k8s.io/v1alpha1
|
||||||
kind
string
|
Gateway |
||||||
metadata
Kubernetes meta/v1.ObjectMeta
|
Refer to the Kubernetes API documentation for the fields of the
metadata field.
|
||||||
spec
GatewaySpec
|
|
||||||
status
GatewayStatus
|
GatewayClass
GatewayClass describes a class of Gateways available to the user for creating Gateway resources.
GatewayClass is a Cluster level resource.
Support: Core.
| Field | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
apiVersion
string |
networking.x-k8s.io/v1alpha1
|
||||||||
kind
string
|
GatewayClass |
||||||||
metadata
Kubernetes meta/v1.ObjectMeta
|
Refer to the Kubernetes API documentation for the fields of the
metadata field.
|
||||||||
spec
GatewayClassSpec
|
Spec for this GatewayClass.
|
||||||||
status
GatewayClassStatus
|
Status of the GatewayClass. |
HTTPRoute
HTTPRoute is the Schema for the httproutes API
| Field | Description | ||
|---|---|---|---|
apiVersion
string |
networking.x-k8s.io/v1alpha1
|
||
kind
string
|
HTTPRoute |
||
metadata
Kubernetes meta/v1.ObjectMeta
|
Refer to the Kubernetes API documentation for the fields of the
metadata field.
|
||
spec
HTTPRouteSpec
|
|
||
status
HTTPRouteStatus
|
TCPRoute
TCPRoute is the Schema for the tcproutes API
| Field | Description | ||
|---|---|---|---|
apiVersion
string |
networking.x-k8s.io/v1alpha1
|
||
kind
string
|
TCPRoute |
||
metadata
Kubernetes meta/v1.ObjectMeta
|
Refer to the Kubernetes API documentation for the fields of the
metadata field.
|
||
spec
TCPRouteSpec
|
|
||
status
TCPRouteStatus
|
AddressType
(string
alias)
(Appears on: GatewayAddress)
AddressType defines how a network address is represented as a text string. Valid AddressType values are:
- “IPAddress”
- “NamedAddress”
ConfigMapsDefaultLocalObjectReference
(Appears on: GatewayClassSpec, HTTPRouteAction, HTTPRouteFilter, HTTPRouteHost, HTTPRouteMatch, TCPRouteAction, TCPRouteMatch)
RouteMatchExtensionObjectReference identifies a route-match extension object within a known namespace.
| Field | Description |
|---|---|
group
string
|
(Optional)
Group is the group of the referent. Omitting the value or specifying the empty string indicates the core API group. For example, use the following to specify a configmaps: fooRef: resource: configmaps name: myconfigmap Otherwise, if the core API group is not desired, specify the desired group: fooRef: group: acme.io resource: foos name: myfoo |
resource
string
|
(Optional)
Resource is the API resource name of the referent. Omitting the value or specifying the empty string indicates the configmaps resource. For example, use the following to specify a configmaps resource: fooRef: name: myconfigmap Otherwise, if the configmaps resource is not desired, specify the desired group: fooRef: group: acme.io resource: foos name: myfoo |
name
string
|
Name is the name of the referent. |
ForwardToTarget
(Appears on: HTTPRouteAction, TCPRouteAction)
ForwardToTarget identifies a target object within a known namespace.
| Field | Description |
|---|---|
targetRef
ServicesDefaultLocalObjectReference
|
TargetRef is an object reference to forward matched requests to. The resource may be “services” (omit or use the empty string for the group), or an implementation may support other resources (for example, resource “myroutetargets” in group “networking.acme.io”). Omitting or specifying the empty string for both the resource and group indicates that the resource is “services”. If the referent cannot be found, the “InvalidRoutes” status condition on any Gateway that includes the HTTPRoute will be true. Support: Core (Kubernetes Services) Support: Implementation-specific (Other resource types) |
targetPort
TargetPort
|
(Optional)
TargetPort specifies the destination port number to use for the TargetRef. If unspecified and TargetRef is a Service object consisting of a single port definition, that port will be used. If unspecified and TargetRef is a Service object consisting of multiple port definitions, an error is surfaced in status. Support: Core |
weight
TargetWeight
|
(Optional)
Weight specifies the proportion of traffic forwarded to a targetRef, computed as weight/(sum of all weights in targetRefs). Weight is not a percentage and the sum of weights does not need to equal 100. The following example (in yaml) sends 70% of traffic to service “my-trafficsplit-sv1” and 30% of the traffic to service “my-trafficsplit-sv2”: forwardTo: - targetRef: name: my-trafficsplit-sv1 weight: 70 - targetRef: name: my-trafficsplit-sv2 weight: 30 If only one targetRef is specified, 100% of the traffic is forwarded to the targetRef. If unspecified, weight defaults to 1. Support: Core (httproute) Support: Extended (tcproute) |
filters
[]HTTPRouteFilter
|
(Optional)
Filters defined at this-level should be executed if and only if the request is being forwarded to the target defined here. Conformance: For any implementation, filtering support, including core filters, is NOT guaranteed at this-level. Use Filters in HTTPRouteRule for portable filters across implementations. Support: custom |
GatewayAddress
(Appears on: GatewaySpec, GatewayStatus)
GatewayAddress describes an address that can be bound to a Gateway.
| Field | Description |
|---|---|
type
AddressType
|
(Optional)
Type of the Address. This is either “IPAddress” or “NamedAddress”. Support: Extended |
value
string
|
Value. Examples: “<IP_ADDRESS>”, “128::1”, “my-ip-address”. Validity of the
values will depend on |
GatewayClassCondition
(Appears on: GatewayClassStatus)
GatewayClassCondition contains the details for the current condition of this GatewayClass.
Support: Core, unless otherwise specified.
| Field | Description |
|---|---|
type
GatewayClassConditionType
|
Type of this condition. |
status
Kubernetes core/v1.ConditionStatus
|
Status of this condition. |
reason
string
|
Reason is a machine consumable string for the last transition. It should be a one-word, CamelCase string. Reason will be defined by the controller. Support: Custom; values will be controller-specific. This field must not be empty. |
message
string
|
Message is a human readable reason for last transition. This field may be empty. |
lastTransitionTime
Kubernetes meta/v1.Time
|
LastTransitionTime is the time of the last change to this condition. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable. |
observedGeneration
int64
|
(Optional)
If set, this represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.condition[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance. |
GatewayClassConditionType
(string
alias)
(Appears on: GatewayClassCondition)
GatewayClassConditionType is the type of status conditions.
GatewayClassSpec
(Appears on: GatewayClass)
GatewayClassSpec reflects the configuration of a class of Gateways.
| Field | Description |
|---|---|
controller
string
|
Controller is a domain/path string that indicates the controller that is managing Gateways of this class. Example: “acme.io/gateway-controller”. This field is not mutable and cannot be empty. The format of this field is DOMAIN “/” PATH, where DOMAIN and PATH are valid Kubernetes names (https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names). Support: Core |
allowedGatewayNamespaceSelector
Kubernetes meta/v1.LabelSelector
|
(Optional)
AllowedGatewayNamespaceSelector is a selector of namespaces that Gateways can use this GatewayClass from. This is a standard Kubernetes LabelSelector. Controllers must not support Gateways in namespaces outside this selector. An empty selector (default) indicates that Gateways can use this GatewayClass from any namespace. When a Gateway attempts to use this class from a namespace that is not allowed by this selector, the controller implementing the GatewayClass may add a new “ForbiddenNamespaceForClass” condition to the Gateway status. Adding this condition is considered optional since not all controllers will have access to all namespaces. Support: Core |
allowedRouteNamespaces
RouteNamespaces
|
(Optional)
AllowedRouteNamespaces indicates in which namespaces Routes can be selected for Gateways of this class. This is restricted to the namespace of the Gateway by default. When any Routes are selected by a Gateway in a namespace that is not allowed by this selector, the controller implementing the GatewayClass may add a new “ForbiddenRoutesForClass” condition to the Gateway status. Adding this condition is considered optional since not all controllers will have access to all namespaces. Support: Core |
parametersRef
ConfigMapsDefaultLocalObjectReference
|
(Optional)
ParametersRef is a controller-specific resource containing the configuration parameters corresponding to this class. This is optional if the controller does not require any additional configuration. Valid resources for reference are up to the Controller. Examples include “configmaps” (omit or specify the empty string for the group to indicate the core API group) or a custom resource (CRD). Omitting or specifying the empty string for both the resource and group indicates that the resource is “configmaps”. If the referent cannot be found, the GatewayClass’s “InvalidParameters” status condition will be true. Support: Custom |
GatewayClassStatus
(Appears on: GatewayClass)
GatewayClassStatus is the current status for the GatewayClass.
| Field | Description |
|---|---|
conditions
[]GatewayClassCondition
|
(Optional)
Conditions is the current status from the controller for this GatewayClass. |
GatewayCondition
(Appears on: GatewayStatus)
GatewayCondition is an error status for a given route.
| Field | Description |
|---|---|
type
GatewayConditionType
|
Type indicates the type of condition. |
status
Kubernetes core/v1.ConditionStatus
|
Status describes the current state of this condition. Can be “True”, “False”, or “Unknown”. |
message
string
|
Message is a human-understandable message describing the condition. This field may be empty. |
reason
string
|
Reason indicates why the condition is in this state. This field must not be empty. |
lastTransitionTime
Kubernetes meta/v1.Time
|
LastTransitionTime indicates the last time this condition changed. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable. |
observedGeneration
int64
|
(Optional)
If set, this represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance. |
GatewayConditionType
(string
alias)
(Appears on: GatewayCondition)
GatewayConditionType is a type of condition associated with a Gateway.
GatewayObjectReference
(Appears on: RouteGatewayStatus)
GatewayObjectReference identifies a Gateway object.
| Field | Description |
|---|---|
namespace
string
|
(Optional)
Namespace is the namespace of the referent. |
name
string
|
Name is the name of the referent. |
GatewaySpec
(Appears on: Gateway)
GatewaySpec defines the desired state of Gateway.
Not all possible combinations of options specified in the Spec are valid. Some invalid configurations can be caught synchronously via a webhook, but there are many cases that will require asynchronous signaling via the GatewayStatus block.
| Field | Description |
|---|---|
class
string
|
Class used for this Gateway. This is the name of a GatewayClass resource. |
listeners
[]Listener
|
Listeners associated with this Gateway. Listeners define logical endpoints that are bound on this Gateway’s addresses. At least one Listener MUST be specified. Each Listener in this array must have a unique Port field, however a GatewayClass may collapse compatible Listener definitions into a single implementation-defined acceptor configuration even if their Port fields would otherwise conflict. Listeners are compatible if all of the following conditions are true:
As a special case, each group of compatible listeners may contain exactly one Listener with a match type of “Any”. If the GatewayClass collapses compatible Listeners, the hostname provided in the incoming client request MUST be matched to a Listener to find the correct set of Routes. The incoming hostname MUST be matched using the Hostname field for each Listener in order of most to least specific. That is, “Exact” matches must be processed before “Domain” matches, which must be processed before “Any” matches. If this field specifies multiple Listeners that have the same Port value but are not compatible, the GatewayClass must raise a “PortConflict” condition on the Gateway. Support: Core |
addresses
[]GatewayAddress
|
(Optional)
Addresses requested for this gateway. This is optional and behavior can depend on the GatewayClass. If a value is set in the spec and the requested address is invalid, the GatewayClass MUST indicate this in the associated entry in GatewayStatus.Addresses. If no Addresses are specified, the GatewayClass may schedule the Gateway in an implementation-defined manner, assigning an appropriate set of Addresses. The GatewayClass MUST bind all Listeners to every GatewayAddress that it assigns to the Gateway. Support: Core |
GatewayStatus
(Appears on: Gateway)
GatewayStatus defines the observed state of Gateway.
| Field | Description |
|---|---|
addresses
[]GatewayAddress
|
Addresses lists the IP addresses that have actually been bound to the Gateway. These addresses may differ from the addresses in the Spec, e.g. if the Gateway automatically assigns an address from a reserved pool. These addresses should all be of type “IPAddress”. |
conditions
[]GatewayCondition
|
(Optional)
Conditions describe the current conditions of the Gateway. |
listeners
[]ListenerStatus
|
(Optional)
Listeners provide status for each unique listener port defined in the Spec. |
HTTPHeaderMatch
(Appears on: HTTPRouteMatch)
HTTPHeaderMatch describes how to select a HTTP route by matching HTTP request headers.
| Field | Description |
|---|---|
type
HeaderMatchType
|
(Optional)
HeaderMatchType specifies how to match a HTTP request header against the Values map. Support: core (Exact) Support: custom (ImplementationSpecific) Default: “Exact” |
values
map[string]string
|
Values is a map of HTTP Headers to be matched. It MUST contain at least one entry. The HTTP header field name to match is the map key, and the value of the HTTP header is the map value. HTTP header field names MUST be matched case-insensitively. Multiple match values are ANDed together, meaning, a request must match all the specified headers to select the route. |
HTTPPathMatch
(Appears on: HTTPRouteMatch)
HTTPPathMatch describes how to select a HTTP route by matching the HTTP request path.
| Field | Description |
|---|---|
type
PathMatchType
|
(Optional)
Type specifies how to match against the path Value. Support: core (Exact, Prefix) Support: custom (RegularExpression, ImplementationSpecific) Since RegularExpression PathType has custom conformance, implementations can support POSIX, PCRE or any other dialects of regular expressions. Please read the implementation’s documentation to determine the supported dialect. Default: “Prefix” |
value
string
|
Value of the HTTP path to match against. |
HTTPRequestHeaderConfig
(Appears on: HTTPRouteFilter)
HTTPRequestHeaderConfig defines configuration for the RequestHeader filter.
| Field | Description |
|---|---|
add
map[string]string
|
Add adds the given header (name, value) to the request before the action. Input: GET /foo HTTP/1.1 Config: add: {“my-header”: “foo”} Output: GET /foo HTTP/1.1 my-header: foo Support: extended? |
remove
[]string
|
Remove the given header(s) from the HTTP request before the action. The value of RemoveHeader is a list of HTTP header names. Note that the header names are case-insensitive [RFC-2616 4.2]. Input: GET /foo HTTP/1.1 My-Header1: ABC My-Header2: DEF My-Header2: GHI Config: remove: [“my-header1”, “my-header3”] Output: GET /foo HTTP/1.1 My-Header2: DEF Support: extended? |
HTTPRouteAction
(Appears on: HTTPRouteRule)
HTTPRouteAction is the action taken given a match.
| Field | Description |
|---|---|
forwardTo
[]ForwardToTarget
|
ForwardTo sends requests to the referenced object(s). The resource may be “services” (omit or use the empty string for the group), or an implementation may support other resources (for example, resource “myroutetargets” in group “networking.acme.io”). Omitting or specifying the empty string for both the resource and group indicates that the resource is “services”. If the referent cannot be found, the “InvalidRoutes” status condition on any Gateway that includes the HTTPRoute will be true. Support: core |
extensionRef
ConfigMapsDefaultLocalObjectReference
|
(Optional)
ExtensionRef is an optional, implementation-specific extension to the “action” behavior. The resource may be “configmaps” (use the empty string for the group) or an implementation-defined resource (for example, resource “myrouteactions” in group “networking.acme.io”). Omitting or specifying the empty string for both the resource and group indicates that the resource is “configmaps”. If the referent cannot be found, the “InvalidRoutes” status condition on any Gateway that includes the HTTPRoute will be true. Support: custom |
HTTPRouteFilter
(Appears on: ForwardToTarget, HTTPRouteRule)
HTTPRouteFilter defines additional processing steps that must be completed during the request or response lifecycle. HTTPRouteFilters are meant as an extension point to express additional processing that may be done in Gateway implementations. Some examples include request or response modification, implementing authentication strategies, rate-limiting, and traffic shaping. API guarantee/conformance is defined based on the type of the filter. TODO(hbagdi): re-render CRDs once controller-tools supports union tags: - https://github.com/kubernetes-sigs/controller-tools/pull/298 - https://github.com/kubernetes-sigs/controller-tools/issues/461
| Field | Description |
|---|---|
type
string
|
Type identifies the filter to execute.
Types are classified into three conformance-levels (similar to
other locations in this API):
- Core and extended: These filter types and their corresponding configuration
is defined in this package. All implementations must implement
the core filters. Implementers are encouraged to support extended filters.
Definitions for filter-specific configuration for these
filters is defined in this package.
- Custom: These filters are defined and supported by specific vendors.
In the future, filters showing convergence in behavior across multiple
implementations will be considered for inclusion in extended or core
conformance rings. Filter-specific configuration for such filters
is specified using the ExtensionRef field. Implementers are encouraged to define custom implementation types to extend the core API with implementation-specific behavior. |
extensionRef
ConfigMapsDefaultLocalObjectReference
|
(Optional)
ExtensionRef is an optional, implementation-specific extension to the “filter” behavior. The resource may be “configmap” (use the empty string for the group) or an implementation-defined resource (for example, resource “myroutefilters” in group “networking.acme.io”). Omitting or specifying the empty string for both the resource and group indicates that the resource is “configmaps”. ExtensionRef MUST NOT be used for core and extended filters. |
requestHeader
HTTPRequestHeaderConfig
|
HTTPRouteHost
(Appears on: HTTPRouteSpec)
HTTPRouteHost is the configuration for a given set of hosts.
| Field | Description |
|---|---|
hostnames
[]string
|
(Optional)
Hostnames defines a set of hostname that should match against the HTTP Host header to select a HTTPRoute to process the request. Hostname is the fully qualified domain name of a network host, as defined by RFC 3986. Note the following deviations from the “host” part of the URI as defined in the RFC:
Incoming requests are matched against the hostnames before the HTTPRoute rules. If no hostname is specified, traffic is routed based on the HTTPRouteRules. Hostname can be “precise” which is a domain name without the terminating dot of a network host (e.g. “foo.example.com”) or “wildcard”, which is a domain name prefixed with a single wildcard label (e.g. “.example.com”). The wildcard character ‘’ must appear by itself as the first DNS label and matches only a single label. You cannot have a wildcard label by itself (e.g. Host == “*”). Requests will be matched against the Host field in the following order: 1. If Host is precise, the request matches this rule if the http host header is equal to Host. 2. If Host is a wildcard, then the request matches this rule if the http host header is to equal to the suffix (removing the first label) of the wildcard rule. Support: Core |
rules
[]HTTPRouteRule
|
Rules are a list of HTTP matchers, filters and actions. |
extensionRef
ConfigMapsDefaultLocalObjectReference
|
(Optional)
ExtensionRef is an optional, implementation-specific extension to the “host” block. The resource may be “configmaps” (omit or specify the empty string for the group) or an implementation-defined resource (for example, resource “myroutehosts” in group “networking.acme.io”). Omitting or specifying the empty string for both the resource and group indicates that the resource is “configmaps”. If the referent cannot be found, the “InvalidRoutes” status condition on any Gateway that includes the HTTPRoute will be true. Support: custom |
HTTPRouteMatch
(Appears on: HTTPRouteRule)
HTTPRouteMatch defines the predicate used to match requests to a given action. Multiple match types are ANDed together, i.e. the match will evaluate to true only if all conditions are satisfied.
For example, the match below will match a HTTP request only if its path
starts with /foo
AND it contains the version: "1"
header:
match:
path:
value: "/foo"
headers:
values:
version: "1"
| Field | Description |
|---|---|
path
HTTPPathMatch
|
(Optional)
Path specifies a HTTP request path matcher. If this field is not specified, a default prefix match on the “/” path is provided. |
headers
HTTPHeaderMatch
|
(Optional)
Headers specifies a HTTP request header matcher. |
extensionRef
ConfigMapsDefaultLocalObjectReference
|
(Optional)
ExtensionRef is an optional, implementation-specific extension to the “match” behavior. The resource may be “configmap” (use the empty string for the group) or an implementation-defined resource (for example, resource “myroutematchers” in group “networking.acme.io”). Omitting or specifying the empty string for both the resource and group indicates that the resource is “configmaps”. If the referent cannot be found, the “InvalidRoutes” status condition on any Gateway that includes the HTTPRoute will be true. Support: custom |
HTTPRouteRule
(Appears on: HTTPRouteHost)
HTTPRouteRule defines semantics for matching an incoming HTTP request against a set of matching rules and executing an action (and optionally filters) on the request.
| Field | Description |
|---|---|
matches
[]HTTPRouteMatch
|
(Optional)
Matches define conditions used for matching the rule against incoming HTTP requests. Each match is independent, i.e. this rule will be matched if any one of the matches is satisfied. For example, take the following matches configuration:
For a request to match against this rule, a request should satisfy EITHER of the two conditions:
See the documentation for HTTPRouteMatch on how to specify multiple match conditions that should be ANDed together. If no matches are specified, the default is a prefix path match on “/”, which has the effect of matching every HTTP request. |
filters
[]HTTPRouteFilter
|
(Optional)
Filters define the filters that are applied to requests that match this rule. The effects of ordering of multiple behaviors are currently undefined. This can change in the future based on feedback during the alpha stage. Conformance-levels at this level are defined based on the type of filter: - ALL core filters MUST be supported by all implementations. - Implementers are encouraged to support extended filters. - Implementation-specific custom filters have no API guarantees across implementations. Specifying a core filter multiple times has undefined or custom conformance. Support: core |
action
HTTPRouteAction
|
(Optional)
Action defines what happens to the request. |
HTTPRouteSpec
(Appears on: HTTPRoute)
HTTPRouteSpec defines the desired state of HTTPRoute
| Field | Description |
|---|---|
hosts
[]HTTPRouteHost
|
Hosts is a list of Host definitions. |
HTTPRouteStatus
(Appears on: HTTPRoute)
HTTPRouteStatus defines the observed state of HTTPRoute.
| Field | Description |
|---|---|
gateways
[]RouteGatewayStatus
|
Gateways is a list of the Gateways that are associated with the HTTPRoute, and the status of the route with respect to each of these Gateways. When a Gateway selects this route, the controller that manages the Gateway should add an entry to this list when the controller first sees the route and should update the entry as appropriate when the route is modified. |
HeaderMatchType
(string
alias)
(Appears on: HTTPHeaderMatch)
HeaderMatchType specifies the semantics of how HTTP headers should be compared. Valid HeaderMatchType values are:
- “Exact”
- “ImplementationSpecific”
HostnameMatch
(Appears on: Listener)
HostnameMatch specifies how a Listener should match the incoming hostname from a client request. Depending on the incoming protocol, the match must apply to names provided by the client at both the TLS and the HTTP protocol layers.
| Field | Description |
|---|---|
match
HostnameMatchType
|
(Optional)
Match specifies how the hostname provided by the client should be matched against the given value. |
name
string
|
(Optional)
Name contains the name to match against. This value must be a fully qualified host or domain name conforming to the preferred name syntax defined in RFC 1034 In addition to any RFC rules, this field MUST NOT contain
This field is required for the “Domain” and “Exact” match types. |
HostnameMatchType
(string
alias)
(Appears on: HostnameMatch)
HostnameMatchType specifies the types of matches that are valid for hostnames. Valid match types are:
- “Domain”
- “Exact”
- “Any”
Listener
(Appears on: GatewaySpec)
Listener embodies the concept of a logical endpoint where a Gateway can accept network connections.
| Field | Description |
|---|---|
hostname
HostnameMatch
|
(Optional)
Hostname specifies to match the virtual hostname for protocol types that define this concept. Incoming requests that include a hostname are matched according to the given HostnameMatchType to select the Routes from this Listener. If a match type other than “Any” is supplied, it MUST be compatible with the specified Protocol field. Support: Core |
port
int32
|
Port is the network port. Multiple listeners may use the same port, subject to the Listener compatibility rules. Support: Core |
protocol
ProtocolType
|
Protocol specifies the network protocol this listener expects to receive. The GatewayClass MUST validate that match type specified in the Hostname field is appropriate for the protocol.
Support: Core |
tls
TLSConfig
|
(Optional)
TLS is the TLS configuration for the Listener. This field is required if the Protocol field is “HTTPS” or “TLS” and ignored otherwise. Support: Core |
routes
RouteBindingSelector
|
Routes specifies a schema for associating routes with the Listener using selectors. A Route is a resource capable of servicing a request and allows a cluster operator to expose a cluster resource (i.e. Service) by externally-reachable URL, load-balance traffic and terminate SSL/TLS. Typically, a route is a “HTTPRoute” or “TCPRoute” in group “networking.x-k8s.io”, however, an implementation may support other types of resources. The Routes selector MUST select a set of objects that are compatible with the application protocol specified in the Protocol field. Support: Core |
ListenerCondition
(Appears on: ListenerStatus)
ListenerCondition is an error status for a given listener.
| Field | Description |
|---|---|
type
ListenerConditionType
|
Type indicates the type of condition. |
status
Kubernetes core/v1.ConditionStatus
|
Status describes the current state of this condition. Can be “True”, “False”, or “Unknown”. |
message
string
|
Message is a human-understandable message describing the condition. This field may be empty. |
reason
string
|
Reason indicates why the condition is in this state. This field must not be empty. |
lastTransitionTime
Kubernetes meta/v1.Time
|
LastTransitionTime indicates the last time this condition changed. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable. |
observedGeneration
int64
|
(Optional)
If set, this represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance. |
ListenerConditionType
(string
alias)
(Appears on: ListenerCondition)
ListenerConditionType is a type of condition associated with the listener.
ListenerStatus
(Appears on: GatewayStatus)
ListenerStatus is the status associated with a Listener port.
| Field | Description |
|---|---|
port
string
|
Port is the unique Listener port value for which this message is reporting the status. If more than one Gateway Listener shares the same port value, this message reports the combined status of all such Listeners. |
conditions
[]ListenerCondition
|
Conditions describe the current condition of this listener. |
PathMatchType
(string
alias)
(Appears on: HTTPPathMatch)
PathMatchType specifies the semantics of how HTTP paths should be compared. Valid PathMatchType values are:
- “Exact”
- “Prefix”
- “RegularExpression”
- “ImplementationSpecific”
ProtocolType
(string
alias)
(Appears on: Listener)
ProtocolType defines the application protocol accepted by a Listener. Implementations are not required to accept all the defined protocols. If an implementation does not support a specified protocol, it should raise a “ConditionUnsupportedProtocol” condition for the affected Listener.
Valid ProtocolType values are:
- “HTTP”
- “HTTPS”
- “TLS”
- “TCP”
RouteBindingSelector
(Appears on: Listener)
RouteBindingSelector defines a schema for associating routes with the Gateway. If NamespaceSelector and RouteSelector are defined, only routes matching both selectors are associated with the Gateway.
| Field | Description |
|---|---|
routeNamespaces
RouteNamespaces
|
(Optional)
RouteNamespaces indicates in which namespaces Routes should be selected for this Gateway. This is restricted to the namespace of this Gateway by default. Support: Core |
routeSelector
Kubernetes meta/v1.LabelSelector
|
(Optional)
RouteSelector specifies a set of route labels used for selecting routes to associate with the Gateway. If RouteSelector is defined, only routes matching the RouteSelector are associated with the Gateway. An empty RouteSelector matches all routes. Support: Core |
group
string
|
(Optional)
Group is the group of the route resource to select. Omitting the value or specifying the empty string indicates the networking.x-k8s.io API group. For example, use the following to select an HTTPRoute: routes: resource: httproutes Otherwise, if an alternative API group is desired, specify the desired group: routes: group: acme.io resource: fooroutes Support: Core |
resource
string
|
Resource is the API resource name of the route resource to select. Resource MUST correspond to route resources that are compatible with the application protocol specified in the Listener’s Protocol field. If an implementation does not support or recognize this resource type, it SHOULD raise a “ConditionInvalidRoutes” condition for the affected Listener. Support: Core |
RouteCondition
(Appears on: RouteGatewayStatus)
RouteCondition is a status condition for a given route.
| Field | Description |
|---|---|
type
RouteConditionType
|
Type indicates the type of condition. |
status
Kubernetes core/v1.ConditionStatus
|
Status describes the current state of this condition. Can be “True”, “False”, or “Unknown”. |
message
string
|
(Optional)
Message is a human-understandable message describing the condition. |
reason
string
|
(Optional)
Reason indicates why the condition is in this state. |
lastTransitionTime
Kubernetes meta/v1.Time
|
(Optional)
LastTransitionTime indicates the last time this condition changed. |
RouteConditionType
(string
alias)
(Appears on: RouteCondition)
RouteConditionType is a type of condition for a route.
RouteGatewayStatus
(Appears on: HTTPRouteStatus, TCPRouteStatus)
RouteGatewayStatus describes the status of a route with respect to an associated Gateway.
| Field | Description |
|---|---|
gatewayRef
GatewayObjectReference
|
GatewayRef is a reference to a Gateway object that is associated with the route. |
conditions
[]RouteCondition
|
Conditions describes the status of the route with respect to the Gateway. For example, the “Admitted” condition indicates whether the route has been admitted or rejected by the Gateway, and why. Note that the route’s availability is also subject to the Gateway’s own status conditions and listener status. |
RouteNamespaces
(Appears on: GatewayClassSpec, RouteBindingSelector)
RouteNamespaces is used by Gateway and GatewayClass to indicate which namespaces Routes should be selected from.
| Field | Description |
|---|---|
namespaceSelector
Kubernetes meta/v1.LabelSelector
|
(Optional)
NamespaceSelector is a selector of namespaces that Routes should be selected from. This is a standard Kubernetes LabelSelector, a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. Controllers must not support Routes in namespaces outside this selector. An empty selector (default) indicates that Routes in any namespace can be selected. The OnlySameNamespace field takes precedence over this field. This selector will only take effect when OnlySameNamespace is false. Support: Core |
onlySameNamespace
bool
|
(Optional)
OnlySameNamespace is a boolean used to indicate if Route references are limited to the same Namespace as the Gateway. When true, only Routes within the same Namespace as the Gateway should be selected. This field takes precedence over the NamespaceSelector field. That selector should only take effect when this field is set to false. Support: Core |
SecretsDefaultLocalObjectReference
(Appears on: TLSConfig)
SecretsDefaultLocalObjectReference identifies an API object within a known namespace that defaults group to core and resource to secrets if unspecified.
| Field | Description |
|---|---|
group
string
|
(Optional)
Group is the group of the referent. Omitting the value or specifying the empty string indicates the core API group. For example, use the following to specify a secrets resource: fooRef: resource: secrets name: mysecret Otherwise, if the core API group is not desired, specify the desired group: fooRef: group: acme.io resource: foos name: myfoo |
resource
string
|
(Optional)
Resource is the API resource name of the referent. Omitting the value or specifying the empty string indicates the secrets resource. For example, use the following to specify a secrets resource: fooRef: name: mysecret Otherwise, if the secrets resource is not desired, specify the desired group: fooRef: group: acme.io resource: foos name: myfoo |
name
string
|
Name is the name of the referent. |
ServicesDefaultLocalObjectReference
(Appears on: ForwardToTarget)
ServicesDefaultLocalObjectReference identifies an API object within a known namespace that defaults group to core and resource to services if unspecified.
| Field | Description |
|---|---|
group
string
|
(Optional)
Group is the group of the referent. Omitting the value or specifying the empty string indicates the core API group. For example, use the following to specify a service: fooRef: resource: services name: myservice Otherwise, if the core API group is not desired, specify the desired group: fooRef: group: acme.io resource: foos name: myfoo |
resource
string
|
(Optional)
Resource is the API resource name of the referent. Omitting the value or specifying the empty string indicates the services resource. For example, use the following to specify a services resource: fooRef: name: myservice Otherwise, if the services resource is not desired, specify the desired group: fooRef: group: acme.io resource: foos name: myfoo |
name
string
|
Name is the name of the referent. |
TCPRouteAction
(Appears on: TCPRouteRule)
TCPRouteAction is the action for a given rule.
| Field | Description |
|---|---|
forwardTo
[]ForwardToTarget
|
ForwardTo sends requests to the referenced object(s). The resource may be “services” (omit or use the empty string for the group), or an implementation may support other resources (for example, resource “myroutetargets” in group “networking.acme.io”). Omitting or specifying the empty string for both the resource and group indicates that the resource is “services”. If the referent cannot be found, the “InvalidRoutes” status condition on any Gateway that includes the HTTPRoute will be true. Support: core |
extensionRef
ConfigMapsDefaultLocalObjectReference
|
(Optional)
ExtensionRef is an optional, implementation-specific extension to the “action” behavior. The resource may be “configmaps” (use the empty string for the group) or an implementation-defined resource (for example, resource “myrouteactions” in group “networking.acme.io”). Omitting or specifying the empty string for both the resource and group indicates that the resource is “configmaps”. If the referent cannot be found, the “InvalidRoutes” status condition on any Gateway that includes the TCPRoute will be true. Support: custom |
TCPRouteMatch
(Appears on: TCPRouteRule)
TCPRouteMatch defines the predicate used to match connections to a given action.
| Field | Description |
|---|---|
extensionRef
ConfigMapsDefaultLocalObjectReference
|
(Optional)
ExtensionRef is an optional, implementation-specific extension to the “match” behavior. The resource may be “configmap” (use the empty string for the group) or an implementation-defined resource (for example, resource “myroutematchers” in group “networking.acme.io”). Omitting or specifying the empty string for both the resource and group indicates that the resource is “configmaps”. If the referent cannot be found, the “InvalidRoutes” status condition on any Gateway that includes the TCPRoute will be true. Support: custom |
TCPRouteRule
(Appears on: TCPRouteSpec)
TCPRouteRule is the configuration for a given rule.
| Field | Description |
|---|---|
match
TCPRouteMatch
|
(Optional)
Match defines which connections match this rule. |
action
TCPRouteAction
|
(Optional)
Action defines what happens to the connection. |
TCPRouteSpec
(Appears on: TCPRoute)
TCPRouteSpec defines the desired state of TCPRoute
| Field | Description |
|---|---|
rules
[]TCPRouteRule
|
Rules are a list of TCP matchers and actions. |
TCPRouteStatus
(Appears on: TCPRoute)
TCPRouteStatus defines the observed state of TCPRoute
| Field | Description |
|---|---|
gateways
[]RouteGatewayStatus
|
Gateways is a list of the Gateways that are associated with the TCPRoute, and the status of the route with respect to each of these Gateways. When a Gateway selects this route, the controller that manages the Gateway should add an entry to this list when the controller first sees the route and should update the entry as appropriate when the route is modified. |
TLSConfig
(Appears on: Listener)
TLSConfig describes a TLS configuration.
References - nginx: https://nginx.org/en/docs/http/configuring_https_servers.html - envoy: https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/auth/cert.proto - haproxy: https://www.haproxy.com/documentation/aloha/9-5/traffic-management/lb-layer7/tls/ - gcp: https://cloud.google.com/load-balancing/docs/use-ssl-policies#creating_an_ssl_policy_with_a_custom_profile - aws: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-https-listener.html#describe-ssl-policies - azure: https://docs.microsoft.com/en-us/azure/app-service/configure-ssl-bindings#enforce-tls-1112
| Field | Description |
|---|---|
certificateRefs
[]SecretsDefaultLocalObjectReference
|
CertificateRefs is a list of references to Kubernetes objects that each contain an identity certificate. The host name in a TLS SNI client hello message is used for certificate matching and route host name selection. The SNI server_name must match a route host name for the Gateway to route the TLS request. If an entry in this list omits or specifies the empty string for both the group and the resource, the resource defaults to “secrets”. An implementation may support other resources (for example, resource “mycertificates” in group “networking.acme.io”). Support: Core (Kubernetes Secrets) Support: Implementation-specific (Other resource types) |
options
map[string]string
|
Options are a list of key/value pairs to give extended options to the provider. There variation among providers as to how ciphersuites are expressed. If there is a common subset for expressing ciphers then it will make sense to loft that as a core API construct. Support: Implementation-specific. |
TargetPort
(int32
alias)
(Appears on: ForwardToTarget)
TargetPort specifies the destination port number to use for a TargetRef.
TargetWeight
(int32
alias)
(Appears on: ForwardToTarget)
TargetWeight specifies weight used for making a forwarding decision to a TargetRef.
Generated with gen-crd-api-reference-docs
.


Purchases
Purchased
$ 159. 00
2 per week
$ 349. 00
8 per month
Accumulative discount
More info
3 %
3400 $
Balance sheet history
$ 1539. 00
Purchase
- All
- Purchase
- Replenishent
- Referal
Description
Lisence
Bill
Date
Sum
Replenishment
Lisence
Visa
32**********5628
12.05.18
$ 175.00
Withdrawal
Lisence
Master Card
32**********5628
14.05.18
$ 155.00
Purchase
Lisence
Visa
32**********5628
24.07.18
$ 465.00
Description
Lisence
Date
Sum
Status
Replenishment
Lisence
12.05.18
$ 175.00
In process
Withdrawal
Lisence
14.05.18
$ 155.00
Abort
Purchase
Lisence
24.07.18
$ 465.00
Done
Choose goods for return
Describe the reason for the return
Quick advice
Carefully describe the problem, this will speed up the decision of the moderator
Type
Type reason
- First type
- Second type
- Third type
Description


{% extends 'base.html' %} {% block title %}Home{% endblock %} {% block content %}
This site is still in development. To be honest I don't know why yu created an account
If you look back later I might have done somthing but for now every page is filler
{% endblock %}


This is the official AtomicDEX mobile beta program channel -
Android: https://play.google.com/store/apps/details?id=com.komodoplatform.atomicdex - iOS: https://testflight.apple.com/join/c2mOLEoC - Please use https://github.com/KomodoPlatform/atomicdex/issues for bug reports and feature requests. For critical security bug reports please do send us your encrypted (https://pgp.mit.edu/pks/lookup?op=get&search=0x379287998EE6CF47) report to<EMAIL_ADDRESS>and allow up to 24h for reply. For atomicDEX API (mm2) related issue reports or feature requests please do use https://github.com/KomodoPlatform/atomicDEX-API/issues
100 messages
Before 05-Dec-19 12:00 AM
Sharifa03-Aug-19 10:58 AM
What does that mean? I have enough KMD to pay for the fees
gcharang03-Aug-19 10:59 AM
@Sharifa to trade ETH/ERC20 tokens, you need some ETH in your wallet to pay gas fees
1
Sharifa03-Aug-19 11:01 AM
@gcharang ok thank you. Didn't know that
gcharang03-Aug-19 11:01 AM
as cipi said above
in a swap that involves ERC20 tokens both maker and taker need to pay gasfees at different stages of the swap
Sharifa03-Aug-19 11:04 AM
@gcharang sorry... didn't check comments above
JvdP03-Aug-19 12:15 PM
Not sure whether anyone commented on this yet, but I have mixed feelings about the UI regarding the order book. Let's say I select that I want to sell my 10 KMD. I used to see how much of each coin I could get for my amount, and now it shows how many bids are out there for each coin instead. I have to click on the order book to see what the best bid actually is. That's okay if I know which coin I want to buy (the "serious" use case), but annoying if I just want to play around and maybe see if there's any "dumb" orders out there (the "casual" use case). Any chance we can have both types of information in the interface? E.g. BTC - 3 - best: 0.001 BTC (where 3 is the number of orders out there; maybe put that in a header or something).
Werxadler03-Aug-19 12:24 PM
@gcharang meanwhile another swap completed, and one reported timeout, i guess the one with reported timeout cleared all other orders for morty, and the other swap for rick took just too long, even though there was no ongooing swap reported
@Werxadler can you confirm the app version is 0.1.5?
Werxadler03-Aug-19 01:25 PM
@gcharang yes, 1.5
1
Spyda9603-Aug-19 03:37 PM
hi
Werxadler03-Aug-19 03:38 PM
Now i created 4 new orders, succesfully order confirmed, don't see them in my orders though, log out and log in doesn't fix the issue
Spyda9603-Aug-19 03:42 PM
are there any FAQs for the beta, nevermind found the pins was looking for morty and ricks(edited)
Acura03-Aug-19 04:04 PM
For all iOS users the new update for AtomicDEX is now available in TestFlight
Spyda9603-Aug-19 04:30 PM
10 mins for order matching, I wish my screen would not timeout
27aume03-Aug-19 04:48 PM
HI, I get some weird behavior,
- I've created an order RFOX_KMD
- It got partialy filled, but the created order didnt updated I still see it untouched in order list
- Then I made a taker order with rest of my RFOX balance, the order never appeared in order list but completed and appeared 5min later in trade history.
- At the end now I have no more RFOX and the initial created order is still showing in orderlist untouched(edited)
27aume03-Aug-19 05:03 PM
.
Also it looks like Maker orders doesnt close after being filled in UI
Angelina03-Aug-19 05:11 PM
@27aume can you DM me logs along with the order IDs, please?
Spyda9603-Aug-19 05:12 PM
anyone trading anything other then ricks or morts
27aume03-Aug-19 05:13 PM
yes no prob
27aume03-Aug-19 05:39 PM
I have a little feedback
For created order(maker) I would be good to have some sort of indicator that the order is still broadcasted/active.
At the moment only having it listed in order list leave place to uncertainty and confusion.
Maybe a little circle loading style
A status code
3little dots loading style
Something like that.
(obviously that in the small tweak category, not a urging matter but still )
weldon.gull503-Aug-19 06:20 PM
\I have received the invitation test, but GOOGLEPLAY can't download
Spyda9603-Aug-19 07:33 PM
I think you have to go through link
Werxadler03-Aug-19 08:57 PM
Meanwhile 5 succesfull swaps, 1 timeout, still my orderbook is empty
Hi. My link to Google Play is not working. "App not available". (Not available for my Google Play account.) Who do I contact in a private message to enable my email address so that I can joint AtomixDEX beta testing?
@ca333 I have same screen as on screenshot on my side, I wonder this issue clue is not precise message: after "Click to create an order" option usage it's better to print something like a "Input amount of BTC you want to get" below the "Receive" section so for user will be clear that "Trade" button will became active after BTC amount input
Price was 1 KMD for ~0.017 RFOX, pretty bad deal yes
花果山04-Aug-19 11:12 AM
@TonyL No corresponding order
Only 0.013, no 0.017.
@TonyL When an order is selected (the current order can be locked, the maximum is selected, the current order should be filled), sometimes the maximum is selected, and it will automatically change to other orders.
I choose the top order 51.12RFOX, and then click the maximum, it will automatically jump to the bottom of the order 0.013.
The current order cannot be locked and the current order is not automatically calculated.
TonyL04-Aug-19 11:25 AM
top order with price 51.12 RFOX have maximum volume 4.4 RFOX (~0.086 KMD). There is an issue that base coin amount (KMD in your case) not updating atomatically on trade view
I wonder what happened is that only one order which fit 1 KMD volume was this bad price one, but it's bad that swap started without confirmation about price change
@花果山 has you input 1 KMD or used max button?
花果山04-Aug-19 11:29 AM
I entered 1KMD.
But please don't deny that the order will automatically change the problem.
Unable to lock, orders that have been selected will change, you can click the maximum, try.
TonyL04-Aug-19 11:34 AM
just tried same case on my side - yes, it's not adjusting KMD max volume for best order (4 RFOX at 51 RFOX/KMD price) which can not fit all base coin volume (1 KMD in our case). But on cofirmation screen it printed 1 KMD to 4 RFOX (best order which can fit 1 KMD volume)
And after I pressed Confirm button swap 1 KMD to 4 RFOX started
So I can't reproduce swap with price different to price on swap confirmation screen
Max volume adjusting will be implemented (developers aware of it)
Sold 2 KMD for 8 RFOX - somebody should be happy
花果山04-Aug-19 11:40 AM
I lost 1 KMD. it's OK. But in the future, more newcomers will use it, if you can't lock the order you have already selected. There will be more users complaining in the future. Any change at a time is a loss.
I am very afraid that there will be an attack API method, and the exchange price will be changed one second before the confirmation.
TonyL04-Aug-19 11:45 AM
Can you remember what price you saw on confrimation screen?
花果山04-Aug-19 11:47 AM
@TonyL Two exchanges before and after, only one minute apart, I can't remember.
TonyL04-Aug-19 11:49 AM
Please doublecheck price on confrimation screen before swap start, if price in swap is different from value on this screen it's very bad bug, but I'm not able to reproduce
花果山04-Aug-19 11:49 AM
Just hope that orders should not be changed at will, just fine.
花果山04-Aug-19 12:23 PM
@TonyL<EMAIL_ADDRESS>Can I add a test user?
TonyL04-Aug-19 12:24 PM
Sure @花果山 For Android, correct?
!kmdtip @花果山 1
KMD TipBotBOT04-Aug-19 12:24 PM
TipBot
@TonyL (TonyL#3577)
You tipped @花果山1 KMD
TonyL04-Aug-19 12:26 PM
Some trade loss coverage Next time please track carefully amounts on low liquidity markets. We'll make UX more clear for such cases in next version(edited)
花果山04-Aug-19 12:27 PM
@TonyL Thank you, the loss is nothing. It's all tested, it's better for the wallet.
1
<EMAIL_ADDRESS>When can he download it?
TonyL04-Aug-19 12:30 PM
He was added to list - it's propagating once per day so he'll be added today/tomororow max
花果山04-Aug-19 12:33 PM
Thank you
TonyL04-Aug-19 12:37 PM
Glad to help!
general_grievous04-Aug-19 01:10 PM
I canceled a trade but it didn't immediately reflect in my bamalces. Is this normal?


Array
extension Array
extension Array:DataContaining
extension Array where Element == String?
extension Array where Element: NSObjectProtocol
extension Array where Element: Equatable
extension Array where Element: RawRepresentable
extension Array where Element:Hashable
public extension Array where Element :Copying
-
binary search
Declaration
Swift
public func binarySearch<T>(target: T, transform: (Element) -> T, _ comparison: (T, T) -> ComparisonResult) -> Int?
Parameters
target
target
transform
transform
comparison
comparision
Return Value
Int
-
remove
Declaration
Swift
public mutating func remove(at indexs: Set<Int>)
Parameters
indexs
index
-
Array方法扩展，支持根据索引数组删除
Declaration
Swift
public mutating func removeAtIndexes(indexs: [Int])
-
Undocumented
Declaration
Swift
subscript(guarded index: Int) -> Element? { get }
-
Returns a random subarray of given length.
Declaration
Swift
public func randomElements(count: Int = 1) -> Array<Element>
Parameters
count
Number of random elements to return.
Return Value
Random subarray of length n.
-
Returns a random element from
self
.Declaration
Swift
public func randomElement() -> Element
-
Split array by chunks of given size.
let array = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12] let chunks = array.splitBy(5) print(chunks) // [[1, 2, 3, 4, 5], [6, 7, 8, 9, 10], [11, 12]]
Declaration
Swift
public func splitBy(_ subSize: Int) -> [[Element]]
-
Undocumented
Declaration
Swift
public func firstElement<T>(type: T.Type) -> T?
-
last element
Declaration
Swift
public func lastElement<T>(type: T.Type) -> T?
Parameters
type
T.type
Return Value
T
-
Undocumented
Declaration
Swift
public typealias ItemType = Element
-
Undocumented
Declaration
Swift
public var data: [ItemType] { get }
-
joined
Declaration
Swift
public func joined(_ separator: String = "") -> String
Parameters
separator
separator
Return Value
string
-
Returns the first index where the specified value appears in the collection.
After using
firstIndex(of:)
to find the position of a particular element in a collection, you can use it to access the element by subscripting. This example shows how you can pop one of the view controller from theUINavigationController
.let navigationController = UINavigationController() if let index = navigationController.viewControllers.firstIndex(of: SearchViewController.self) { navigationController.popToViewController(at: index, animated: true) }
Declaration
Swift
public func firstIndex(of elementType: Element.Type) -> Int?
Parameters
elementType
An element type to search for in the collection.
Return Value
The first index where
element
is found. Ifelement
is not found in the collection, returnsnil
. -
Returns the last index where the specified value appears in the collection.
After using
lastIndex(of:)
to find the position of a particular element in a collection, you can use it to access the element by subscripting. This example shows how you can pop one of the view controller from theUINavigationController
.let navigationController = UINavigationController() if let index = navigationController.viewControllers.lastIndex(of: SearchViewController.self) { navigationController.popToViewController(at: index, animated: true) }
Declaration
Swift
public func lastIndex(of elementType: Element.Type) -> Int?
Parameters
elementType
An element type to search for in the collection.
Return Value
The last index where
element
is found. Ifelement
is not found in the collection, returnsnil
. -
Returns a boolean value indicating whether the sequence contains an element that exists in the given parameter.
let navigationController = UINavigationController() if navigationController.viewControllers.contains(any: [SearchViewController.self, HomeViewController.self]) { _ = navigationController?.popToRootViewController(animated: true) }
Declaration
Swift
public func contains(any elementTypes: [Element.Type]) -> Bool
Parameters
any
An array of element types to search for in the collection.
Return Value
true
if the sequence contains an element; otherwise,false
.
-
Sorts the collection in place, using the given preferred order as the comparison between elements.
let preferredOrder = ["Z", "A", "B", "C", "D"] var alphabets = ["D", "C", "B", "A", "Z", "W"] alphabets.sort(by: preferredOrder) print(alphabets) // Prints ["Z", "A", "B", "C", "D", "W"]
Declaration
Swift
public mutating func sort(by preferredOrder: `Self`)
Parameters
preferredOrder
The ordered elements, which will be used to sort the sequence’s elements.
-
Returns the elements of the sequence, sorted using the given preferred order as the comparison between elements.
let preferredOrder = ["Z", "A", "B", "C", "D"] let alphabets = ["D", "C", "B", "A", "Z", "W"] let sorted = alphabets.sorted(by: preferredOrder) print(sorted) // Prints ["Z", "A", "B", "C", "D", "W"]
Declaration
Swift
public func sorted(by preferredOrder: `Self`) -> Array<Element>
Parameters
preferredOrder
The ordered elements, which will be used to sort the sequence’s elements.
Return Value
A sorted array of the sequence’s elements.
-
Return an array containing all corresponding
rawValue
s ofself
.Declaration
Swift
public var rawValues: [Element.RawValue] { get }
-
是否统一
Declaration
Swift
public mutating func uniqueInPlace()
-
Undocumented
Declaration
Swift
public mutating func uniqueInPlace<T>(_ uniqueProperty: (Element) -> T) where T : Hashable
-
deep copy
Declaration
Swift
func deepCopy() -> [Element]
Return Value
return [Element]


Category:
General
Usage:
--help
Description:
--help displays list of all commands
Use "--help command" for specific help for that command
View the commands for Amuse-ic.
General
--help
--help displays list of all commands
Use "--help command" for specific help for that command
General
--hi, --hello
Tired of getting no DMs? Well, atleast the bot will greet you 🙂.
Music
--join, --j
Once the bot has joined your vc, try the cool music player functions
Music
--disconnect, --dc, --leave
Done listening? Kick me out of the voice channel (Everyone does 😢)
Music
--pause
Wanna come back in a while? Pause the player.
Music
--resume
Have some work? SoundBox is eagerly waiting for you to resume
Music
--stop
Done with the jam session? Stop the songs
PS: If leaving, disconnect the bot using --disconnect. Would help in reducing load on our servers.
Music
--play <argument>, --p <argument>
--p <song name>
--p <spotify_url>
--p <youtbe url>
Use this command to play a song, or spotify playlist.
If song is already playing this command queues the next song
Music
--n, --next
Music
--previous, --prev
Music
--skip
Don't like the song? But not as much as to delete it. Lemme hide it from queue.
Music
--jump <song number>
Jump to your favourite song.
Music
For looping track: --loop,
For looping queue: --loop queue
And I keep hitting repeat-peat-peat-peat-peat-peat! 🎶
Play your jams on loop
Music
--np
Like the song? Wanna know its name? Use this command.
Music
--q, --queue
See the upcoming songs! Navigate using reactions provided
Music Playlist
--load <playlist name>
Load your own saved playlist
Music Playlist
--save <playlist name>
Listen to this playlist often? Save the queue so as to load in just one command.
PS: Max 5 playlists can be saved
Music Playlists
--playlists
Displays all the saved playlists which can be added to queue directly by using "--load <playlist name>"
Music Playlist
--delete <playlist name>
Delete the playlists you grew out of!
Music
--remove <song number>
Remove the songs you don't wanna listen from the queue
Music
--clear, --clr
Annoying friends added annoying songs? Don't worry, we all got such friends. Lemme clear the queue for you.
Music
--shuffle
Make the party more exciting, Shuffle your jams
Music Playlist
--display <playlist name>
See the saved songs in your Favourite playlists
Music
--lyrics
Wanna sing along?? Here are the lyrics!
General
--joke
Some tickling for your tummy 😉
General
--truth
Get ready for some fun! Bring your gang and lets get the party started with these spicy truth questions. 😉
General
--dare
Get ready for some fun! Bring your gang and lets get the party started with these spicy Dares. 😉


In order to take part in the DD track, you need to be a registered participant of TREC. The TREC Call for
Participation, at
http://trec.nist.gov/pubs/call2017.html, includes
instructions on how to register.
The datasets and relevance judgments will be made generally available to non-participants after the TREC
2017 cycle, in February 2018. So register to participate if you want early access.
The TREC DD track provides interesting and understudied domains of documents. In 2017, we provides two
datasets, Ebola and New York Times, from different domains.
The Ebola dataset contains webpages, tweets and
other records related to the Ebola outbreak in Africa from 2014 to 2015. Documents in this dataset are
crawled from internet and most of them are in html format.
The New York Times dataset contains articles published in New York Times from 1987 to 2007.
Documents in this dataset are manually organized and annotated. All the documents in this dataset are stored
in
NITF.
Please check
Datasets page for more details.
Within each domain, there will be 25-50 topics that represent user search needs.
The topics have been developed by the NIST assessors in a period of three weeks.
A topic (which is like a query) contains a few words. It is the main
search target for one complete run of dynamic search. Each topic contains multiple subtopics, each of which
addresses one aspect of the topic. The NIST assessors have tried (very hard to) produce a complete set of
subtopics for each topic, and so we will treat them as the complete set and use them in the interactions and
evaluation.
An example topic from the 2015 Illicit Goods domain topic set may be found
here. It is about "paying for amazon book reviews" and contains
2 subtopics.
The topics will be made available from the
Tracks page
in the TREC Active Participants area. You cannot access this page without registering for TREC. If you
lose your active participants password, you will need to contact
<EMAIL_ADDRESS>The topics file contains not only the queries but in fact the full ground truth data: subtopics, relevant
documents, and highlighted passages.
DO NOT READ THE FILE. The file should be used only as input to
the jig, and your system receives the truth data via the jig. If you examine the topics file, your run
may
not be labeled automatic but rather is a manual run.
When your "run" starts, your system will communicate with the jig via a simple API. Your system indicates
that it is ready for a new query, and the jig will give you a query along with its domain label. Your system
can use that query to search the domain collection and return up to five documents to the jig. The jig will
reply with relevance information for any of those retrieved documents that have been judged.
Your systems will receive an initial query for each topic, where the query is two to four words and
additionally indicates the domain by a number 1, 2, 3 or 4. In response to that query, systems may return up
to five documents to the user. The jig (acting as a simulated user) will respond by indicating which of the
retrieved documents are relevant to their interests in the topic, and to which subtopic the document is
relevant to. Additionally, the simulated user will identify passages from the relevant documents and assign
the passages to the subtopics with a graded relevance rating. The system may then return another five
documents for more feedback. Systems should stop until they believe they have covered all the user's
subtopics sufficiently.
The subtopics are not known to your system in advance; systems must discover the subtopics from the user's
responses.
The jig only gives relevance information when it exists. If the jig gives no information about a document
your system retrieved, it does not mean that the document is not relevant, it means that the user hasn't
examined it. Your system should assume this partial relevance situation,
NOT the traditional TREC
interpretation that unjudged documents are not relevant.
The following picture illustrates the task:
The system's interactions with the user can be simulated by a jig that the track coordinators provide. This
jig runs on Linux, Mac OS, and Windows. You will need the
topics with ground truth to make the jig work, and
your system may only interact with the ground truth through the jig that we provide.
You can find the jig program
here.
The measurements of runs are Cube Test, sDCG and Expected Utility. Scoring scripts are included in the jig.
other diagnostic measures such as precision and recall may also be reported.
Cube Test is a search effectiveness measurement evaluating the speed of gaining relevant information (could
be documents or passages) in a dynamic search process. It measures the amount of relevant information a
system could gather and the time needed in the entire search process. The higher the Cube Test score, the
better the IR system.
sDCG extends the classic DCG to a search session which consists of multiple iterations. The relevance scores
of results that are ranked lower or returned in later iterations get more discounts. The discounted cumulative
relevance score is the final results of this metric.
Expected Utility scores different runs by measuring the relevant information a system found and the length
of documents. The relevance scores of documents are discounted based on ranking order and novelty. The document
length is discounted only based on ranking position. The difference between the cumulative relevance score and
the aggregated document length is the final score of each run.
References:
Jiyun Luo, Christopher Wing, Hui Yang, and Marti Hearst. 2013.
The water lling model and the cube
test: multi-dimensional evaluation for professional search. In Proceedings of the 22nd ACM international
conference on Information & Knowledge Management. ACM, 709-714.
Kalervo Järvelin, Susan L Price, Lois ML Delcambre, and Marianne Lykke Nielsen. 2008.
Discounted cumulated gain based
evaluation of multiple-query IR sessions. In European Conference on Information Retrieval. Springer, 4-15.
Yiming Yang and Abhimanyu Lad. 2009.
Modeling expected utility of
multi-session information distillation. In Conference on the Theory of Information Retrieval. Springer,
164-175.
In TREC, a "run" is the output of a search system over all topics. In the DD track, the runs are the output
of the harness jig. Participating groups typically submit more than one run corresponding to different
parameter settings or algorithmic choices. The maximum number of runs allowed for DD-2017 is
five
from each team.
We use a line-oriented format similar to the classic TREC submission format:
topic_id docno ranking_score on_topic subtopic_rels
where 'on_topic' is 1 or 0 if the document is relevant to any subtopic, and the subtopic_rels indicate
graded relevance for the document for all relevant subtopics. For instance:
topic_id docno ranking_score on_topic subtopic_rels
DD15-1<PHONE_NUMBER>-d6783cba6ad386f4444dcc2679637e0b 883.000000 1 DD15-1.1:3|DD15-1.4:2|DD15-1.4:2|DD15-1.4:2|DD15-1.4:2|DD15-1.4:2|DD15-1.2:2|DD15-1.2:2
DD15-1<PHONE_NUMBER>-f67659162ce908cc510881a6b6eabc8b 564.000000 1 DD15-1.1:3
DD15-1<PHONE_NUMBER>-f9c69177db43b0f810ce03c822576c5c 177.000000 1 DD15-1.1:3
DD15-1<PHONE_NUMBER>-e8c92486dc3462e4a352c4fd41d3a723 66.000000 0
DD15-1<PHONE_NUMBER>-d9ad76f0947e2acd79cba3acd5f449f7 25.000000 1 DD15-1.3:2|DD15-1.1:2
Participants are expected to submit at least one run by the deadline.
Runs may be fully automatic, or manual. Manual indicates intervention by a person at any stage of the
retrieval. We welcome unusual approaches to the task including human-in-the-loop searching, as this helps us
set upper performance bounds.


| nc_close {pbdNCDF4} | R Documentation |
Closes an open netCDF file, which flushes any unwritten data to disk. Always close a netCDF file when you are done with it! You are risking data loss otherwise.
nc_close( nc )
nc |
An object of class |
Data written to a netCDF file is cached in memory, for better performance. This data is only written out to disk when the file is closed. Therefore, always remember to close a netCDF file when done with it.
David W. Pierce<EMAIL_ADDRESS>http://dwpierce.com/software
## Not run: nc <- nc_open("salinity.nc") ## Not run: data <- ncvar_get( nc ) # Read the "only" var in the file ## Not run: nc_close(nc)


The requested URL /html/stylexpo/stx001/highlight.js was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.


New York marathon jumpstarts 50th anniversary party
NEW YORK, Nov 3 — As thousands of runners cross the finish line inside leafy Central Park today, the race will just be starting for the organisers of the New York City Marathon, as they begin a year-long celebration of a half century of running in 2020.
A early “50 for the 50th” drawing for amateur runners opens on race day and will see the first 50 participants selected for the New York City Marathon’s golden anniversary next year, long before the general application opens in January.
The drawing is the first of several events planned to mark the occasion, Michael Capiraso, president and CEO of New York Road Runners (NYRR), told Reuters.
“I think there are more people interested in running a marathon now than there ever have been,” said Capiraso. “From a standpoint of participation and demand, it’s never been stronger certainly for us here in New York.”
The sport has expanded rapidly since the annual race first began with just 127 participants, running the entire marathon inside Central Park. Last year, 52,813 runners completed the course across all five of the city’s boroughs.
“When we first started this thing, who ever thought?
The 49th edition of the New York City Marathon begins today. — Reuters


See class {@link nl.esi.metis.aisparser.AISParser AISParser} for more information on how to use this package.
See the ESI AIS Parser License for more information on the legal aspects.
The parser was used in the Poseidon project, and is improved in the Metis project to better handle uncertain information. Both projects were led by the Embedded Systems Institute. In both projects Thales Nederlands was the carrying industrial partner, and multiple Dutch universities participated.


Home
Projet
About
Content on this page requires a newer version of Adobe Flash Player.
Info
Code
Move Player 1
Move Player 2
Download et Source Code
View on GitHub


Over-range protection shall be provided for pressure instruments, pilots, gauges, etc. that may be subject to pressures that could damage or change the calibration of the instrument.
Instruments shall be equipped with pulsation dampeners when required by process conditions (e.g. pulsating service), capable of being adjusted while instruments are pressurized.
All pressure instruments connections shall be installed with a block and bleed valve assembly.
This assembly complements the process isolation valve (block, block & bleed or double block & bleed) installed by Piping discipline (refer to GS EP PVV 102).
It shall be of AISI 316 or 316L stainless steel material at the minimum, including the trim.
Where capillaries are not used, differential pressure transmitters shall be provided with a 316 or 316L stainless steel close coupled 5-valve manifold.
This requirement also applies to differential pressure transmitters used in flow or level measurement applications.