Skip to content
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

chore: aggressive dns caching approach #32

Merged
merged 4 commits into from
Jan 23, 2025

Conversation

GangGreenTemperTatum
Copy link
Contributor

@GangGreenTemperTatum GangGreenTemperTatum commented Jan 22, 2025

context: accidental commit to main here which was immediately reverted

this is a development PR to close #31 which is currently in further testing - i'm going to automate this with scripts and run multiple concurrent runs websites using the selenium loader to be confident going forward

the PR as per this comment (see Update debug:) specifically tries to not significantly reduce our ability to trace, but remove any non-critical functionality which can relate to DNS caching, general Google caching or problematic chrome functionality which is highly probable to hangs and therefore 💀 containers.. current changelog:

  • added more aggressive DNS and cache control flags
  • added network logging capabilities
  • track DNS resolution timing
  • added browser logs capture
  • disabled Chrome's logging to stderr which can interfere with tracing

@GangGreenTemperTatum GangGreenTemperTatum marked this pull request as draft January 22, 2025 21:22
@GangGreenTemperTatum
Copy link
Contributor Author

for visibility, im testing with a script like so (not entirely robust) -> 679f305, as well as some manual tracing

i'll gather some test case scenario's and also ask a few others to test and try to replicate for any errors on this branch

@evilsocket evilsocket marked this pull request as ready for review January 23, 2025 11:12
@evilsocket evilsocket merged commit 9090fa8 into main Jan 23, 2025
3 checks passed
@GangGreenTemperTatum
Copy link
Contributor Author

thank you for fixing my poor linting and typescript verification @evilsocket 😂 ❤️

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.

[BUG] container timeouts and no dns traffic for website loader
2 participants