Skip to content

issue 2828 fix #2949

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

Conversation

PrakashDurlabhji
Copy link
Contributor

@PrakashDurlabhji PrakashDurlabhji commented Jul 18, 2019

#2828 fix

@codeMinter
Copy link
Contributor

@PrakashDurlabhji please fix all issues before marking ready for review.

@codeMinter codeMinter assigned codeMinter and unassigned codeMinter Jul 19, 2019
@codeMinter codeMinter self-assigned this Jul 23, 2019
@codeMinter
Copy link
Contributor

@PrakashDurlabhji doesn't looks like we have tab enabled for Prizes. I have tried this on Windows and Mac both, there is no tab for Prizes. We need to enable tab for Prizes too.

@PrakashDurlabhji
Copy link
Contributor Author

@codeMinter updating it

@codeMinter
Copy link
Contributor

@PrakashDurlabhji Please flag where are we on this? I will wait for next 4 hrs for new PR with fix, after which will need to open this for others.

@PrakashDurlabhji
Copy link
Contributor Author

@codeMinter just a minor change it should be update in few minutes

@PrakashDurlabhji
Copy link
Contributor Author

@codeMinter @veshu PR updated

@veshu
Copy link
Contributor

veshu commented Jul 25, 2019

@PrakashDurlabhji Please check the tests are failing.

@codeMinter
Copy link
Contributor

codeMinter commented Jul 26, 2019

@PrakashDurlabhji any reason why you add role="button" ? It reads the prize and then reads button - prizes are not buttons

@PrakashDurlabhji
Copy link
Contributor Author

@codeMinter i guess link will do.

@PrakashDurlabhji
Copy link
Contributor Author

@codeMinter Pr updated

@codeMinter
Copy link
Contributor

@codeMinter i guess link will do.

It is neither a link. I will research and suggest what should it be, but I guess since you are working on it, please can you look up Accessibility guidelines what you do for labels? It is just a label.

Going ahead, please do not mark for review unless everything is GREEN on PR, you might loose access to this repo else.

@PrakashDurlabhji
Copy link
Contributor Author

@codeMinter sorry for it, I will make sure it wont happen again, but link shall do I feel

@veshu
Copy link
Contributor

veshu commented Jul 28, 2019

@PrakashDurlabhji Your fix is breaking on automated test, please ensure they are passing. Thanks!

@codeMinter
Copy link
Contributor

@PrakashDurlabhji do not assign ticket to yourself, you cannot keep ticket forever.

@codeMinter codeMinter closed this Jul 29, 2019
@PrakashDurlabhji
Copy link
Contributor Author

@codeMinter ya I understand I cannot keep ticket myself, but isnt this working as expected?

@codeMinter
Copy link
Contributor

@PrakashDurlabhji plz do not open PRs for tickets not owned by you

@PrakashDurlabhji
Copy link
Contributor Author

@codeMinter i want to check how can my PR failed while code is same, I wont link this PR to issue. I want to see how circleCI can behave weirdly

@PrakashDurlabhji
Copy link
Contributor Author

@codeMinter let me see circleCI build job now. I will close PR again after that.

@codeMinter
Copy link
Contributor

@PrakashDurlabhji run it locally. You cannot open PR and push commits, you are putting unnecessary load on our servers.

@codeMinter codeMinter closed this Jul 29, 2019
@PrakashDurlabhji
Copy link
Contributor Author

PrakashDurlabhji commented Jul 29, 2019

@veshu waiting for your take on above issue. where a person delibaterly takes someone else issue which is made open, while he could have taken other issues which are open, though previous feedbacks are already pending for his current going issue, and PR is copied too.
Did not experience such biased decisions by reviewers
issue which was already in pending feedback by rohit, comments can be checked there too:
#2814

@codeMinter @r0hit-gupta

@crazyk07
Copy link

crazyk07 commented Jul 29, 2019

Hi @PrakashDurlabhji, there seems to be a misunderstanding here and Rohit has wrote an explanation in the ticket you are discussing. Our reviewers are just following procedure with code reviewing, I currently do not detect any bias. There could have been something procedural that was overlooked (Since we are dealing with 170 tickets initially), but there is nothing intentional here. If you want to discuss further, please raise a ticket with topcoder support and tag me onto the message ([email protected]). Would prefer to move the conversation outside this thread for better accountability. I have a low likelihood of responding within github due to the high volume of tickets we are looking at.

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

Successfully merging this pull request may close these issues.

5 participants