-
Notifications
You must be signed in to change notification settings - Fork 69
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
add an exclude option to permitted subnets to exclude small chunks of a bit block #203
Comments
This seems to lead to a problem for me:
Weirdly enough, this only happens in a containerized version, when running in a venv ony my mac, it works flawless. |
Mhh, which python version are you running in your venv and which one in your docker container? |
Container (which throws the error) has |
very strange, actually no idea why there would be such a difference in behaviour between these two environments |
What do you suggest? I'm pretty sure this feature is the cause, if I check out the commit before this commit, it works. |
Hi, I just pushed another commit. I'm certain I found the issue. Can you check out the latest Thank you |
Unfortunately still the issue, I'm sure i checked out the latest commit from the development branch.
|
Hi, did you pull the latest container or did you build a new container from the source and used this one? |
Built a new container from source. Dockerfile looks like this: Edit: |
mmhhh, I pushed another commit. Could you try this one again? thank you |
wheee 👍 , works this time. Thanks so much! One thing I noticed and where i'm not sure if this is related to the code changes in this issue or if it is something independent:
|
Great to hear. Will have a look into ps naming tomorrow. |
Hi @Eldiabolo21, took a bit longer then just a day. I just pushed a commit to "development". Can you test it out? Thank you |
exclude subnets with a leading
!
suggestion:
permitted_subnets = 172.16.0.0/12, 10.0.0.0/8, !10.8.0.0/24
The text was updated successfully, but these errors were encountered: