sam
January 12, 2018, 3:28am
7
OK this is fixed per:
I just finished pushing a rather gnarly change per:
https://github.com/discourse/discourse/commit/49ed382c2a7ddd11756e552e094319861418cd7f
It basically replaces this pattern we used previously in tests:
expect do
get :index, format: :json
end.to raise_error(Discourse::NotLoggedIn)
With this
get :index, format: :json
expect(response.status).to eq(403)
I made this change so our test environment is much more inline with our production environment. Previously we were leaking out a few exc…
But it will take a bit for it to land cause I need to clean plugin tests.
The particular reason you are getting rate limited is:
message_bus_redis_password =
# skip configuring client id for cloud providers who support no client commands
message_bus_redis_skip_client_commands = false
# enable Cross-origin Resource Sharing (CORS) directly at the application level
enable_cors = false
cors_origin = ''
# enable if you really need to serve assets in prod
serve_static_assets = false
# number of sidekiq workers (launched via unicorn master)
sidekiq_workers = 5
# adjust stylesheets to rtl (requires "rtlit" gem)
rtl_css = false
# connection reaping helps keep connection counts down, postgres
# will not work properly with huge numbers of open connections
# reap connections from pool that are older than 30 seconds
if you are self hosting you can raise DISCOURSE_MAX_ADMIN_API_REQS_PER_KEY_PER_MINUTE to a higher number. We introduced this limit to protect from unintentional API abuse.
6 Likes