Yuval Kordov
Yuval Kordov
Its Friday, so entirely possible I just need a drink and some sleep. But after upgrading a legacy app to the latest and greatest, I've started to see unexpected validations...
Its been a long day, so I may be missing something completely obvious, but I ran into this very strange error today. I have two models named User and Document...
Just an FYI. The upload doesn't start when a file is dragged onto the target zone. Using the button does work.
When setting `splines: ortho`, no ERD is produced when inheritance or polymorphism are set to true. There are no warnings or errors during the processing.
I have an authenticated download method in my asset model as follows: AWS::S3::S3Object.url_for(upload.path(style || upload.default_style), upload.bucket_name, :use_ssl => upload.s3_protocol == 'https', :expires_in => expires_in) This generates a secure, expiring link...
Noticed this today when testing a form that I wanted to limit to single uploads. Even if you specify allow_multiple_files: false in the initializer, you can drag and drop multiple...
I found that `Rails.logger.silence` blocks fail when using this gem. The issues seems to be that `RemoteSyslogLogger.new` instantiates a`Logger`, when it should be instantiating an `ActiveSupport::Logger`. Reference: https://stackoverflow.com/a/38361137
I noticed during a rudimentary test today that the max_file_size param correctly limits uploads with s3, but an error is only thrown when s3 reaches its policy limit. Oversized files...