Class: Google::Apis::GenomicsV2alpha1::CheckInRequest
- Inherits:
- 
      Object
      
        - Object
- Google::Apis::GenomicsV2alpha1::CheckInRequest
 
- Includes:
- Core::Hashable, Core::JsonObjectSupport
- Defined in:
- generated/google/apis/genomics_v2alpha1/classes.rb,
 generated/google/apis/genomics_v2alpha1/representations.rb,
 generated/google/apis/genomics_v2alpha1/representations.rb
Overview
The parameters to the CheckIn method.
Instance Attribute Summary collapse
- 
  
    
      #deadline_expired  ⇒ Google::Apis::GenomicsV2alpha1::Empty 
    
    
  
  
  
  
    
    
  
  
  
  
  
  
    A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. 
- 
  
    
      #event  ⇒ Hash<String,Object> 
    
    
  
  
  
  
    
    
  
  
  
  
  
  
    A workflow specific event occurred. 
- 
  
    
      #result  ⇒ Google::Apis::GenomicsV2alpha1::Status 
    
    
  
  
  
  
    
    
  
  
  
  
  
  
    The Statustype defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs.
Instance Method Summary collapse
- 
  
    
      #initialize(**args)  ⇒ CheckInRequest 
    
    
  
  
  
    constructor
  
  
  
  
  
  
  
    A new instance of CheckInRequest. 
- 
  
    
      #update!(**args)  ⇒ Object 
    
    
  
  
  
  
  
  
  
  
  
    Update properties of this object. 
Methods included from Core::JsonObjectSupport
Methods included from Core::Hashable
Constructor Details
#initialize(**args) ⇒ CheckInRequest
Returns a new instance of CheckInRequest
| 249 250 251 | # File 'generated/google/apis/genomics_v2alpha1/classes.rb', line 249 def initialize(**args) update!(**args) end | 
Instance Attribute Details
#deadline_expired ⇒ Google::Apis::GenomicsV2alpha1::Empty
A generic empty message that you can re-use to avoid defining duplicated
empty messages in your APIs. A typical example is to use it as the request
or the response type of an API method. For instance:
service Foo 
rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty);
The JSON representation for Empty is empty JSON object ```.
Corresponds to the JSON propertydeadlineExpired`
| 199 200 201 | # File 'generated/google/apis/genomics_v2alpha1/classes.rb', line 199 def deadline_expired @deadline_expired end | 
#event ⇒ Hash<String,Object>
A workflow specific event occurred.
Corresponds to the JSON property event
| 204 205 206 | # File 'generated/google/apis/genomics_v2alpha1/classes.rb', line 204 def event @event end | 
#result ⇒ Google::Apis::GenomicsV2alpha1::Status
The Status type defines a logical error model that is suitable for different
programming environments, including REST APIs and RPC APIs. It is used by
gRPC. The error model is designed to be:
- Simple to use and understand for most users
- Flexible enough to meet unexpected needs
# Overview
The Statusmessage contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers understand and resolve the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the packagegoogle.rpcthat can be used for common error conditions. # Language mapping TheStatusmessage is the logical representation of the error model, but it is not necessarily the actual wire format. When theStatusmessage is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C. # Other uses The error model and theStatusmessage can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments. Example uses of this error model include:
- Partial errors. If a service needs to return partial errors to the client,
it may embed the Statusin the normal response to indicate the partial errors.
- Workflow errors. A typical workflow has multiple steps. Each step may
have a Statusmessage for error reporting.
- Batch operations. If a client uses batch request and batch response, the
Statusmessage should be used directly inside batch response, one for each error sub-response.
- Asynchronous operations. If an API call embeds asynchronous operation
results in its response, the status of those operations should be
represented directly using the Statusmessage.
- Logging. If some API errors are stored in logs, the message Statuscould be used directly after any stripping needed for security/privacy reasons. Corresponds to the JSON propertyresult
| 247 248 249 | # File 'generated/google/apis/genomics_v2alpha1/classes.rb', line 247 def result @result end | 
Instance Method Details
#update!(**args) ⇒ Object
Update properties of this object
| 254 255 256 257 258 | # File 'generated/google/apis/genomics_v2alpha1/classes.rb', line 254 def update!(**args) @deadline_expired = args[:deadline_expired] if args.key?(:deadline_expired) @event = args[:event] if args.key?(:event) @result = args[:result] if args.key?(:result) end |