Agis Anastasopoulos
Agis Anastasopoulos
While using the IDP server for integration tests, I've experienced a deadlock after issuing many concurrent requests to the following endpoints: - `PUT /services/:id` - `GET /sso` Apparently, the issue...
I want to store uploaded images in different locations, depending on the view. This could be done if there's a way to use different model & uploader for each editor...
As the following example demonstrates, after I edit `config/environments/development.rb`, even though it seems Spring properly restarts, the changes are not reflected when I run `bin/rails c` until I run `bin/spring...
This will effectively allow upstream servers to know with how many concurrency we're downloading from them. With this information, they could implement smarter rate-limiting, notice potential misconfigurations on our side...
It should be easy for users to test their commands inside their apps.
Right now, since all the user-defined commands are eventually turn into Proc objects, we can't use `return`. So we are forced to use `next` instead, but it's not intuitive.
When an error occurs inside a command, the backtrace is not useful due to eval. We should fix this.
We should somehow only accept requests from the cogy executable. This could be done by generating a token from the host application and send it in the `config` section of...