ui / server mode: make thread safe #22
Comments
ldemailly
added a commit
that referenced
this issue
Nov 24, 2017
Fixes most of #22 Except for the http.go client headers
ldemailly
added a commit
that referenced
this issue
Nov 27, 2017
… allow save/retrieve/graph saved data (#37) * Move result -> chart logic entirely in javascript So a page can directly graph a fortio JSON Also added the version in the virtual static prefix (so fortio upgrades/version bump yield a reload of the code) * Update webtest for version in path * Fixed thread safety of all periodic/runner* Fixes most of #22 Except for the http.go client headers * Increases stats/ coverage * Fixed JS formatting * Fixed the last client thread safety Which was about headers * Added new nolint: gas * Accelerate the build and made an image for linters Fixes #36 * Use our own build image * Rename data dir to resources dir (data dir will be where we save) * Adding gcc to build image get -race test and libc-dev to get linters * Limit concurrency to not explode on circleci * Data can now be saved and fetched/graphed later Default data dir is /var/lib/istio/fortio * Bumping to 0.4.0 Given the big changes in this PR (and then we’re early for Dec release) * Fixed hanging case with chunked mode when the last read covered more than 1 chunk, which happens at the moment with the main url. Fortio was doing 1 more read and hanging Added option to change debug level in webtest * Fixing refactoring bug And adding a test * Adding safe ID() to put alphanumeric part of Labels in file name * Linter/spelling * Code review comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: