forked from carrierwaveuploader/carrierwave
-
Notifications
You must be signed in to change notification settings - Fork 2
Update #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
asurin
wants to merge
1,116
commits into
tkwwarchive:0.11-stable
Choose a base branch
from
carrierwaveuploader:master
base: 0.11-stable
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
e.g)
The implicit block expectation syntax is deprecated, you should pass a block rather than an argument to `expect` to use the provided block expectation matcher or the matcher must implement `supports_value_expectations?`. e.g `expect { value }.to raise CarrierWave::DownloadError` not `expect(value).to raise CarrierWave::DownloadError`
suppress following deprecation warning /home/runner/work/carrierwave/carrierwave/spec/uploader/url_spec.rb:64: warning: already initialized constant FileX /home/runner/work/carrierwave/carrierwave/spec/uploader/url_spec.rb:64: warning: previous definition of FileX was here
prevent to add code with rspec deprecation
suppress some rspec deprecation warning
Fix content type detection for JSON files.
rails/sprockets already has no master branch.
Fixed non-existent branch name
Restored the condition to execute write_uploader
Co-authored-by: Mitsuhiro Shibuya <mit.shibuya@gmail.com>
…ions Set `:content_type` in `copy_options` for GCS.
Have RemoteFile raise CarrierWave::DownloadError when the HTTP response is of a type that has no content, according to the standards. In those cases, response.body returns nil. There are 8 response types that have no body, 4 of which we can get, so just check whether the body was nil. Fixes #2632
Includes a backwards compatibility mode for SsrfFilter 1.0, which is needed for Ruby 2.5 and JRuby 9.2. Also includes a local version constraint for fog-google for Ruby 2.5 and JRuby 9.2 because of a known but undeclared incompatibility in that gem. gemfiles/rails-6-1.gemfile already has this fix. [Fixes #2625]
Support ssrf_filter 1.1
chore: minor refactor from select first to detect
Raise DownloadError when no content is returned
…ptions fix: ruby 2.7 kwarg warning in uploader process
public_url returns a path-based URL when :endpoint is given. AWS FIPS endpoints only work with virtual host-style URLs per https://aws.amazon.com/compliance/fips/ Add a warning and return nil if both :endpoint is given and :fog_aws_fips=true. Add tests for :endpoint for both :fog_aws_fips=false (default) and true.
The CarrierWave::Storage::File#public_url method returns the standard
- Raises an error instead of returning nil - Reorganize spec/storage/fog_helper.rb so it doesn't have high cyclomatic complexity
…der-template Add CarrierWave::Vips comment to uploader template
These specs originate from this one: fe90e05#diff-139363042a1d27e5830373d80deb5a2f8e7afcb68e28be55a73ffbd587517c0dR55-R57 But it was implemented in a wrong way (without calling #image=). Also this assumption doesn't hold true after #2658.
While `write_uploader` is aliased to `write_attribute` by default, it may be overridden in the model. This change ensures that the override method is called when clearing the attribute.
Fixes #2732 Starting in Alpine Linux 3.19, installing the `imagemagick` package no longer includes support for JPG, SVG, and other image formats.[1] This means upgrading Alpine linux on a server can cause Carrierwave to start failing with CarrierWave::ProcessingError when uploading images. The root cause isn't obvious from this error. However when ImageMagick is not installed, Carrierwave raises MiniMagick::Error instead of CarrierWave::ProcessingError, and includes the detailed error message. This fix also raises MiniMagick::Error if ImageMagick is installed but is missing the delegates required for the image format being manipulated. This will make it easier to debug when uploads are failing. [1] https://maxsmolens.org/posts/imagemagick-packaging-change-on-alpine-linux/
mb_chars has been deprecated. and can be replaced rails/rails#54081
…r-on-dup Fix #dup with custom serialisation
…issing-jpg-svg-delegates-on-alpine Raise MiniMagick::Error if ImageMagick is missing delegates needed for image formats
Remove use of deprecated mb_chars method
Marking ruby-head as experimental, until cucumber works on it
By providing a 'changelog_uri' in the metadata of the gemspec a 'Changelog' link will be shown on https://rubygems.org/gems/carrierwave which makes it quick and easy for someone to check on the changes introduced with a new version. Details of this functionality can be found on https://guides.rubygems.org/specification-reference/#metadata
Adds a commented example of `content_type_allowlist` (/image\//) to the generated uploader. It mirrors the existing `extension_allowlist` comment and helps users mitigate content-type spoofing attacks.
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 5. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v4...v5) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.