Skip to content

Update Maintainers and Contributors file for overassigning issues #481

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

TimOsahenru
Copy link
Contributor

No description provided.

Copy link
Contributor

@kjaymiller kjaymiller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TimOsahenru great work on this.

I made a note that needs to be address in the wording around working on multiple PRs at the same time. Please resolve that.

CONTRIBUTING.md Outdated
@@ -38,6 +38,8 @@ Follow these steps and note these guidelines to begin contributing:

## Working on an issue

- As a first-time contributor, please do not request assignment to more than one issue at a time, except in rare scenarios where the issues are closely related.
- As a returning contributor, ensure that you do not have an open pull request before requesting assignment to a new issue. Your pull request from a previous issue must be reviewed and merged first.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think that it's a problem that you work on multiple issues. I think the problem arises when second PR references changes in the first PR...

For instance:

  • A USER edits a file
  • The same USER wants to submit another PR but is working on the same branch as the file with changes.
  • The MAINTAINER requests changes on the first PR which now need to be made on the second PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gotcha!

@TimOsahenru
Copy link
Contributor Author

@kjaymiller I've implemented the requested changes, but I get a failing test when I run pytest. I've already pulled the latest changes from upstream. I think I understand the error message, but I'm struggling to find a solution, LOL. Please help. Thanks
image

@kjaymiller
Copy link
Contributor

I pulled down changes and I'm not running into that issue.

can you run pre-commit run -a?

@kjaymiller
Copy link
Contributor

@TimOsahenru - There may have been a push recently so try another pull of changes.

I don't think any of that changed the _conferences section.

@kjaymiller
Copy link
Contributor

@kjaymiller I've implemented the requested changes, but I get a failing test when I run pytest. I've already pulled the latest changes from upstream. I think I understand the error message, but I'm struggling to find a solution, LOL. Please help. Thanks image

I ran into a similar issue that I noticed doesn't happen when you do python -m pytest I wonder if there is a namespace thing that we're doing.

@TimOsahenru
Copy link
Contributor Author

I've been worked on this bug, still no headway from my end. Previously, I've always ran our test case with python -m pytest. After this change 56e317b I noticed that running either pytest or python -m pytest now causes almost all of our tests to fail

@kjaymiller
Copy link
Contributor

@TimOsahenru - I'm not sure as I can't replicate the issue.

@TimOsahenru
Copy link
Contributor Author

@TimOsahenru - I'm not sure as I can't replicate the issue.

Certainly it's from my end then

@TimOsahenru
Copy link
Contributor Author

is it okay to make a push regardless ?

@TimOsahenru
Copy link
Contributor Author

Finally got the tests to pass by slapping anything to the wall, hoping something sticks:

  • Extending kill time by 20
  • Adding port number while spinning server
  • Turning off network 😂
  • Running command in CMD instead of my editor's terminal.
    Just documenting this here in case anyone else runs into similar issues!

@kjaymiller
Copy link
Contributor

Wow that's a lot of things to get going but great troubleshooting. If you continue to have issues we need to look at our setup. There are a lot of things happening. Maybe we can simplify them somehow.

@kjaymiller kjaymiller self-requested a review October 1, 2024 16:36
@kjaymiller kjaymiller merged commit 4091aa5 into BlackPythonDevs:gh-pages Oct 1, 2024
2 checks passed
@TimOsahenru
Copy link
Contributor Author

Wow that's a lot of things to get going but great troubleshooting. If you continue to have issues we need to look at our setup. There are a lot of things happening. Maybe we can simplify them somehow.

agreed

@TimOsahenru TimOsahenru deleted the update-maintainers-and-contributors-file-for-overassigning-issues branch March 21, 2025 10:14
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

Successfully merging this pull request may close these issues.

2 participants