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.

Sign up for GitHub

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

Jump to bottom

fortio improvements #453

Closed
8 of 19 tasks
ldemailly opened this issue Jul 5, 2017 · 6 comments
Closed
8 of 19 tasks

fortio improvements #453

ldemailly opened this issue Jul 5, 2017 · 6 comments
Milestone
0.3

Comments

@ldemailly
Copy link
Contributor

ldemailly commented Jul 5, 2017 •
edited

Some next steps for fortio once #445 is in:
Done (in #470)

Remaining:

  • ^C support to stop / option to run continuously until ^C
  • a request id in either headers or query arg or both
  • calculate bytes sent/received including headers (to be researched)
  • h2 testing (h2 benchmark (end to end) #452)
  • struct, json or other structured output for the histogram
  • graph (picture) generation
  • go over the TODOs
  • consider passing a context and/or using channels
  • warm up time
  • payload option (exists in grpcping)
  • evaluate/use https://github.com/spf13/cobra
@ldemailly ldemailly mentioned this issue Jul 7, 2017
Merged
@ldemailly
Copy link
Contributor Author

chart 1
chart with echosrv - will ref in readme

@ldemailly ldemailly mentioned this issue Jul 15, 2017
Merged
@ldemailly
Copy link
Contributor Author

4 more items [x] in #470

@ldemailly
Copy link
Contributor Author

grpc in #519

@ldemailly
Copy link
Contributor Author

7.83MB single binary image doing both http and grpc server and clients in #546

@ldemailly ldemailly added this to the Istio 0.3 milestone Sep 29, 2017
@ldemailly
Copy link
Contributor Author

added ^c support request

@ldemailly ldemailly mentioned this issue Oct 12, 2017
Closed
14 tasks
@ldemailly
Copy link
Contributor Author

moving to fortio/fortio#2

mandarjog pushed a commit to mandarjog/istio that referenced this issue Oct 30, 2017
@ZackButcher
Update ConfigErrors.Extend so that nil.Extend(nil) == nil. (istio#453)
4013ac3 
Previously such a call would return a zero-value ConfigErrors, breaking the standard `if ce := foo(); ce != nil { ... }` if ConfigErrors.Extend was used anywhere during the construction of the error in `foo` (or any of the methods it calls, transitively).

Former-commit-id: fe4de8be19dc07b25c32029b549617f6a4b5a509
mandarjog pushed a commit that referenced this issue Oct 31, 2017
@ZackButcher
Update ConfigErrors.Extend so that nil.Extend(nil) == nil. (#453)
ce0e47a 
Previously such a call would return a zero-value ConfigErrors, breaking the standard `if ce := foo(); ce != nil { ... }` if ConfigErrors.Extend was used anywhere during the construction of the error in `foo` (or any of the methods it calls, transitively).

Former-commit-id: 940c9ebcb6743d6d99ee05954acc3c3d948abc87
kyessenov pushed a commit to kyessenov/istio that referenced this issue Aug 13, 2018
@qiwzhang
update to mixer client with quota cache change. (istio#453)
37a29e1
howardjohn pushed a commit to howardjohn/istio that referenced this issue Jan 12, 2020
@dgn @istio-testing
Charts for: Custom root certificates for JWKSResolver (istio#17176) (i…
fe4a478 
…stio#453)
danehans pushed a commit to danehans/istio that referenced this issue Nov 2, 2021
@mathetake
Fix human error (istio#453)
fa497cc 
Signed-off-by: Takeshi Yoneda <takeshi@tetrate.io>
antonioberben pushed a commit to antonioberben/istio that referenced this issue Jan 29, 2024
@pie-r
[jaeger] istio#452 support initContainers (istio#453)
f8412bb 
* feat: istio#452 support initContainers

Signed-off-by: Pier <53210578+pie-r@users.noreply.github.com>

* missing if

Signed-off-by: Pier <53210578+pie-r@users.noreply.github.com>

---------

Signed-off-by: Pier <53210578+pie-r@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.3
Development

No branches or pull requests
1 participant
@ldemailly