Skip to content
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

RetryFunc.java:37-41: Avoid usage of null value in... #886

Closed
0pdd opened this issue May 19, 2018 · 12 comments
Closed

RetryFunc.java:37-41: Avoid usage of null value in... #886

0pdd opened this issue May 19, 2018 · 12 comments

Comments

@0pdd
Copy link
Collaborator

0pdd commented May 19, 2018

The puzzle 861-3f3a5fe1 from #861 has to be resolved:

* @todo #861:30min Avoid usage of null value in ctor(Proc),
* ctor(Proc, int), ctor(Proc, Func(Integer, Boolean)) which is against
* design principles.
* Perhaps in creating RetryProc?
* Please take a look on #551 and #843 for more details.

The puzzle was created by Isammoc OFF on 16-May-18.

Estimate: 30 minutes,

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0crat
Copy link
Collaborator

0crat commented May 19, 2018

@llorllale/z please, pay attention to this issue

@0crat
Copy link
Collaborator

0crat commented May 19, 2018

Job #886 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Jun 29, 2018

The job #886 assigned to @vssekorin/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

vssekorin added a commit to vssekorin/cactoos that referenced this issue Jul 3, 2018
@0crat
Copy link
Collaborator

0crat commented Jul 4, 2018

@vssekorin/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.

@0crat
Copy link
Collaborator

0crat commented Jul 26, 2018

The user @vssekorin/z resigned from #886, please stop working. Reason for job resignation: It is older than 10 days, see §8

@0crat
Copy link
Collaborator

0crat commented Jan 14, 2019

The job #886 assigned to @iprogrammerr/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 no monetary reward for this job

BinaryIgor pushed a commit to BinaryIgor/cactoos that referenced this issue Jan 15, 2019
BinaryIgor pushed a commit to BinaryIgor/cactoos that referenced this issue Jan 20, 2019
BinaryIgor pushed a commit to BinaryIgor/cactoos that referenced this issue Jan 24, 2019
BinaryIgor pushed a commit to BinaryIgor/cactoos that referenced this issue Jan 24, 2019
BinaryIgor pushed a commit to BinaryIgor/cactoos that referenced this issue Jan 24, 2019
BinaryIgor pushed a commit to BinaryIgor/cactoos that referenced this issue Feb 2, 2019
BinaryIgor pushed a commit to BinaryIgor/cactoos that referenced this issue Feb 2, 2019
BinaryIgor pushed a commit to BinaryIgor/cactoos that referenced this issue Feb 2, 2019
BinaryIgor pushed a commit to BinaryIgor/cactoos that referenced this issue Feb 2, 2019
BinaryIgor pushed a commit to BinaryIgor/cactoos that referenced this issue Feb 2, 2019
@BinaryIgor
Copy link
Contributor

@llorllale Seems that with rebasing and/or force pushing 0pdd doesn't close issues related to PR's. What should we do?

@0pdd
Copy link
Collaborator Author

0pdd commented Feb 7, 2019

The puzzle 861-3f3a5fe1 has disappeared from the source code, that's why I closed this issue.

@0pdd
Copy link
Collaborator Author

0pdd commented Feb 7, 2019

@0pdd the puzzle #1062 is still not solved.

@0crat 0crat removed the scope label Feb 7, 2019
@0crat
Copy link
Collaborator

0crat commented Feb 7, 2019

The job #886 is now out of scope

@0crat
Copy link
Collaborator

0crat commented Feb 7, 2019

Order was finished: +30 point(s) just awarded to @iprogrammerr/z

@0pdd
Copy link
Collaborator Author

0pdd commented Apr 19, 2019

@0pdd the only puzzle #1062 is solved here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants