-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Big rails, ruby and gem version update #240
Conversation
1774a63
to
8fd8488
Compare
@oscgonfer perdona, he arreglado los tests - ahora está listo para revisar! |
Hey, some feedback after testing this: After doing some normal unauthenticated requests, I did two with Auth, to test
And the logs show:
|
Aha, thanks for testing! I'll take a look ASAP and get to the bottom of it! :-) |
Commenting on the |
Also, adding here - there are these entries in the log:
|
8fd8488
to
4d0b3fb
Compare
Hey @oscgonfer , I have fixed the weird 'marshal format' error (it was, as expected, to do with the throttling), and tested that the CSV job runs successfully - it does, with the caveat that the email doesn't get set (due to a 404 from ActiveDispatch when attempting to contact the mailgun server) - however, I think this is a misconfiguration on staging in general rather than an upgrade problem - the same thing happens when I test from the current |
Hi! I just tested 1000 requests with unauthorized (no bearer) and I think this last fix would have broken the throttling, see below for logs:
So basically, there is a throttling in between, but it immediately comes back to accepting requests. |
Hey Oscar, I've just been looking at this - I saw the same behaviour, but after a hard rebuild of the docker container it seems to have fixed itself! I'm seeing the throttling working as before for unauthorized users, but. shall we verify together next week before deploying? docker images seem weirdly 'sticky' btw - i had to do a |
Tried to update as much as possible without breakage / huge changes - this will still need a good test before deploying, but looks good so far. upgrade rails to 6.1.7.3 Update doorkeeper to version ~> 5 Upgrade Ruby to 3.0.6 upgrade sidekiq to 6.0
4946d03
to
54d83e9
Compare
Tried to update as much as possible without breakage / huge changes - this will still need a good test before deploying, but looks good so far.
upgrade rails to 6.1.7.3
Update doorkeeper to version ~> 5
Upgrade Ruby to 3.0.6
upgrade sidekiq to 6.0
ON DEPLOYMENT:
ensure that
RAILS_LOG_TO_STDOUT=true
is present in the.env
file