fix: WARCWritingClient nil ptr dereference#581
fix: WARCWritingClient nil ptr dereference#581AltayAkkus wants to merge 1 commit intointernetarchive:mainfrom
Conversation
| clients = append(clients, c) | ||
| } | ||
| globalArchiver.Client.Timeout = config.Get().HTTPTimeout | ||
| } |
There was a problem hiding this comment.
Removed because it used nowhere, and with one .Client we won't need any GetClients() shorthand soon
|
I checked if the Proxy is actually used by adding |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #581 +/- ##
==========================================
+ Coverage 56.46% 56.67% +0.20%
==========================================
Files 133 133
Lines 6742 6712 -30
==========================================
- Hits 3807 3804 -3
+ Misses 2556 2533 -23
+ Partials 379 375 -4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
This is very interesting - there was once a concept of proxied requests and non-proxied requests in one Zeno client, the idea being we could specifically route some traffic over a proxy and some not based on simple domain rules, I suppose over some of our rewrites, this got a little lost, so this is technically the correct fix but misses the initial intentions behind Let me talk with @willmhowes to see if we can recommend something specific here. |
|
That makes sense! #136 proposed mapping tlds -> proxies (!). If I understood Corentin right, that would mean that you can map I would throw another wish into the pot, I would like to use a proxy to retry items that failed with We could all crawl in peace & happiness if we were able to define a Proxy on a per-request level with This sunday I wasted about 6 hours of my life on trying to implement HTTP/2 in |
|
Implemented per-request proxy definition with gowarc's HTTP client in internetarchive/gowarc#186 After due diligence & review we MAY continue here. https://github.com/Icheka/go-rules-engine Or we build something else on our own. The rules are evaluated in the Zeno/internal/pkg/archiver/general/archiver.go Lines 59 to 75 in ce2eb77 Depending on the outcome of the evaluation, we add the |


See #580