Open nhekfqn opened 9 years ago
I am aware of the task, give me some time to find a developer...
@nhekfqn many thanks, 15 mins added to your acc for reporting this bug, pmt ID 51683468
@dmarkov Can I ask to assign this to me?
@apocarteres the issue is yours, please help
@tmjee the task is for you now, follow these guidelines. Don't hesitate to ask any technical questions right here... This task's budget is 30 mins. This is exactly how much will be paid when the problem explained above is solved. See this for more information
@dmarkov fixed in pull request #29
@nhekfqn Merged. Pls close this issue. Thx
@dmarkov fixed in pull request #29
@tmjee OK thanks
@prondzyn it's your task, go ahead
@dmarkov I reviewed history of this task, PR, and source code and this issue is already fixed adding extra checking.
Please see line: https://github.com/jcabi/jcabi-beanstalk-maven-plugin/blob/master/src/test/java/com/jcabi/beanstalk/maven/plugin/GenericMojoTest.java#L178
In meanwhile the problematic test was renamed and moved to GenericMojoTest class.
I will ask task author to close this ticket.
@nhekfqn please close the issue. It was already fixed in PR #29.
@nhekfqn ping
@dmarkov looks like author of this task is no longer active on GitHub - zero commits through last year. But the issue is fixed as I mentioned before. Can you close the task or do something about it?
@nhekfqn I'm asking once again, please close the issue. It was already fixed in PR #29.
@dmarkov still does not respond. What should I do with this task?
@dmarkov looks like author of this task is no longer active on GitHub - zero commits through last year. But the issue is fixed as I mentioned before. Can you close the task or do something about it?
@prondzyn sure
@dmarkov can you close the task?
@prondzyn this task is in your hands for 16 days already
added -30 to your rating, now it is equal to +60
@dmarkov why? I was asking you 10 days ago about closing this task:
@dmarkov looks like author of this task is no longer active on GitHub - zero commits through last year. But the issue is fixed as I mentioned before. Can you close the task or do something about it?
@prondzyn sure
@dmarkov please close the task
@dmarkov please close the task
@prondzyn thanks
@dmarkov this stinks. @yegor256 I know that you will say same as @dmarkov but please review history of this task and my comments. I reviewed it and contacted with an author but he is no longer active. I know the "no obligations" and other rules but there are some lack with them in some cases. Think about it.
@dmarkov this stinks. @yegor256 I know that you will say same as @dmarkov but please review history of this task and my comments. I reviewed it and contacted with an author but he is no longer active. I know the "no obligations" and other rules but there are some lack with them in some cases. Think about it.
@prondzyn @yegor256 could you please help us here?
That test does not actually check that exception is thrown. If no exception is thrown, assert will not be called and test will pass.