Open YoranBrondsema opened 10 years ago
+1
+1
+1
+1
+1
+1
could it be in my case because the request is being done to http and not https?
sorry in the miniprofiler looks with http, but on the console the post is with https
+1
temporay solve problem by removing files in tmp/miniprofiler/mp_timers_*
in project dir and restart server.
hope this help find permanent solution
+1
rm -fr tmp/miniprofiler
Thanks @wild-r and @guange2015 , rm -fr tmp/miniprofiler
has worked for me as a temporary solution.
+1 for @wild-r and @guange2015 for rm -rf tmp/miniprofiler
+1
With http://lotusrb.org/ getting 404 to POST to /mini-profiler-resources/results
@sanrodari @murtali MemoryStorage seems to be broken. FileStorage works, which is default storage for rails.
Rack::MiniProfiler.config.storage = Rack::MiniProfiler::FileStore
Rack::MiniProfiler.config.storage_options = { path: './tmp' }
Is there desire to make file system the default for all?
Do we need to do something more extravagant than path: './tmp'
like ENV['TMP_DIR']
or something?
@kbrock path depends on framework you are working with. Just do like you want.
File.join(Dir.pwd, 'tmp')
# or
File.join(__dir__, 'tmp')
# or
File.expand_path(File.dirname(__FILE__), 'tmp') # if you are setting it in config.ru
Don't forget to create target directory. About default engine, I think everybody free to choose one :smile:
creating the target directory should be all set with #208
@railsme Setting the default store to FileStore is easy enough. But I still don't know what the gem should set as the default path. every framework wants something different. I agree that the user can pick something easily. But if the default store is file, then either a good default path needs to be chosen, or it will be broken out of the box. (maybe not much of a change)
@sanrodari Is there something like railties for Hanami (Framework Formerly Known as Lotus) where a suitable Hanami defaults can be set?
@kbrock I don't know something like a railtie in Hanami, maybe @jodosha can help us?
+1 rm -rf tmp/miniprofiler solved the issue. Thanks.
@kbrock @sanrodari Hi, Hanami is Rack based, you can use
it in config.ru
.
+1
+1
+1
Sorry to see so many +1 here. Are the issues still with rails. or are they for Rack / Sinatra / Other framework apps?
For me, it's happening with Rails
@shaneog thanks. and that is rails 4.0 I assume?
@kbrock Apologies, it is. Rails 4.2.7
Rails 4.2.x
Sent from my iPhone
On 25 Aug 2016, at 19:44, Keenan Brock notifications@github.com wrote:
Sorry to see so many +1 here. Are the issues still with rails. or are they for Rack / Sinatra / Other framework apps?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
Rails 4.2.x
Thanks,
Rob Little.
On Thu, Aug 25, 2016 at 9:07 AM, Prokop Simek notifications@github.com wrote:
Rails 4.2.x
Sent from my iPhone
On 25 Aug 2016, at 19:44, Keenan Brock notifications@github.com wrote:
Sorry to see so many +1 here. Are the issues still with rails. or are they for Rack / Sinatra / Other framework apps?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/MiniProfiler/rack-mini-profiler/issues/71#issuecomment-242503182, or mute the thread https://github.com/notifications/unsubscribe-auth/ABjJo1SDMaPibQIjdOn3KvTEMiJ-ldoGks5qjefXgaJpZM4BxCLX .
This still seems to be an issue on Rails 4.2 - @railsme's suggestion above works perfectly.
jFYI: Same with Rails 5.2.2
I'm running into this with a Sinatra app and version 2.3.1 - I know this issue is pretty old, but since it's still open I figured it might be worth a comment.
Same with:
Rack::MiniProfiler::MemoryStore
Seeing it (HTTP 422) with:
Rails 6.1.7 Puma 5.6.4 rack-mini-profiler 3.0.0
rm -rf tmp/miniprofiler
fixes the issue for now :adhesive_bandage:
I think if we had a simple reproducing app, we could fix this for all storage engines.
Hi,
I am running rack-mini-profiler on Rails 4.0.3 and I'm having issues. All but one POST to /mini-profiler-resources/results returns a 404. I included a screenshot below. Would anyone have an idea what might be causing this?