Fullscreen / yt

94%

master: 94%

LAST BUILD ON BRANCH v0.33.4

branch: v0.33.4

CHANGE BRANCH

x

Reset

• v0.33.4
• accept-camelcase-privacy-status
• accept-env-variables
• activesupport-4.1.4
• add-authentication
• add-days-and-weeks-to-duration
• add-filter-to-account-videos
• add-live-attributes
• add-live-streaming-detail
• add-log-level
• add-new-url-back
• add-partnered-channels
• add-statistics
• add-status-fields
• add-todo
• add-video-update
• add-viewer-percentages
• add-yt-support-back
• analytics
• asset-and-ownership
• asset-monetization-flow
• auth-no-api-key
• automatically-refresh-the-access-token
• be-kind-rewind
• better-code
• better-weather
• bug/playlist-status
• bump-gems
• bump-rspec
• camelize
• channel-comment-count
• channels-with-more-than-500-videos
• co-upload-thumbnail
• co-video-update
• delegate-explicitly
• device
• do-not-delete
• don-t-fail-on-adding-unavailable-videos
• extend-snippet
• extract-metrics
• extract-reports
• extracting-has-many
• extracting-status
• feature/approval_prompt
• feature/claim-third-party
• feature/claims
• feature/collection-include
• feature/content-owner-detail
• feature/content-owners-list
• feature/list-claims
• feature/policies
• feature/references
• feature/video-search
• fix-annotations
• fix-annotations-with-0-timestamp
• fix-claim-segments
• fix-duration
• fix-failing-spec
• fix-gzip-for-ruby-19
• fix-refresh
• fix-ruby-specs
• fix-travis
• fix-travis-key
• handle-random-400-error-from-youtube
• implement-access-token
• issue-43
• limit-refresh-retry
• list-references
• master
• metrics-for-non-content-owners
• more-metrics
• only-update-passed-parameters
• playlist-items-content-owner
• remove-by-week
• remove-collection-resources
• rename-rating-update-to-set
• rename-time-updated
• reports-for-videos
• rescue-503-errors
• retry-refresh-token-once
• retry-timeout
• retry-youtube-request-when-they-might-work-the-second-time
• sanitize-angle-brackets
• size-not-count
• sort-videos-by-most-recent-first
• stage
• stage-2
• stage-3
• temporarily-add-logger-to-notify-google-of-500-errors
• temporarily-skip-content-owner-specs
• test-rspec-tag
• token-empty
• track-500-errors-separately
• transform-brackets-in-snippets
• update-accepts-both-underscore-and-camelcase
• update-changelog-for-jcohenho
• update-patch-asset
• update-tests
• update-video-status
• upload-in-chunks
• upload-video
• url-id-bug-fixes
• v0.11.0
• v0.11.1
• v0.32.4
• v0.32.5
• v0.32.6
• v0.33.0
• v0.33.2
• v0.4.10
• v0.4.7
• v0.4.8
• v0.4.9
• v0.5.10
• v0.5.11
• v0.5.12
• v0.5.13
• v0.5.14
• v0.5.3
• v0.5.4
• v0.5.5
• v0.5.6
• v0.5.7
• v0.5.8
• v0.5.9
• v0.6.0
• v0.6.1
• v0.6.2
• v0.6.3
• v0.6.4
• v0.6.5
• v0.6.6
• v0.7.0
• v0.7.1
• v0.7.10
• v0.7.11
• v0.7.2
• v0.7.3
• v0.7.4
• v0.7.5
• v0.7.6
• v0.7.8
• v0.7.9
• v0.8.0
• v0.8.1
• v0.8.2
• v0.8.3
• v0.8.4
• v0.8.5
• v0.9.0
• v0.9.1
• v0.9.2
• v0.9.3
• v0.9.4
• v0.9.6
• v0.9.7
• vcr
• version-bump
• yt-collections-videos
• yt-info
• yt-video-where

Build # 591

Build Type

push

travis-ci

Committed by web-flow

Commit Message

Don't retry on quota errors (#401)

* Don't retry on quota errors

They say that insanity is doing the same thing over and over and
expecting different results...

This patch removes retry behavior on quota issues because:

* this isn't useful when daily quota has been reached
* in the case of 100s quota, you'd need to be attempting requests ~61s
into the quota cool-off in order for the final retry to succeed. That
seems pretty unlikely.

So for all practical purposes, when quota is reached, the library stalls
for the maximum timeout time (39s by my math). This is further
problematic when making requests in environments like Heroku that have
a 30s timeout for web request-response cycles.

Let's do the sane thing and just raise an error when quota is reached.

* Bump to 0.33.4 [ci-skip]

Run Details

5630 of 5994 relevant lines covered (93.93%)

40.58 hits per line