Rework Gun connection pooling #7934
No reviewers
Labels
No labels
AP C2S
AdminAPI
Breaking API
Breaks existing config
Check if still valid
Data Protection
Do not merge
Document in the changelog
Doing
Feature Request / Enhancement
MastoAPI
NL2
NL4
OStatus
OTP Releases
Refactor
Security
To Do
TwitterAPI
bug
complicated
confirmed
deps
discussion
documentation
easy
feature: to be merged in stable
fix: to be merged in stable
incident
needs to be backported to maint
needs-changes
needs-info
needs-review
performance
regression
unclear
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pleroma/pleroma!7934
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-2263-gun-validation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Closes #2263
Relates #7834
Gun 2.4 review
Testing
mix test --seed 0(4881 tests, 0 failures, 2 excluded, 4 skipped)mix test --seed 0(4881 tests, 0 failures, 2 excluded, 4 skipped)22 tests, 0 failures)mix format --check-formattedgit diff --checktools/check-changelogwithCI_COMMIT_TARGET_BRANCH=developmix credo --strictcompletes; the repository has an existing strict backlog and reports non-blocking style/complexity advisories in touched filesAll of these configs are broken likely due to some auth bug:
The string representation uses Squid as a forwarding proxy without any authentication and all plain HTTP requests (non-TLS) result in
{:error, :unauthorized}being returned and this in Squid access logs:The socks5 tuple representations always returns
{:error, :eacces}.Only the string representation works in Hackney as well.
Did you run this standalone or on top of the other MR? can't reproduce the non-squid issues.
They are merged on top of each other (this one last). I'm able to reproduce the issue only on my main instance using OTP builds, but test instance running a source install works fine with all three config options. Weird.
EDIT: Gah, nevermind. The tuple issue was caused by SELinux denying access to the Tor port. Sorry, all three work fine now for the HTTP client.
WIP: Rework Gun connection poolingto Rework Gun connection poolingRunning this on lain.com, so far seems to work normally. If you don't see anything bad, I'd merge it soon.
I've made a few small nitpicky notes, but haven't found anything wrong per-se. Better not to monkey with something that works at this time.
Drop the
DEVLOG.mdfrom history and feel free to merge.