For #63: Fix of too many threads error.

[paulodamaso]

For #63: Fix of too many threads error.

• Left Executor manage thread pool;
• Added check for interrupted threads.

[0crat]

Job #68 is now in scope, role is REV

[0crat]

@carlosmiranda/z everybody who has role DEV is banned at #68; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[carlosmiranda]

@0crat assign @pinaf

[0crat]

@0crat assign @pinaf (here)

@carlosmiranda The job #68 assigned to @pinaf/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be a monetary reward for this job

[0crat]

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @carlosmiranda/z

[g4s8]

@0crat status

[0crat]

@0crat status (here)

@g4s8 This is what I know about this job in C7FCB1EQN, as in §32:

• The job #68 is in scope for 3hr
• The role is DEV
• The job is assigned to @pinaf/z for 2hr
• There is a monetary reward attached
• @pinaf/z will get 50% of their hourly rate for this job
• The job doesn't have any impediments
• The budget is 30 minutes/points
• These users are banned and won't be assigned:
  • @paulodamaso/z: This user reported the ticket
• Job footprint (restricted area)

[pinaf]

@carlosmiranda shouldn't the role here be REV?

[paulodamaso]

@pinaf Thanks for the review, please take a look.

[pinaf]

@carlosmiranda @paulodamaso Unfortunately I can't think of an easy way to tie this error down with a unit test, but it seems reasonable to infer that this abundance of threads would be related to instantiating executors services all the time, wouldn't you agree?

[paulodamaso]

@pinaf Fixed the last issue, please take a look. As for your question I've found difficult to unit test this error too. I think that the two conclusions are tied, this executor instantiating and the fixed check for 64 threads together were causing the issue, I think.

[pinaf]

@paulodamaso Looks good, thank you.

[pinaf]

@carlosmiranda Looks good to merge

[carlosmiranda]

@pinaf yeah, it's a bug, see https://github.com/zerocracy/farm/issues/1675

[carlosmiranda]

@0crat boost 1x

[0crat]

@0crat boost 1x (here)

@carlosmiranda Boost 1x was set for #68

[0crat]

Boosting tasks is against our principles, see §15: -10 point(s) just awarded to @carlosmiranda/z

[carlosmiranda]

@rultor merge

[rultor]

@rultor merge

@carlosmiranda OK, I'll try to merge now. You can check the progress of the merge here

[rultor]

@rultor merge

@carlosmiranda Done! FYI, the full log is here (took me 14min)

[0crat]

Job was finished in 18 hours, bonus for fast delivery is possible (see §36)

[0crat]

@ypshenychka/z please review this job completed by @pinaf/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

[0crat]

The job #68 is now out of scope

[0crat]

Payment to ARC for a closed pull request, as in §28: +10 point(s) just awarded to @carlosmiranda/z

[ypshenychka]

@0crat quality good

[0crat]

Order was finished, quality is "good": +25 point(s) just awarded to @pinaf/z

[0crat]

Quality review completed: +8 point(s) just awarded to @ypshenychka/z