-
Notifications
You must be signed in to change notification settings - Fork 32
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
🐛 fix issue 34 when running Pi-Hole in Docker Container #40
Conversation
Checks won't fail any more after PR #37 has beeen finished/done… |
I'm not convinced if this is really a working solution. If it takes hours this is nothing I'd like to ship to users |
Does it really work? I did not test it, but expect it to fail also here: pihole_adlist_tool/pihole_adlist_tool Line 1006 in 890f454
|
I reviewed and a fix will come…
You are right, do not merge this until we have an optimized version! |
💡 This is working with limit of 2000 (distinct) domains, but limited due to "Argument list too long". This array should be splitted by for example 500 domains and regex-tested in packages…
❓ Which counts are relevant for the regex-mode?
|
All regex (number not shown) are checked against the 2980 distinct domains |
@yubiuser , I changed my commit / PR: This PR will disable regex-analysis when Pi-hole is running in a docker container and tells user about this. So Regex analysis is still not supported on docker, but script isn't doing anything worthless/useless stuff anymore. Do you agree? |
I also added a .stickler.yml 😉 |
The difficulty is that we have an unknown and possibly very big list of domains that we have to pass to the docker container for regex-checking. I really have no clue how to solve this efficiently… 🤷🏻♂️ |
I agree that we should probably disable regex-checking if Pi-hole is running on docker as long as we do not have a better solution. Please remove the stickler stuff from this PR. I'm happy to include it, but don't mix unrelated changes in one PR |
I couldn't find a |
…ned a string. adapt suggestion Co-authored-by: yubiuser <[email protected]>
Co-authored-by: yubiuser <[email protected]>
Co-authored-by: yubiuser <[email protected]>
Co-authored-by: yubiuser <[email protected]>
Co-authored-by: yubiuser <[email protected]>
Co-authored-by: yubiuser <[email protected]>
Is this PR now ready for a merge? Or do you want a single commit rebased to commit 890f454 ? |
Co-authored-by: yubiuser <[email protected]>
I guess best would be a rebase on current development. Please also target development. Do not modify |
|
Whats's about the changes in line 859 and above? |
Something went wrong during rebase I guess. These changes were introduced in your other PR but later reverted. |
I fixed the rebase now. |
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.
I can't test currently because I don't have a docker installation right now. But the code change seems right
I'll add a final test later (in/after the lunch-break possibly)… |
I just decided that it looks Ok ;-) |
Short coffee-break before next meeting 😜
|
This PR will fix issue #34 by disabling regex-check when running Pi-hole in Docker Container 😁
To be honest to the user, we will print this info in options and when running 👍🏻