http.rb must be reactive #176
Comments
Job #176 is now in scope, role is |
@emilianodellacasa/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please. |
The user @emilianodellacasa/z resigned from #176, please stop working. Reason for job resignation: It is older than 10 days, see §8 |
Resigned on delay, see §8: -30 point(s) just awarded to @emilianodellacasa/z |
@0crat resign |
@KuxaBeast Job |
@0crat wait - this issue seems to be assigned to two different users, opening an issue |
@emilianodellacasa The impediment for #176 was registered successfully by @emilianodellacasa/z |
@0crat status |
@g4s8 This is what I know about this job in CAZPZR9FS, as in §32:
|
@yegor256 What does it mean to make "http.rb more reactive"? Is it something related to its speed and performance or do you have something specific in mind? |
@emilianodellacasa would be great to make it work like this:
I'm not sure whether we need it now though... |
@yegor256 If you think this issue is not needed anymore we can close it, I won't mind |
@0crat refuse |
Job |
The job #176 is now out of scope |
At the moment we are spending a lot of time on waiting for remote nodes. Instead, we should make
http.rb
reactive. See also #81The text was updated successfully, but these errors were encountered: