-
-
Notifications
You must be signed in to change notification settings - Fork 580
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
nameserver: discover nameserver within environment of this host #741
Conversation
Please let me know if documentation is needed or unit tests. If you would like tests, let me know where to read and I'll jump on that. Thanks! |
I figured this out: https://github.com/BC-SECURITY/Empire/blob/main/.github/CONTRIBUTING.md#code-formatting-and-linting |
Evidence of linting:
There seems to be a problem with pytest. When running a pytest, including on older versions, I am getting errors. I also ran the docker-compose.yml tests from the .github workflow, they fail as well. Also note, |
Snippet of errors from pytest, they seem to be the same in docker compose and poetry:
|
@BuildAndDestroy The important part for debugging the pytest errors is below the summary, if you want to share that I can see if it looks familiar. Regardless, we don't currently require testing specific modules. The code looks fine to me, so if the CI passes we can merge it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just needs an update to the changelog
Co-authored-by: Vincent Rose <vrose04@gmail.com>
Seems the author name is being interpreted as byte data using the GitHub install.
As soon as the bug was fixed, pytest completes without issue:
We should be good to run the workflow |
Looks like we skip Pytest coverage comment in Test Python 3.10 but we run in Test Python 3.12. Is there a manual way to run this locally? I assumed this would have been under Also commented this on the other pull request, we are hitting the same in PR 742. |
I was able to track this down in the Workflow file:
Ran this locally with sudo, most of ther Failures went away except for 1:
Looking through the log output:
Permission error. Odd since I am running sudo and this is in /tmp/ and the file permissions are my lower level user:
So I went back and modified perms:
Looks like this resolved the Failures:
As for the poetry test, we are reading the same in the workflow as we are locally, so this may not be the problem. We can see the next test is sqlite. Let's run it:
No Errors heres. Seems to be a problem with the Workflow. If a resource is not accessible by the integration, is it really an error or a warning that can be skipped? |
* nameserver: discover nameserver within environment of this host * CHANGELOG.md: Update the changelog * fixit! Add CHANGELOG.md verbiage that was removed * Update CHANGELOG.md Co-authored-by: Vincent Rose <vrose04@gmail.com> * fixit! Update author name as string Seems the author name is being interpreted as byte data using the GitHub install. --------- Co-authored-by: Vincent Rose <vrose04@gmail.com>
…vate v5.8.2 into private-main
Describe your changes
Add a nameserver check for Linux hosts.
Issue ticket number and link (if there is one)
Checklist before requesting a review
CHANGELOG.md
docs/
(if applicable)