Open JamiePhonic opened 7 years ago
Same as @JamiePhonic , Nginx error log
and Runit/Background Worker logs
and Unicorn log
are all fine, only production.log
shows here:
I, [2017-03-26T14:53:23.338066 #13047] INFO -- : [cf103f69-3a3f-4955-a875-0cac5268f585] Started GET "/scenarios/14/export.json" for 54.162.208.2 at 2017-03-26 14:53:23 +0800
I, [2017-03-26T14:53:23.339222 #13047] INFO -- : [cf103f69-3a3f-4955-a875-0cac5268f585] Processing by ScenariosController#export as JSON
I, [2017-03-26T14:53:23.339474 #13047] INFO -- : [cf103f69-3a3f-4955-a875-0cac5268f585] Parameters: {"id"=>"14"}
I, [2017-03-26T14:53:23.387118 #13047] INFO -- : [cf103f69-3a3f-4955-a875-0cac5268f585] Completed 200 OK in 47ms (Views: 0.2ms | ActiveRecord: 0.0ms)
@JamiePhonic Thanks for creating the issue, here is the backtrace I am getting with http://huginnio.herokuapp.com/scenarios/14/download
[3dc4d58b-935c-4b02-889a-25d9d7f2f1a3] ActionView::Template::Error (incompatible character encodings: ASCII-8BIT and UTF-8):
[3dc4d58b-935c-4b02-889a-25d9d7f2f1a3] 18: <% if @scenario_import.step_one? %>
[3dc4d58b-935c-4b02-889a-25d9d7f2f1a3] 19: <%= render 'step_one', :f => f %>
[3dc4d58b-935c-4b02-889a-25d9d7f2f1a3] 20: <% elsif @scenario_import.step_two? %>
[3dc4d58b-935c-4b02-889a-25d9d7f2f1a3] 21: <%= render 'step_two', :f => f %>
[3dc4d58b-935c-4b02-889a-25d9d7f2f1a3] 22: <% end %>
[3dc4d58b-935c-4b02-889a-25d9d7f2f1a3] 23: <% end %>
[3dc4d58b-935c-4b02-889a-25d9d7f2f1a3] 24:
Right, so i tried downloading the JSON file for the scenario first and uploading it to a stand alone web server (Running Apache2 this time), then entering that URL into hugin.io, but i still get the same error.
I'm not entirely sure how you've coded the backend and I'm not a ruby (or really any programming language) dev by any stretch, but I'm confused as to how uploading the file works, but getting the server to download it doesn't.
My database is using UTF8-MB4 if that could be related somehow, but I'm not storing any extended characters like emoji, and notepad++ recognizes the file as being encoded with UTF8.
At a guess, id say that somewhere in your code, the file is being read as ASCII, and in other places as UTF8 (Again, not a programmer)
So, it would appear that the issue where users recieve the
We're sorry, but something went wrong.
message when attempting to upload a scenario from a public URL instead of a file has returned.I origonally ran into this issue myself back in november last year but the issue was rectified pretty swiftly. I noticed that its now popped back up again in #https://github.com/cantino/huginn/issues/1774 , so i thought that since i had to update my `UK TV Air Dates" scenario anyway, that i'd try using the Public URL and provide the same information that you asked waldens for in #https://github.com/cantino/huginn/issues/1774
Relevent entry's from Huginn's
Production.log
(Prior entry's timestamps are from hours earlier, so i assumed they wouldnt be relevant)Relevent entry's from Nginx
Let me know if you need any other information, and keep up the amazing work your doing on huginn and its related projects!