na--
I think that's because I have WINE installed in the Archlinux VMs, since that's what gets started when I run ./redbean.com. But even after I remove WINE, it still doesn't work, I probably have to restart (i.e. remove WINE from the TemplateVM, not the AppVM) for it to work.
In any case, incredible work, I am in awe!
It has been a while since I watched these Gil Tene talks, so I might be missing something, but I think the only remaining task we have is to adopt something like his HDR histogram library [2]. And that's mostly for performance reasons, though we'll probably play around with the correction logic as well.
You can export HAR files from all web browsers and a lot of proxies and other tools. Then you can convert that recording to a k6 script with our HAR converter: https://k6.io/docs/test-authoring/recording-a-session/har-co...
We also have browser plugins to directly record browser traffic and import it as a k6 script in our cloud service: https://k6.io/docs/test-authoring/recording-a-session/browse...
However, you don't need a cloud subscription to run the tests, you can copy-paste the generated script code and `k6 run` it locally, without paying us anything.
See the example in https://github.com/loadimpact/k6/#checks-and-thresholds. If, at the end of the test run, some of these rules (encoded as `thresholds`) were unsatisfied, k6 will exit with a non-zero exit code (and thus fail your CI check): - The 95th percentile of all HTTP request durations should be be less than 500ms - The 99th percentile of all HTTP request durations that were tagged with `staticAsset:yes` should be less than 250ms - The failure rate of the checks should be less than 1%, although if it's more than 5% the test will abort immediately.
> tests that would run much much more often (like every seconds or couple of seconds), in a continuous manner.
You can do that, just use an arrival-rate executor that runs an iteration every second, with a test duration of 365 days or something like that :) See https://k6.io/docs/using-k6/scenarios/arrival-rate
> Tue goal was to have something at the same time like a healtcheck (is it still working), like a performance test (does it answer in a timely manner) and like a validation test (does it answer the right result - the endpoints we wanted to test do "complex calculations"). Our best answer so far was to wrap K6 in an infinite loop, but I wonder if there could be something smarter.
You can certainly wrap k6 in an infinite loop. Nothing wrong with that, though you can probably use the `scenarios` feature (with long `duration` values) to achieve it without wrapping k6: https://k6.io/docs/using-k6/scenarios
Regarding debugging, that's unfortunately unlikely to come any time soon... We'd need support for that in the JS runtime we're using (https://godoc.org/github.com/dop251/goja) and then we'd need to figure out how to expose in in k6, while dealing with potentially hundreds of concurrent JS runtimes (VUs). Not impossible, just unlikely to land anytime soon...
You can find some basic performance and other comparisons between load testing tools in this very long article of ours: https://k6.io/blog/comparing-best-open-source-load-testing-t...
And some advice for squeezing the maximum performance out of k6 in here: https://k6.io/docs/testing-guides/running-large-tests
I'm someone who has read that story, at least the public parts of it, and I object slightly to your quality assessment... ;) I don't argue it's great literature or anything, more like the literary equivalent of popcorn - a fun and interesting story with not a lot of depth. So, entertainment, not life-changing prose...
And while I'm surprised he gets $13k a month, I'm not _very_ surprised. I'm one of his $1/month patrons, and I also give $1-$3 a month to a lot of other writers, YouTubers, and other creators. For another internet serial writer, see https://www.patreon.com/Wildbow
One of my criteria for supporting such creators is for them to make their creations public, even if some do it after a time delay. My rationale is that, this way, I both support the creators, and the creation of "culture", for a certain definition of that word, that other people would be able to enjoy for free. And while this might never replace traditional publishing and isn't suitable for everything, you've demonstrated that some people can certainly make a living this way.
Remote: Yes
Willing to relocate: Unlikely
Technologies and skills: Go, Linux, DevOps, Rust (currently learning), Bash, JavaScript, PHP, Data Wrangling and others (see CV timeline)
Résumé/CV: https://cv.andreev.sh/ (print to PDF for a concise normal-looking CV)
Email: [email protected]
Highly skilled generalist developer with more than 12 years of diverse work experience. Interested in security, DevOps, and data wrangling. Currently striving to master Rust and machine learning with Python. Seeking professional opportunities, especially to work on intriguing open source projects.
Remote: Yes
Willing to relocate: Unlikely
Technologies and skills: Go, Linux, DevOps, Rust (currently learning), Bash, JavaScript, PHP, Data Wrangling and others (see CV timeline)
Résumé/CV: https://cv.andreev.sh/ (print to PDF for a concise normal-looking CV)
Email: [email protected]
Highly skilled generalist developer with more than 12 years of diverse work experience. Interested in security, DevOps, and data wrangling. Currently striving to master Rust and machine learning with Python. Seeking professional opportunities, especially to work on intriguing open source projects.