olix0r
Follow
Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 50 million developers.
Sign up
Pinned
1,235 contributions in the last year
Activity overview
Contribution activity
November 2020
Created 55 commits in 7 repositories
Created 8 repositories
- olix0r/h2 Rust
- olix0r/hyper Rust
- olix0r/http Rust
- olix0r/http-body Rust
- olix0r/tonic Rust
- olix0r/linkerd2 Go
- olix0r/linkerd2-proxy Rust
- olix0r/audit-check TypeScript
Created a pull request in hyperium/hyper that received 8 comments
Update bytes to v0.6
Depends on: hyperium/h2#497 hyperium/http-body#29 hyperium/http#440
+19
−7
•
8
comments
Opened 25 other pull requests in 11 repositories
linkerd/linkerd2-proxy
3
open
5
merged
- outbound: Avoid redundant TCP endpoint resolution
- Ver/connection header
- io: Set a minimum detect buffer size
- actions: Add timeouts to GitHub workflows
- outbound: Skip endpoint resolution on profile hint
- Update *ring* and rustls dependencies
- http: Configure client connection pools
- Allow specifying the number of available cores via the env
linkerd/linkerd2
1
open
6
merged
olix0r/ort
2
merged
linkerd/linkerd2-proxy-api
1
merged
tokio-rs/tokio
1
merged
hyperium/h2
1
closed
hyperium/http-body
1
closed
hyperium/tonic
1
open
hyperium/http
1
closed
danburkert/prost
1
closed
BuoyantIO/emojivoto
1
merged
Reviewed 15 pull requests in 4 repositories
linkerd/linkerd2 10 pull requests
- Update ADOPTERS.md M1 Finance
- Remove logs comparisons in integration tests
- Increase ARM integration test timeout
- edge-20.11.2
- Update BUILD.md with multiarch stuff and some extras
- cli: Remove get cmd and relevant tests
- Add "The Zebra" to ADOPTERS.md
- Add Doji to adopters
- nit: return crtExpiry even for External Certs
- Add changes for edge-20.11.1
linkerd/linkerd2-proxy 2 pull requests
linkerd/linkerd2-proxy-init 2 pull requests
linkerd/linkerd2-proxy-api 1 pull request
Created an issue in linkerd/linkerd2 that received 6 comments
Validate that cpu-limit actually restricts proxy CPU allocations
Anecdotally (in k3d) I've noticed that when setting a proxy cpu limit of "1", the proxy can still consume many cores worth of resources. The proxy …
6
comments
Opened 11 other issues in 1 repository
linkerd/linkerd2
9
open
2
closed
- `edges` does not include identities on proxy prometheus scrapes
- Proxy admin server should expose metrics
- Move `check --multicluster` to `multicluster check`
- Modularize a linkerd-viz extension
- Document the destination controller's contract
- Move sp-validator into the `destination` controller
- cli: Support CLI plugins
- cli: Remove the `install-sp` subcommand
- cli: Reorganize diagnostic subcommand(s)
- cli: Remove `logs` subcommand
- cli: Remove `get` subcommand