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

SpotBugsValidatorTest.java:39-42: Continue migration from... #959

Open
0pdd opened this issue Dec 5, 2018 · 24 comments
Open

SpotBugsValidatorTest.java:39-42: Continue migration from... #959

0pdd opened this issue Dec 5, 2018 · 24 comments
Labels

Comments

@0pdd
Copy link
Collaborator

0pdd commented Dec 5, 2018

The puzzle 884-ab2ca2fa from #884 has to be resolved:

https://github.com/teamed/qulice/blob/3fc6397fd84790caefe24a013133455ec9cd489c/qulice-spotbugs/src/test/java/com.qulice.spotbugs/SpotBugsValidatorTest.java#L39-L42

The puzzle was created by Paulo Lobo on 05-Dec-18.

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 Dec 5, 2018

@krzyk/z please, pay attention to this issue

@0crat 0crat added the scope label Dec 5, 2018
@0crat
Copy link
Collaborator

0crat commented Dec 5, 2018

Job #959 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Jan 24, 2019

The job #959 assigned to @paulodamaso/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

@paulodamaso
Copy link
Contributor

@0crat refuse

@0crat
Copy link
Collaborator

0crat commented Jan 28, 2019

@0crat refuse (here)

@paulodamaso The user @paulodamaso/z resigned from #959, please stop working. Reason for job resignation: Order was cancelled

@0crat
Copy link
Collaborator

0crat commented Jan 28, 2019

Tasks refusal is discouraged, see §6: -15 point(s) just awarded to @paulodamaso/z

@0crat
Copy link
Collaborator

0crat commented Jan 28, 2019

@krzyk/z everybody who has role DEV is banned at #959; 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)

@krzyk
Copy link
Collaborator

krzyk commented Jan 30, 2019

@0crat assign @korthout

@0crat
Copy link
Collaborator

0crat commented Jan 30, 2019

@0crat assign @korthout (here)

@krzyk The job #959 assigned to @korthout/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; @korthout/z is not a member of this project yet, but they can request to join, as §1 explains; there will be no monetary reward for this job

@0crat
Copy link
Collaborator

0crat commented Jan 30, 2019

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

@korthout
Copy link
Contributor

@krzyk I keep having difficulty implementing this. Running Spotbugs in a separate process like in the findbugs module is difficult to debug, let alone use TDD to implement it. It's a bit discouraging. Ideas on how to approach this? Otherwise, perhaps someone else will have to resolve this one.

@krzyk
Copy link
Collaborator

krzyk commented Mar 3, 2019

@korthout no worries, I don't have idea right now, maybe I'll jump into it myself when I'll find some spare time

@krzyk
Copy link
Collaborator

krzyk commented Mar 3, 2019

@0crat refuse

@0crat
Copy link
Collaborator

0crat commented Mar 3, 2019

@0crat refuse (here)

@krzyk The user @korthout/z resigned from #959, please stop working. Reason for job resignation: Order was cancelled

@0crat
Copy link
Collaborator

0crat commented Mar 3, 2019

@krzyk/z everybody who has role DEV is banned at #959; 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)

@0crat
Copy link
Collaborator

0crat commented Mar 8, 2019

@krzyk/z everybody who has role DEV is banned at #959; 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)

@0crat
Copy link
Collaborator

0crat commented Mar 13, 2019

@krzyk/z everybody who has role DEV is banned at #959; 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)

@0crat
Copy link
Collaborator

0crat commented Mar 18, 2019

@krzyk/z everybody who has role DEV is banned at #959; 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)

@0crat
Copy link
Collaborator

0crat commented Mar 23, 2019

@krzyk/z everybody who has role DEV is banned at #959; 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)

@0crat
Copy link
Collaborator

0crat commented Mar 28, 2019

@krzyk/z everybody who has role DEV is banned at #959; 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)

@0crat
Copy link
Collaborator

0crat commented Apr 2, 2019

@krzyk/z everybody who has role DEV is banned at #959; 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)

@0crat
Copy link
Collaborator

0crat commented Apr 7, 2019

@krzyk/z everybody who has role DEV is banned at #959; 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)

@0crat
Copy link
Collaborator

0crat commented Apr 12, 2019

@krzyk/z everybody who has role DEV is banned at #959; 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)

@0crat
Copy link
Collaborator

0crat commented Apr 17, 2019

@krzyk/z everybody who has role DEV is banned at #959; 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)

@yegor256 yegor256 removed pdd labels Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants