-
Notifications
You must be signed in to change notification settings - Fork 149
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
[image: {"is invalid", [type: AppName.ImageUploader.Type]}] #81
Comments
Having the same issue:
|
So I had this problem tonight and it ended up being that I had the wrong settings in prod for my IAM token so the upload to s3 was failing. |
Also here. |
Getting this as well. @shawnonthenet can you elaborate on your IAM issue? I only have a single user and key. Works on another dev's machine. |
In my case there's something wrong with Imagemagick which cause the conversion step to fail. Error traced on this line Everything back to normal after "brew update imagemagick". |
@xfumihiro Thanks!! |
This should have more visibility. Upgrading |
(ArgumentError) invalid or unknown type Golfcoupons.PackageImageUploader.Type for field :image I have ImageMagik installed on Linux Mint 18.2 (package version 8:6.8.9.9-7ubuntu5.9) |
I'm having this problem and I can't make it work. I've uninstalled and reinstalled imagemagick with homebrew and I still get Anyone else with this problem or any other possible solution? |
As it said above, upload failure to S3 causes Line 68 in d114fe0
So any kind of storage failure will cause is invalid error.Why not raise or propagate adequate error? Image itself is fine, it's just some network error. |
So I've lost about an hour trying to get a debug to find out why I received [{:http_error, 403,
%{body: "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error><Code>RequestTimeTooSkewed</Code><Message>The difference between the request time and the current time is too large.</Message><RequestTime>20180810T132202Z</RequestTime><ServerTime>2018-08-10T13:37:30Z</ServerTime><MaxAllowedSkewMilliseconds>900000</MaxAllowedSkewMilliseconds><RequestId>B78B31447C732471</RequestId><HostId>...</HostId></Error>",
headers: [{"x-amz-request-id", "..."},
{"x-amz-id-2",
"..."},
{"Content-Type", "application/xml"}, {"Transfer-Encoding", "chunked"},
{"Date", "Fri, 10 Aug 2018 13:37:29 GMT"}, {"Server", "AmazonS3"}],
status_code: 403}}]} So Better to raise an error than to handle it that way. |
Back in February, I had arc_ecto configured and working just fine to upload images to S3 and save the path to my database. As sometimes happens with projects, the client didn't start using what I had built until earlier this week, and (without any changes to deps or related files since February on my part) things don't seem to work any longer. When I try to upload an image, I get the error mentioned in the title. Here's my ImageUploader file:
Here's my Ecto Model file:
Here's the map I'm passing to the changeset method on update, along with a model struct:
Here's the error I'm getting in its entirety:
I'm pretty stumped here. It seems as if the custom type has stopped working, and I could see that happening if any of deps had crept, but I really don't think they have. Here are my pinned versions for reference:
Any help would be much appreciated.
The text was updated successfully, but these errors were encountered: