核心内容摘要
搜索AI的奥秘手抄报_探索AI搜索技术：揭秘手抄报中的智能奥秘
如何用JS实现关键词逐字动态显示且兼容IE11？
The event types are a controlled set, defined by Supervisor itself. There is no way to add an event type without changing itself. This is typically not a problem, though, because metadata is attached to events that can be used by event listeners as additional filter criterion, in conjunction with its type. Event types that may be subscribed to by event listeners are predefined by supervisor and fall into several major categories, including “process state change”, “process communication”, and “supervisor state change” events. Below are tables describing these event types. In the below list, we indicate that some event types have a “body” which is a a token set. A token set consists of a set of characters with space-separated tokens. Each token represents a key-value pair. The key and value are separated by a colon. For example: processname:cat groupname:cat from_state:STOPPED Token sets do not have a linefeed or carriage return character at their end. The base event type. This event type is abstract. It will never be sent directly. Subscribing to this event type will cause a subscriber to receive all event notifications emitted by Supervisor. Name: Subtype Of: N/A Body Description: N/A This process type indicates a process has moved from one state to another. See for a description of the states that a process moves through during its lifetime. This event type is abstract, it will never be sent directly. Subscribing to this event type will cause a subscriber to receive event notifications of all the event types that are subtypes of . Name: Subtype Of: Body Description All subtypes of have a body which is a token set. Additionally, each subtype’s token set has a default set of key/value pairs: , , and . represents the process name which supervisor knows this process as. represents the name of the supervisord group which this process is in. is the name of the state from which this process is transitioning (the new state is implied by the concrete event type). Concrete subtypes may include additional key/value pairs in the token set. Indicates a process has moved from a state to the STARTING state. Name: Subtype Of: Body Description This body is a token set. It has the default set of key/value pairs plus an additional key. represents the number of times this process has entered this state before transitioning to RUNNING or FATAL (it will never be larger than the “startretries” parameter of the process). For example: processname:cat groupname:cat from_state:STOPPED tries:0 Indicates a process has moved from the state to the state. This means that the process has successfully started as far as Supervisor is concerned. Name: Subtype Of: Body Description This body is a token set. It has the default set of key/value pairs plus an additional key. represents the UNIX process id of the process that was started. For example: processname:cat groupname:cat from_state:STARTING pid:2766 Indicates a process has moved from the state to the state. This means that the process did not successfully enter the RUNNING state, and Supervisor is going to try to restart it unless it has exceeded its “startretries” configuration limit. Name: Subtype Of: Body Description This body is a token set. It has the default set of key/value pairs plus an additional key. represents the number of times this process has entered this state before transitioning to or (it will never be larger than the “startretries” parameter of the process). For example: processname:cat groupname:cat from_state:STOPPED tries:0 Indicates a process has moved from either the state or the state to the state. Name: Subtype Of: Body Description This body is a token set. It has the default set of key/value pairs plus an additional key. represents the UNIX process id of the process that was started. For example: processname:cat groupname:cat from_state:STARTING pid:2766 Indicates a process has moved from the state to the state. Name: Subtype Of: Body Description This body is a token set. It has the default set of key/value pairs plus two additional keys: and . represents the UNIX process id of the process that exited. represents whether the process exited with an expected exit code or not. It will be if the exit code was unexpected, or if the exit code was expected. For example: processname:cat groupname:cat from_state:RUNNING expected:0 pid:2766 Indicates a process has moved from the state to the state. Name: Subtype Of: Body Description This body is a token set. It has the default set of key/value pairs plus an additional key. represents the UNIX process id of the process that was started. For example: processname:cat groupname:cat from_state:STOPPING pid:2766 Indicates a process has moved from the state to the state. This means that Supervisor tried number of times unsuccessfully to start the process, and gave up attempting to restart it. Name: Subtype Of: Body Description This event type is a token set with the default key/value pairs. For example: processname:cat groupname:cat from_state:BACKOFF Indicates a process has moved from any state to the state (indicates an error in ). This state transition will only happen if itself has a programming error. Name: Subtype Of: Body Description This event type is a token set with the default key/value pairs. For example: processname:cat groupname:cat from_state:BACKOFF An event type raised when the method is called on Supervisor’s RPC interface. The and are arguments of the RPC method. Name: Subtype Of: Body Description type:type data An event type emitted when a process writes to stdout or stderr. The event will only be emitted if the file descriptor is not in capture mode and if or config options are set to . This event type is abstract, it will never be sent directly. Subscribing to this event type will cause a subscriber to receive event notifications for all subtypes of . Name: Subtype Of: Body Description: N/A Indicates a process has written to its stdout file descriptor. The event will only be emitted if the file descriptor is not in capture mode and if the config option is set to . Name: Subtype Of: Body Description processname:name groupname:name pid:pid channel:stdout data Indicates a process has written to its stderr file descriptor. The event will only be emitted if the file descriptor is not in capture mode and if the config option is set to . Name: Subtype Of: Body Description processname:name groupname:name pid:pid channel:stderr data An event type raised when any process attempts to send information between and tags in its output. This event type is abstract, it will never be sent directly. Subscribing to this event type will cause a subscriber to receive event notifications for all subtypes of . Name: Subtype Of: Body Description: N/A Indicates a process has sent a message to Supervisor on its stdout file descriptor. Name: Subtype Of: Body Description processname:name groupname:name pid:pid data Indicates a process has sent a message to Supervisor on its stderr file descriptor. Name: Subtype Of: Body Description processname:name groupname:name pid:pid data An event type raised when the state of the process changes. This type is abstract, it will never be sent directly. Subscribing to this event type will cause a subscriber to receive event notifications of all the subtypes of . Name: Subtype Of: Body Description: N/A Indicates that has started. Name: Subtype Of: Body Description: Empty string Indicates that is stopping. Name: Subtype Of: Body Description: Empty string An event type that may be subscribed to for event listeners to receive “wake-up” notifications every N seconds. This event type is abstract, it will never be sent directly. Subscribing to this event type will cause a subscriber to receive event notifications for all subtypes of . Note that the only events available are the ones listed below. You cannot subscribe to an arbitrary interval. If you need an interval not provided below, you can subscribe to one of the shorter intervals given below and keep track of the time between runs in your event listener. Name: Subtype Of: Body Description: N/A An event type that may be subscribed to for event listeners to receive “wake-up” notifications every 5 seconds. Name: Subtype Of: Body Description This event type is a token set with a single key: “when”, which indicates the epoch time for which the tick was sent. when:1201063880 An event type that may be subscribed to for event listeners to receive “wake-up” notifications every 60 seconds. Name: Subtype Of: Body Description This event type is a token set with a single key: “when”, which indicates the epoch time for which the tick was sent. when:1201063880 An event type that may be subscribed to for event listeners to receive “wake-up” notifications every 3600 seconds (1 hour). Name: Subtype Of: Body Description This event type is a token set with a single key: “when”, which indicates the epoch time for which the tick was sent. when:1201063880 An event type raised when a process group is added to or removed from Supervisor. This type is abstract, it will never be sent directly. Subscribing to this event type will cause a subscriber to receive event notifications of all the subtypes of . Name: Subtype Of: Body Description: N/A Indicates that a process group has been added to Supervisor’s configuration. Name: Subtype Of: Body Description: This body is a token set with just a groupname key/value. groupname:cat Indicates that a process group has been removed from Supervisor’s configuration. Name: Subtype Of: Body Description: This body is a token set with just a groupname key/value. groupname:cat
