New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

@maxim_mazurok/gapi.client.cloudscheduler-v1beta1

Package Overview
Dependencies
Maintainers
1
Versions
81
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@maxim_mazurok/gapi.client.cloudscheduler-v1beta1 - npm Package Compare versions

Comparing version

to
0.0.20230816

11

index.d.ts

@@ -12,3 +12,3 @@ /* Type definitions for non-npm package Cloud Scheduler API v1beta1 0.0 */

// Generated from: https://cloudscheduler.googleapis.com/$discovery/rest?version=v1beta1
// Revision: 20230726
// Revision: 20230816

@@ -180,3 +180,4 @@ /// <reference types="gapi.client" />

* if the previous execution has not ended when its scheduled time occurs. If retry_count > 0 and a job attempt fails, the job will be tried a total of retry_count times, with
* exponential backoff, until the next scheduled start time.
* exponential backoff, until the next scheduled start time. If retry_count is 0, a job attempt will not be retried if it fails. Instead the Cloud Scheduler system will wait for the
* next scheduled execution time. Setting retry_count to 0 does not prevent failed jobs from running according to schedule after the failure.
*/

@@ -332,5 +333,5 @@ schedule?:

* The number of attempts that the system will make to run a job using the exponential backoff procedure described by max_doublings. The default value of retry_count is zero. If
* retry_count is zero, a job attempt will *not* be retried if it fails. Instead the Cloud Scheduler system will wait for the next scheduled execution time. If retry_count is set to a
* non-zero number then Cloud Scheduler will retry failed attempts, using exponential backoff, retry_count times, or until the next scheduled execution time, whichever comes first.
* Values greater than 5 and negative values are not allowed.
* retry_count is 0, a job attempt will not be retried if it fails. Instead the Cloud Scheduler system will wait for the next scheduled execution time. Setting retry_count to 0 does
* not prevent failed jobs from running according to schedule after the failure. If retry_count is set to a non-zero number then Cloud Scheduler will retry failed attempts, using
* exponential backoff, retry_count times, or until the next scheduled execution time, whichever comes first. Values greater than 5 and negative values are not allowed.
*/

@@ -337,0 +338,0 @@ retryCount?:

{
"name": "@maxim_mazurok/gapi.client.cloudscheduler-v1beta1",
"version": "0.0.20230726",
"version": "0.0.20230816",
"description": "TypeScript typings for Cloud Scheduler API v1beta1",

@@ -18,4 +18,4 @@ "license": "MIT",

"@types/gapi.client": "*",
"@types/gapi.client.discovery": "*"
"@types/gapi.client.discovery-v1": "*"
}
}

@@ -6,3 +6,3 @@ /* This is stub file for gapi.client.cloudscheduler-v1beta1 definition tests */

// Revision: 20230726
// Revision: 20230816

@@ -9,0 +9,0 @@ gapi.load('client', async () => {