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

Constructors of FkHitRefresh shouldn't throw any exceptions. #744

Closed
skapral opened this issue Aug 18, 2017 · 26 comments
Closed

Constructors of FkHitRefresh shouldn't throw any exceptions. #744

skapral opened this issue Aug 18, 2017 · 26 comments

Comments

@skapral
Copy link
Contributor

skapral commented Aug 18, 2017

The issue was raised after this discussion - http://disq.us/p/1lgf1ax.

According to this post, constructors should not do any logic inside. For Takes framework, this rule is violated in several places. One of them is the class org.takes.facets.fork.FkHitRefresh, which handles with IO inside a constructor.

PS: @yegor256 please consider me as a contributor to solve this issue.

@0crat
Copy link
Collaborator

0crat commented Aug 18, 2017

@yegor256 please, pay attention to this issue

@yegor256
Copy link
Owner

@skapral thanks! Please, submit a pull request, if you can.

@yegor256
Copy link
Owner

@0crat assign @skapral

@0crat
Copy link
Collaborator

0crat commented Aug 20, 2017

@0crat assign @skapral (here)

@yegor256 Job gh:yegor256/takes#744 assigned to @skapral, please go ahead (policy). @skapral is not a member of this project yet, but can request to join. @skapral check your Zerocracy profile and follow the instructions.

@0crat
Copy link
Collaborator

0crat commented Nov 16, 2017

@skapral this job was assigned to you 8 days ago.
It will be taken away from you after 10 days from start (this is our policy).

@0crat
Copy link
Collaborator

0crat commented Nov 16, 2017

Oops! Job gh:yegor256/takes#744 is not assigned to anyone.

1 similar comment
@0crat
Copy link
Collaborator

0crat commented Nov 16, 2017

Oops! Job gh:yegor256/takes#744 is not assigned to anyone.

@0crat
Copy link
Collaborator

0crat commented Feb 12, 2018

The job #744 assigned to @t-izbassar/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.

@t-izbassar
Copy link
Contributor

@0crat waiting for @skapral to decide what to do with his #745 PR.

@0crat
Copy link
Collaborator

0crat commented Feb 15, 2018

@0crat waiting for @skapral to decide what to do with his #745 PR. (here)

@t-izbassar The impediment for #744 was registered successfully by @t-izbassar/z

@t-izbassar
Copy link
Contributor

@skapral apparently, you are done with this one) #745 is merged, can you close it?)

@t-izbassar
Copy link
Contributor

@skapral ping

@skapral skapral closed this as completed Feb 17, 2018
@0crat
Copy link
Collaborator

0crat commented Feb 17, 2018

@elenavolokhova/z please review this job, as in §30

@elenavolokhova
Copy link

elenavolokhova commented Feb 19, 2018

@yegor256 This ticket violates QA rule:

Problem reporter and problem solver are two different persons.

Desision to let @skapral to deliver a solution to his own ticket led to incorrect situation here:

  • actual problem solver is a bug reporter, but he is not assigned to this ticket any more and is not a member of this project.
  • @skapral assigned to this project didn't actually solve an issue and shouldn't be paid.

Please, confirm that you'll try to avoid assigning problem reporter to his own issue in future.

I assume the quality of this ticket is bad. Please, let me know, if I'm wrong.

@t-izbassar
Copy link
Contributor

@elenavolokhova can you inform 0crat about quality? Personally, I agree with you. I need this task to be closed by 0crat so that I can handle next one - thus you need to inform 0crat about the decision.

@elenavolokhova
Copy link

@t-izbassar Sure.

@elenavolokhova
Copy link

@0crat Quality is bad here.

@0crat
Copy link
Collaborator

0crat commented Feb 19, 2018

@0crat Quality is bad here. (here)

@elenavolokhova Argument "is" doesn't match regex good|bad|acceptable

@elenavolokhova
Copy link

elenavolokhova commented Feb 19, 2018

@0crat Quality bad

@0crat
Copy link
Collaborator

0crat commented Feb 19, 2018

@0crat Quality bad (here)

@elenavolokhova Can't understand "bad", try one of these:

  • assign Assign a performer to this issue
  • boost Set a boost for the job
  • hello Just say hello
  • in Register this issue in scope (WBS)
  • out Remove this issue from scope (WBS)
  • quality Review a task
  • resign Resign from this issue
  • status Check the status of the job
  • version Print current version of the bot
  • waiting Register an impediment for a job

@elenavolokhova
Copy link

@0crat quality bad

@0crat
Copy link
Collaborator

0crat commented Feb 19, 2018

QA review completed: +15 points just awarded to @elenavolokhova/z, total is +15

@t-izbassar
Copy link
Contributor

@0crat status

@0crat
Copy link
Collaborator

0crat commented Feb 19, 2018

@0crat status (here)

@t-izbassar This is what I know about this job, as in §32:

marceloamadeu added a commit to marceloamadeu/takes that referenced this issue Jan 4, 2019
@0pdd
Copy link
Collaborator

0pdd commented Jan 4, 2019

@skapral the puzzle #935 is still not solved; solved: #802.

@0pdd
Copy link
Collaborator

0pdd commented Jan 16, 2019

@skapral all 2 puzzles are solved here: #802, #935.

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

No branches or pull requests

6 participants