Skip to content

Releases: fortio/fortio

Fortio 1.57.3

12 Jul 23:31
c1c5e58
Compare
Choose a tag to compare

What's Changed

  • Rebuilt with go 1.20.6 (security fix)

(1.57.1 and .2 were miss build due to #793 / docker ce upstream image error)

Full Changelog: v1.57.0...v1.57.3

Fortio 1.57.0

07 Jul 02:53
6a72267
Compare
Choose a tag to compare

What's Changed

  • Update to color supporting version of log/cli/scli console/terminal logs are now colorized by default (JSON when redirected unless changed by flags) by @ldemailly in #789

Full Changelog: v1.56.0...v1.57.0

Fortio 1.56.0

04 Jul 02:53
8890d97
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.55.2...v1.56.0

Fortio 1.55.2

27 Jun 02:36
c39b74f
Compare
Choose a tag to compare

What's Changed

#782

Switch to new log 1.5.0 format where the timestamp is (float64) sec.usec instead of a large (int64) usec since unix epoch {like uber zap}

https://github.com/fortio/log/releases/tag/v1.5.0

Update / use scli with flag (-logger-timestamp=false) for not logging TS (and not doing JSON under a new name, was -json-log=false, now -logger-json=false)

https://github.com/fortio/scli/releases/tag/v1.6.0

Requires logc 1.1.0 or newer to parse the new log format back to colorized text

https://github.com/fortio/logc/releases/tag/v1.1.0

Full Changelog: v1.55.1...v1.55.2

Fortio 1.55.1

21 Jun 23:02
b80d012
Compare
Choose a tag to compare

What's Changed

  • Use fixed log package for log.Printf, remove bogus \n in log.Printf (#775)
  • Change all the http client logs (info level and up) to structured (#778)

Full Changelog: v1.55.0...v1.55.1

Fortio 1.55.0

15 Jun 00:11
7d76c8e
Compare
Choose a tag to compare

What's Changed

  • Big change is to be using JSON structured logging (unless calling -json-log=false) (#768)
    • Also add log-errors=on option setting to rest api and web UI
    • Also add the runid to the structured logs (run=...) so errors from specific runs can be identified even if more than one are currently running

Structured JSON logging is coming from fortio.org/log 1.4.0 / fortio/log#22 - it includes http request logging in that format too (log.LogRequest)

Other changes:

  • go1.20.5 build image (#762)
  • dependency updates

Full Changelog: v1.54.3...v1.55.0

Fortio 1.54.3

03 May 03:03
c6665d1
Compare
Choose a tag to compare

What's Changed

  • Rebuilt with Go 1.20.4 (#755)
  • Remove non idiomatic use of new() and use recommended var buf bytes.Buffer directly (#751)
  • Dependency updates

Full Changelog: v1.54.2...v1.54.3

Fortio 1.54.2

14 Apr 00:54
42273f0
Compare
Choose a tag to compare

What's Changed

  • Fix long standing boundary condition rare bug with histogram buckets (in #746)
  • Fix error handling so passing an invalid -payload-file cause fortio to not proceed with curl/load test (abort, fixes #748 )
  • Dep updates

Full Changelog: v1.54.1...v1.54.2

Fortio 1.54.1

06 Apr 15:47
e3eb219
Compare
Choose a tag to compare

What's Changed

  • Use newer go 1.20.3 (security fixes plus switch from 1.19) and corresponding new lints(#743)

Note the linter identified an incompatible change needed:

func HandleCall[Q any](w http.ResponseWriter, r *http.Request) (*Q, error) {

to

func ProcessRequest[Q any](r *http.Request) (*Q, error) {

as HandleCall doesn't... handle it just unserializes. kept the old api as Deprecated for now.

Full Changelog: v1.54.0...v1.54.1

Fortio 1.54.0

20 Mar 18:57
69ae5d0
Compare
Choose a tag to compare

What's Changed

  • New Dns debug endpoint /fortio/rest/dns?name=xxx and in the UI form as well (#735)
$ curl -s localhost:8080/fortio/rest/dns?name=debug.fortio.org | jq

yields

{
  "Name": "debug.fortio.org",
  "IPv4": [
    "18.222.136.83",
    "192.9.142.5",
    "192.9.227.83"
  ],
  "IPv6": [
    "2600:1f16:9c6:b400:282c:a766:6cab:4e82",
    "2603:c024:c00a:d144:7cd0:4951:7106:96b8",
    "2603:c024:c00a:d144:6663:5896:7efb:fbf3"
  ]
}

Full Changelog: v1.53.1...v1.54.0