Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: google/go-cloud
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.39.0
Choose a base ref
...
head repository: google/go-cloud
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.40.0
Choose a head ref
  • 15 commits
  • 331 files changed
  • 6 contributors

Commits on Aug 14, 2024

  1. all: postrelease (#3470)

    vangent authored Aug 14, 2024
    Configuration menu
    Copy the full SHA
    7a096fb View commit details
    Browse the repository at this point in the history

Commits on Aug 20, 2024

  1. Configuration menu
    Copy the full SHA
    54419b7 View commit details
    Browse the repository at this point in the history

Commits on Aug 21, 2024

  1. Configuration menu
    Copy the full SHA
    d2adbc5 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    bb796f8 View commit details
    Browse the repository at this point in the history

Commits on Aug 29, 2024

  1. s3blob: fix data race (#3480)

    w.pr cannot be used to indicate that the pipe has been closed. The problem with
    using w.pr is that a write to it in the goroutine launched by writer.open can
    race with a read on w.pr in Close.
    
    We just don't write to w.pr in writer.open. The read end of the pipe can still be
    closed twice, but that's fine.
    arjunnair1997 authored Aug 29, 2024
    Configuration menu
    Copy the full SHA
    2d0cce5 View commit details
    Browse the repository at this point in the history

Commits on Sep 6, 2024

  1. Configuration menu
    Copy the full SHA
    49a4d98 View commit details
    Browse the repository at this point in the history

Commits on Sep 9, 2024

  1. blob/azblob: Support AZURE_STORAGEBLOB_CONNECTIONSTRING as an alterna…

    …tive for AZURE_STORAGE_CONNECTION_STRING (#3483)
    vangent authored Sep 9, 2024
    Configuration menu
    Copy the full SHA
    8b41580 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    9af237b View commit details
    Browse the repository at this point in the history

Commits on Sep 11, 2024

  1. Configuration menu
    Copy the full SHA
    aeb964f View commit details
    Browse the repository at this point in the history

Commits on Sep 18, 2024

  1. Configuration menu
    Copy the full SHA
    e5b1bc6 View commit details
    Browse the repository at this point in the history

Commits on Oct 5, 2024

  1. Configuration menu
    Copy the full SHA
    2cb18bb View commit details
    Browse the repository at this point in the history

Commits on Oct 9, 2024

  1. Configuration menu
    Copy the full SHA
    bbdd0b3 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    af4c9dd View commit details
    Browse the repository at this point in the history

Commits on Oct 10, 2024

  1. aws: add rate_limiter_capacity to configure client-side rate limits

    Issuing many S3 uploads in quick succession causes the following
    error:
    
    operation error S3: PutObject, failed to get rate limit token, retry quota exceeded, 0 available, 5 requested
    
    By default, this rate limit is disabled to restore the same behavior
    as SDK v1. If `rate_limiter_capacity` is set, then client-side rate
    limits will take effect.
    
    Closes #3496
    stanhu authored Oct 10, 2024
    Configuration menu
    Copy the full SHA
    0bc0788 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    ce6d5c1 View commit details
    Browse the repository at this point in the history
Loading