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

package-info.java:29-31: Exploit generic variance for... #1566

Closed
0pdd opened this issue Mar 14, 2021 · 18 comments
Closed

package-info.java:29-31: Exploit generic variance for... #1566

0pdd opened this issue Mar 14, 2021 · 18 comments

Comments

@0pdd
Copy link
Collaborator

0pdd commented Mar 14, 2021

The puzzle 1533-48e5c994 from #1533 has to be resolved:

* @todo #1533:30min Exploit generic variance for package org.cactoos.list
* to ensure typing works as best as possible as it is explained in
* #1533 issue.

The puzzle was created by @baudoliver7 on 13-Mar-21.

Estimate: 30 minutes, role: DEV.

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.

@0pdd
Copy link
Collaborator Author

0pdd commented Mar 14, 2021

This puzzle inherited milestone 1.0 from issue #1533.

@victornoel
Copy link
Collaborator

@0crat status

@0crat
Copy link
Collaborator

0crat commented Jun 22, 2021

The job #1566 assigned to @DmitryBarskov/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

DmitryBarskov added a commit to DmitryBarskov/cactoos that referenced this issue May 6, 2022
DmitryBarskov added a commit to DmitryBarskov/cactoos that referenced this issue May 6, 2022
DmitryBarskov added a commit to DmitryBarskov/cactoos that referenced this issue May 6, 2022
DmitryBarskov added a commit to DmitryBarskov/cactoos that referenced this issue May 6, 2022
DmitryBarskov added a commit to DmitryBarskov/cactoos that referenced this issue Jul 15, 2022
@DmitryBarskov
Copy link
Contributor

@0crat status

@victornoel
Copy link
Collaborator

@yegor256 0pdd seems to be broken, can you fix it?

@yegor256
Copy link
Owner

@victornoel we're working with this: yegor256/0pdd#371

@yegor256
Copy link
Owner

yegor256 commented Jul 26, 2022

@victornoel how about now? push something to master, 0pdd should react

@DmitryBarskov
Copy link
Contributor

@0crat status

Will it work?

@victornoel
Copy link
Collaborator

@yegor256 @DmitryBarskov we need to re-run 0pdd, I will try to do this

@victornoel
Copy link
Collaborator

@yegor256 0pdd has re-run as part of the github CI, but it does not seem to have had any impact… is it only applied when it's executed by rultor maybe? I don't understand how it works

yegor256 added a commit that referenced this issue Jul 27, 2022
yegor256 added a commit that referenced this issue Jul 27, 2022
@0pdd
Copy link
Collaborator Author

0pdd commented Jul 30, 2022

The puzzle 1533-48e5c994 has disappeared from the source code, that's why I closed this issue.

@0pdd 0pdd closed this as completed Jul 30, 2022
@victornoel
Copy link
Collaborator

@DmitryBarskov looks like it's good now!

Thx @yegor256 for triggering 0pdd , now what's happening with 0crat bot, it's not working anymore?

@0crat
Copy link
Collaborator

0crat commented Aug 1, 2022

@0crat status (here)

@DmitryBarskov This is what I know about this job in C63314D6Z, as in §32:

@0crat
Copy link
Collaborator

0crat commented Aug 1, 2022

@0crat status Will it work? (here)

@DmitryBarskov This is what I know about this job in C63314D6Z, as in §32:

@0crat
Copy link
Collaborator

0crat commented Aug 1, 2022

@0crat status (here)

@victornoel This is what I know about this job in C63314D6Z, as in §32:

@victornoel
Copy link
Collaborator

@yegor256 what's the command again to tell 0crat that the ticket has been closed and it should trigger the end of the job?

@yegor256
Copy link
Owner

yegor256 commented Aug 1, 2022

@0crat out

@0crat 0crat added the qa label Aug 1, 2022
@0crat
Copy link
Collaborator

0crat commented Aug 1, 2022

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

@0crat 0crat removed the 0crat/scope label Aug 1, 2022
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

5 participants