# Cloud Tool Results API . projects . histories . executions . steps . thumbnails

## Instance Methods

Lists thumbnails of images attached to a step.

Retrieves the next page of results.

### Method Details

`list(projectId=None, historyId=None, executionId=None, stepId=None, pageSize=None, pageToken=None)`

    Lists thumbnails of images attached to a step.

    May return any of the following canonical error codes: - PERMISSION_DENIED - if the user is not authorized to read from the project, or from any of the images - INVALID_ARGUMENT - if the request is malformed - NOT_FOUND - if the step does not exist, or if any of the images do not exist

    Args:
      projectId: string, A Project id.

    Required. (required)
      historyId: string, A History id.

    Required. (required)
      executionId: string, An Execution id.

    Required. (required)
      stepId: string, A Step id.

    Required. (required)
      pageSize: integer, The maximum number of thumbnails to fetch.

    Default value: 50. The server will use this default if the field is not set or has a value of 0.

    Optional.
      pageToken: string, A continuation token to resume the query at the next item.

    Optional.

    Returns:
      An object of the form:

        { # A response containing the thumbnails in a step.
        "nextPageToken": "A String", # A continuation token to resume the query at the next item.
            #
            # If set, indicates that there are more thumbnails to read, by calling list again with this value in the page_token field.
        "thumbnails": [ # A list of image data.
            #
            # Images are returned in a deterministic order; they are ordered by these factors, in order of importance: * First, by their associated test case. Images without a test case are considered greater than images with one. * Second, by their creation time. Images without a creation time are greater than images with one. * Third, by the order in which they were added to the step (by calls to CreateStep or UpdateStep).
          { # An image, with a link to the main image and a thumbnail.
            "thumbnail": { # A single thumbnail, with its size and format. # The thumbnail.
              "data": "A String", # The thumbnail file itself.
                  #
                  # That is, the bytes here are precisely the bytes that make up the thumbnail file; they can be served as an image as-is (with the appropriate content type.)
                  #
                  # Always set.
              "widthPx": 42, # The width of the thumbnail, in pixels.
                  #
                  # Always set.
              "contentType": "A String", # The thumbnail's content type, i.e. "image/png".
                  #
                  # Always set.
              "heightPx": 42, # The height of the thumbnail, in pixels.
                  #
                  # Always set.
            },
            "stepId": "A String", # The step to which the image is attached.
                #
                # Always set.
            "sourceImage": { # A reference to a ToolExecution output file. # A reference to the full-size, original image.
                #
                # This is the same as the tool_outputs entry for the image under its Step.
                #
                # Always set.
              "testCase": { # A reference to a test case. # The test case to which this output file belongs.
                  #
                  # - In response: present if set by create/update request - In create/update request: optional
                  #
                  # Test case references are canonically ordered lexicographically by these three factors: * First, by test_suite_name. * Second, by class_name. * Third, by name.
                "className": "A String", # The name of the class.
                "testSuiteName": "A String", # The name of the test suite to which this test case belongs.
                "name": "A String", # The name of the test case.
                    #
                    # Required.
              },
              "output": { # A reference to a file. # A FileReference to an output file.
                  #
                  # - In response: always set - In create/update request: always set
                "fileUri": "A String", # The URI of a file stored in Google Cloud Storage.
                    #
                    # For example: http://storage.googleapis.com/mybucket/path/to/test.xml or in gsutil format: gs://mybucket/path/to/test.xml with version-specific info, gs://mybucket/path/to/test.xml#1360383693690000
                    #
                    # An INVALID_ARGUMENT error will be returned if the URI format is not supported.
                    #
                    # - In response: always set - In create/update request: always set
              },
              "creationTime": { # A Timestamp represents a point in time independent of any time zone or calendar, represented as seconds and fractions of seconds at nanosecond resolution in UTC Epoch time. It is encoded using the Proleptic Gregorian Calendar which extends the Gregorian calendar backwards to year one. It is encoded assuming all minutes are 60 seconds long, i.e. leap seconds are "smeared" so that no leap second table is needed for interpretation. Range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings. See [https://www.ietf.org/rfc/rfc3339.txt](https://www.ietf.org/rfc/rfc3339.txt). # The creation time of the file.
                  #
                  # - In response: present if set by create/update request - In create/update request: optional
                  #
                  # Example 1: Compute Timestamp from POSIX `time()`.
                  #
                  # Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0);
                  #
                  # Example 2: Compute Timestamp from POSIX `gettimeofday()`.
                  #
                  # struct timeval tv; gettimeofday(&tv, NULL);
                  #
                  # Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000);
                  #
                  # Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`.
                  #
                  # FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
                  #
                  # // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
                  #
                  # Example 4: Compute Timestamp from Java `System.currentTimeMillis()`.
                  #
                  # long millis = System.currentTimeMillis();
                  #
                  # Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build();
                  #
                  #
                  #
                  # Example 5: Compute Timestamp from current time in Python.
                  #
                  # timestamp = Timestamp() timestamp.GetCurrentTime()
                "nanos": 42, # Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive.
                "seconds": "A String", # Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive.
              },
            },
            "error": { # 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](https://github.com/grpc). The error model is designed to be: # An error explaining why the thumbnail could not be rendered.
                #
                # - Simple to use and understand for most users - Flexible enough to meet unexpected needs
                #
                # # Overview
                #
                # The `Status` message 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 package `google.rpc` which can be used for common error conditions.
                #
                # # Language mapping
                #
                # The `Status` message is the logical representation of the error model, but it is not necessarily the actual wire format. When the `Status` message 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 the `Status` message 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 `Status` in the normal response to indicate the partial errors.
                #
                # - Workflow errors. A typical workflow has multiple steps. Each step may have a `Status` message for error reporting purpose.
                #
                # - Batch operations. If a client uses batch request and batch response, the `Status` message 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 `Status` message.
                #
                # - Logging. If some API errors are stored in logs, the message `Status` could be used directly after any stripping needed for security/privacy reasons.
              "message": "A String", # A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][] field, or localized by the client.
              "code": 42, # The status code, which should be an enum value of [google.rpc.Code][].
              "details": [ # A list of messages that carry the error details. There will be a common set of message types for APIs to use.
                { # `Any` contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message.
                    #
                    # Protobuf library provides support to pack/unpack Any values in the form of utility functions or additional generated methods of the Any type.
                    #
                    # Example 1: Pack and unpack a message in C++.
                    #
                    # Foo foo = ...; Any any; any.PackFrom(foo); ... if (any.UnpackTo(&foo)) { ... }
                    #
                    # Example 2: Pack and unpack a message in Java.
                    #
                    # Foo foo = ...; Any any = Any.pack(foo); ... if (any.is(Foo.class)) { foo = any.unpack(Foo.class); }
                    #
                    # Example 3: Pack and unpack a message in Python.
                    #
                    # foo = Foo(...) any = Any() any.Pack(foo) ... if any.Is(Foo.DESCRIPTOR): any.Unpack(foo) ...
                    #
                    # The pack methods provided by protobuf library will by default use 'type.googleapis.com/full.type.name' as the type URL and the unpack methods only use the fully qualified type name after the last '/' in the type URL, for example "foo.bar.com/x/y.z" will yield type name "y.z".
                    #
                    #
                    #
                    # JSON ==== The JSON representation of an `Any` value uses the regular representation of the deserialized, embedded message, with an additional field `@type` which contains the type URL. Example:
                    #
                    # package google.profile; message Person { string first_name = 1; string last_name = 2; }
                    #
                    # { "@type": "type.googleapis.com/google.profile.Person", "firstName": , "lastName":  }
                    #
                    # If the embedded message type is well-known and has a custom JSON representation, that representation will be embedded adding a field `value` which holds the custom JSON in addition to the `@type` field. Example (for message [google.protobuf.Duration][]):
                    #
                    # { "@type": "type.googleapis.com/google.protobuf.Duration", "value": "1.212s" }
                  "typeUrl": "A String", # A URL/resource name whose content describes the type of the serialized protocol buffer message.
                      #
                      # For URLs which use the scheme `http`, `https`, or no scheme, the following restrictions and interpretations apply:
                      #
                      # * If no scheme is provided, `https` is assumed. * The last segment of the URL's path must represent the fully qualified name of the type (as in `path/google.protobuf.Duration`). The name should be in a canonical form (e.g., leading "." is not accepted). * An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
                      #
                      # Schemes other than `http`, `https` (or the empty scheme) might be used with implementation specific semantics.
                  "value": "A String", # Must be a valid serialized protocol buffer of the above specified type.
                },
              ],
            },
          },
        ],
      }

`list_next(previous_request, previous_response)`

    Retrieves the next page of results.

    Args:
      previous_request: The request for the previous page. (required)
      previous_response: The response from the request for the previous page. (required)

    Returns:
      A request object that you can call 'execute()' on to request the next
      page. Returns None if there are no more items in the collection.