All workflows

Workflow runs

• fix: stop deserializing the staged agent from Cloud Storage during Agent Engine deployment

  completed successfully:
  Run mypy#7433:Pull request#7241synchronizebycopybara-service[bot]Bot
  copybara_1004920613

  Oct 22, 202625m 4s
  More actions for workflow run 7433

• fix: stop deserializing the staged agent from Cloud Storage during Agent Engine deployment

  completed successfully:
  Google GitHub Admin: Actions Workflow Security Scan#5875:Pull request#7241synchronizebycopybara-service[bot]Bot
  copybara_1004920613

  Oct 22, 202624m 56s
  More actions for workflow run 5875

• fix: stop deserializing the staged agent from Cloud Storage during Agent Engine deployment

  skipped:
  Enforce Multiple Approvals for Major Releases#1886:Pull request#7241synchronizebycopybara-service[bot]Bot
  copybara_1004920613

  Oct 22, 20269s
  More actions for workflow run 1886

• PR #7241

  completed successfully:
  CodeQL#33633:bycopybara-service[bot]Bot
  refs/pull/7241/head

  Oct 22, 202626m 0s

• Push on copybara_1004920613

  completed successfully:
  CodeQL#33632:bycopybara-service[bot]Bot
  copybara_1004920613

  Oct 22, 202631m 50s
  More actions for workflow run 33632

• fix: Correct the URL scheme and port used on the psc_endpoint branch in Sandboxes.send_command and Sandboxes.generate_browser_ws_headers. The branch added in cl/981254234 built https://{psc_endpoint} and defaulted to port 443, but PSC endpoints for VPC-SC sandboxes route directly to the sandbox router pod, which serves plain HTTP on the caller-supplied port (default 8080) and does not terminate TLS on 443. As a result every VPC-SC data-plane call through the SDK hung on ConnectTimeout at HTTPSConnectionPool(host='<psc-ip>', port=443). The endpoint is now built as http://{psc_endpoint}:{port} for send_command and ws://{psc_endpoint}:{port} for generate_browser_ws_headers, so the URL matches what the router serves. Non-VPC-SC callers (load_balancer_hostname / load_balancer_ip branches) are unaffected.

  skipped:
  Enforce Multiple Approvals for Major Releases#1885:Pull request#7236synchronizebycopybara-service[bot]Bot
  copybara_983303249

  Oct 22, 20261s
  More actions for workflow run 1885

• fix: Correct the URL scheme and port used on the psc_endpoint branch in Sandboxes.send_command and Sandboxes.generate_browser_ws_headers. The branch added in cl/981254234 built https://{psc_endpoint} and defaulted to port 443, but PSC endpoints for VPC-SC sandboxes route directly to the sandbox router pod, which serves plain HTTP on the caller-supplied port (default 8080) and does not terminate TLS on 443. As a result every VPC-SC data-plane call through the SDK hung on ConnectTimeout at HTTPSConnectionPool(host='<psc-ip>', port=443). The endpoint is now built as http://{psc_endpoint}:{port} for send_command and ws://{psc_endpoint}:{port} for generate_browser_ws_headers, so the URL matches what the router serves. Non-VPC-SC callers (load_balancer_hostname / load_balancer_ip branches) are unaffected.

  completed successfully:
  Run mypy#7432:Pull request#7236synchronizebycopybara-service[bot]Bot
  copybara_983303249

  Oct 22, 202631m 10s
  More actions for workflow run 7432

• fix: Correct the URL scheme and port used on the psc_endpoint branch in Sandboxes.send_command and Sandboxes.generate_browser_ws_headers. The branch added in cl/981254234 built https://{psc_endpoint} and defaulted to port 443, but PSC endpoints for VPC-SC sandboxes route directly to the sandbox router pod, which serves plain HTTP on the caller-supplied port (default 8080) and does not terminate TLS on 443. As a result every VPC-SC data-plane call through the SDK hung on ConnectTimeout at HTTPSConnectionPool(host='<psc-ip>', port=443). The endpoint is now built as http://{psc_endpoint}:{port} for send_command and ws://{psc_endpoint}:{port} for generate_browser_ws_headers, so the URL matches what the router serves. Non-VPC-SC callers (load_balancer_hostname / load_balancer_ip branches) are unaffected.

  completed successfully:
  Google GitHub Admin: Actions Workflow Security Scan#5874:Pull request#7236synchronizebycopybara-service[bot]Bot
  copybara_983303249

  Oct 22, 202630m 46s
  More actions for workflow run 5874

• PR #7236

  completed successfully:
  CodeQL#33631:bycopybara-service[bot]Bot
  refs/pull/7236/head

  Oct 22, 202632m 39s

• Push on copybara_983303249

  completed successfully:
  CodeQL#33630:bycopybara-service[bot]Bot
  copybara_983303249

  Oct 22, 202639m 6s
  More actions for workflow run 33630

• fix: stop deserializing the staged agent from Cloud Storage during Agent Engine deployment

  completed successfully:
  Run mypy#7431:Pull request#7241openedbycopybara-service[bot]Bot
  copybara_1004920613

  Oct 22, 202620m 32s
  More actions for workflow run 7431

• fix: stop deserializing the staged agent from Cloud Storage during Agent Engine deployment

  skipped:
  Enforce Multiple Approvals for Major Releases#1884:Pull request#7241openedbycopybara-service[bot]Bot
  copybara_1004920613

  Oct 22, 20261s
  More actions for workflow run 1884

• fix: stop deserializing the staged agent from Cloud Storage during Agent Engine deployment

  completed successfully:
  Google GitHub Admin: Actions Workflow Security Scan#5873:Pull request#7241openedbycopybara-service[bot]Bot
  copybara_1004920613

  Oct 22, 202620m 21s
  More actions for workflow run 5873

• PR #7241

  completed successfully:
  CodeQL#33629:bycopybara-service[bot]Bot
  refs/pull/7241/head

  Oct 22, 202622m 15s

• Push on copybara_1004920613

  completed successfully:
  CodeQL#33628:bycopybara-service[bot]Bot
  copybara_1004920613

  Oct 22, 202631m 31s

• fix: use the job's project, location and credentials in preview PipelineJob submit and rerun

  requires action with the application:
  Google GitHub Admin: Actions Workflow Security Scan#5872:Pull request#7240openedbyabhishekacharya200
  abhishekacharya200:fix/preview-pipeline-job-project-location

  Oct 22, 2026Action required
  More actions for workflow run 5872

• fix: use the job's project, location and credentials in preview PipelineJob submit and rerun

  requires action with the application:
  Run mypy#7430:Pull request#7240openedbyabhishekacharya200
  abhishekacharya200:fix/preview-pipeline-job-project-location

  Oct 22, 2026Action required
  More actions for workflow run 7430

• fix: use the job's project, location and credentials in preview PipelineJob submit and rerun

  requires action with the application:
  Enforce Multiple Approvals for Major Releases#1883:Pull request#7240openedbyabhishekacharya200
  abhishekacharya200:fix/preview-pipeline-job-project-location

  Oct 22, 2026Action required
  More actions for workflow run 1883

• fix: Correct the URL scheme and port used on the psc_endpoint branch in Sandboxes.send_command and Sandboxes.generate_browser_ws_headers. The branch added in cl/981254234 built https://{psc_endpoint} and defaulted to port 443, but PSC endpoints for VPC-SC sandboxes route directly to the sandbox router pod, which serves plain HTTP on the caller-supplied port (default 8080) and does not terminate TLS on 443. As a result every VPC-SC data-plane call through the SDK hung on ConnectTimeout at HTTPSConnectionPool(host='<psc-ip>', port=443). The endpoint is now built as http://{psc_endpoint}:{port} for send_command and ws://{psc_endpoint}:{port} for generate_browser_ws_headers, so the URL matches what the router serves. Non-VPC-SC callers (load_balancer_hostname / load_balancer_ip branches) are unaffected.

  completed successfully:
  Run mypy#7429:Pull request#7236synchronizebycopybara-service[bot]Bot
  copybara_983303249

  Oct 22, 20261m 11s
  More actions for workflow run 7429

• fix: Correct the URL scheme and port used on the psc_endpoint branch in Sandboxes.send_command and Sandboxes.generate_browser_ws_headers. The branch added in cl/981254234 built https://{psc_endpoint} and defaulted to port 443, but PSC endpoints for VPC-SC sandboxes route directly to the sandbox router pod, which serves plain HTTP on the caller-supplied port (default 8080) and does not terminate TLS on 443. As a result every VPC-SC data-plane call through the SDK hung on ConnectTimeout at HTTPSConnectionPool(host='<psc-ip>', port=443). The endpoint is now built as http://{psc_endpoint}:{port} for send_command and ws://{psc_endpoint}:{port} for generate_browser_ws_headers, so the URL matches what the router serves. Non-VPC-SC callers (load_balancer_hostname / load_balancer_ip branches) are unaffected.

  completed successfully:
  Google GitHub Admin: Actions Workflow Security Scan#5871:Pull request#7236synchronizebycopybara-service[bot]Bot
  copybara_983303249

  Oct 22, 202640s
  More actions for workflow run 5871

• fix: Correct the URL scheme and port used on the psc_endpoint branch in Sandboxes.send_command and Sandboxes.generate_browser_ws_headers. The branch added in cl/981254234 built https://{psc_endpoint} and defaulted to port 443, but PSC endpoints for VPC-SC sandboxes route directly to the sandbox router pod, which serves plain HTTP on the caller-supplied port (default 8080) and does not terminate TLS on 443. As a result every VPC-SC data-plane call through the SDK hung on ConnectTimeout at HTTPSConnectionPool(host='<psc-ip>', port=443). The endpoint is now built as http://{psc_endpoint}:{port} for send_command and ws://{psc_endpoint}:{port} for generate_browser_ws_headers, so the URL matches what the router serves. Non-VPC-SC callers (load_balancer_hostname / load_balancer_ip branches) are unaffected.

  skipped:
  Enforce Multiple Approvals for Major Releases#1882:Pull request#7236synchronizebycopybara-service[bot]Bot
  copybara_983303249

  Oct 22, 20261s
  More actions for workflow run 1882

• PR #7236

  completed successfully:
  CodeQL#33627:bycopybara-service[bot]Bot
  refs/pull/7236/head

  Oct 22, 20261m 50s

• Push on copybara_983303249

  completed successfully:
  CodeQL#33626:bycopybara-service[bot]Bot
  copybara_983303249

  Oct 22, 202611m 28s

• fix: Correct the URL scheme and port used on the psc_endpoint branch in Sandboxes.send_command and Sandboxes.generate_browser_ws_headers. The branch added in cl/981254234 built https://{psc_endpoint} and defaulted to port 443, but PSC endpoints for VPC-SC sandboxes route directly to the sandbox router pod, which serves plain HTTP on the caller-supplied port (default 8080) and does not terminate TLS on 443. As a result every VPC-SC data-plane call through the SDK hung on ConnectTimeout at HTTPSConnectionPool(host='<psc-ip>', port=443). The endpoint is now built as http://{psc_endpoint}:{port} for send_command and ws://{psc_endpoint}:{port} for generate_browser_ws_headers, so the URL matches what the router serves. Non-VPC-SC callers (load_balancer_hostname / load_balancer_ip branches) are unaffected.

  completed successfully:
  Google GitHub Admin: Actions Workflow Security Scan#5870:Pull request#7236synchronizebycopybara-service[bot]Bot
  copybara_983303249

  Oct 22, 202644s
  More actions for workflow run 5870

• fix: Correct the URL scheme and port used on the psc_endpoint branch in Sandboxes.send_command and Sandboxes.generate_browser_ws_headers. The branch added in cl/981254234 built https://{psc_endpoint} and defaulted to port 443, but PSC endpoints for VPC-SC sandboxes route directly to the sandbox router pod, which serves plain HTTP on the caller-supplied port (default 8080) and does not terminate TLS on 443. As a result every VPC-SC data-plane call through the SDK hung on ConnectTimeout at HTTPSConnectionPool(host='<psc-ip>', port=443). The endpoint is now built as http://{psc_endpoint}:{port} for send_command and ws://{psc_endpoint}:{port} for generate_browser_ws_headers, so the URL matches what the router serves. Non-VPC-SC callers (load_balancer_hostname / load_balancer_ip branches) are unaffected.

  skipped:
  Enforce Multiple Approvals for Major Releases#1881:Pull request#7236synchronizebycopybara-service[bot]Bot
  copybara_983303249

  Oct 22, 20261s
  More actions for workflow run 1881