Skip to content

Commit 56c63d2

Browse files
feat(api): manual updates (#38)
1 parent 73b681c commit 56c63d2

File tree

9 files changed

+169
-1221
lines changed

9 files changed

+169
-1221
lines changed

.stats.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,2 @@
11
configured_endpoints: 111
2-
openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/gitpod%2Fgitpod-064a191bc556bcab46bb5d612c844437e1a4aef5981a4a99ab7f825a96ede4fa.yml
2+
openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/gitpod%2Fgitpod-3655d5ad0ac3e228c1519af70dbf3d0bfa3c47a2d06d4cac92a650da051b49a6.yml

src/resources/environments/automations/services.ts

+1-88
Original file line numberDiff line numberDiff line change
@@ -268,94 +268,7 @@ export interface Service {
268268

269269
export interface ServiceMetadata {
270270
/**
271-
* A Timestamp represents a point in time independent of any time zone or local
272-
* calendar, encoded as a count of seconds and fractions of seconds at nanosecond
273-
* resolution. The count is relative to an epoch at UTC midnight on January 1,
274-
* 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar
275-
* backwards to year one.
276-
*
277-
* All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap
278-
* second table is needed for interpretation, using a
279-
* [24-hour linear smear](https://developers.google.com/time/smear).
280-
*
281-
* The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By
282-
* restricting to that range, we ensure that we can convert to and from
283-
* [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) date strings.
284-
*
285-
* # Examples
286-
*
287-
* Example 1: Compute Timestamp from POSIX `time()`.
288-
*
289-
* Timestamp timestamp;
290-
* timestamp.set_seconds(time(NULL));
291-
* timestamp.set_nanos(0);
292-
*
293-
* Example 2: Compute Timestamp from POSIX `gettimeofday()`.
294-
*
295-
* struct timeval tv;
296-
* gettimeofday(&tv, NULL);
297-
*
298-
* Timestamp timestamp;
299-
* timestamp.set_seconds(tv.tv_sec);
300-
* timestamp.set_nanos(tv.tv_usec * 1000);
301-
*
302-
* Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`.
303-
*
304-
* FILETIME ft;
305-
* GetSystemTimeAsFileTime(&ft);
306-
* UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
307-
*
308-
* // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z
309-
* // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z.
310-
* Timestamp timestamp;
311-
* timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL));
312-
* timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
313-
*
314-
* Example 4: Compute Timestamp from Java `System.currentTimeMillis()`.
315-
*
316-
* long millis = System.currentTimeMillis();
317-
*
318-
* Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000)
319-
* .setNanos((int) ((millis % 1000) * 1000000)).build();
320-
*
321-
* Example 5: Compute Timestamp from Java `Instant.now()`.
322-
*
323-
* Instant now = Instant.now();
324-
*
325-
* Timestamp timestamp =
326-
* Timestamp.newBuilder().setSeconds(now.getEpochSecond())
327-
* .setNanos(now.getNano()).build();
328-
*
329-
* Example 6: Compute Timestamp from current time in Python.
330-
*
331-
* timestamp = Timestamp()
332-
* timestamp.GetCurrentTime()
333-
*
334-
* # JSON Mapping
335-
*
336-
* In JSON format, the Timestamp type is encoded as a string in the
337-
* [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is
338-
* "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always
339-
* expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are
340-
* zero-padded to two digits each. The fractional seconds, which can go up to 9
341-
* digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix
342-
* indicates the timezone ("UTC"); the timezone is required. A proto3 JSON
343-
* serializer should always use UTC (as indicated by "Z") when printing the
344-
* Timestamp type and a proto3 JSON parser should be able to accept both UTC and
345-
* other timezones (as indicated by an offset).
346-
*
347-
* For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on
348-
* January 15, 2017.
349-
*
350-
* In JavaScript, one can convert a Date object to this format using the standard
351-
* [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString)
352-
* method. In Python, a standard `datetime.datetime` object can be converted to
353-
* this format using
354-
* [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the
355-
* time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the
356-
* Joda Time's
357-
* [`ISODateTimeFormat.dateTime()`](<http://joda-time.sourceforge.net/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime()>)
358-
* to obtain a formatter capable of generating timestamps in this format.
271+
* created_at is the time the service was created.
359272
*/
360273
createdAt?: string;
361274

0 commit comments

Comments
 (0)