/explore
|
You are here 
|
andre.arko.net | ||
| | | | |
code.dblock.org
|
|
| | | | | The OpenSearch API specification is authored in OpenAPI and used to auto-generate OpenSearch language clients. I wanted to know how much of the API was described in it vs. the actual API implemented in the default distribution of OpenSearch that includes all plugins. To do so, I have exposed an iterator over REST handlers in OpenSearch core, and wrote a plugin that rendered a very minimal OpenAPI spec at runtime. All that was left was to compare the manually authored OpenAPI spec in opensearch-api-specification to the runtime one, added in opensearch-api-specification#179. The comparison workflow output a total and relative number of APIs described. | |
| | | | |
skerritt.blog
|
|
| | | | | Over in my Discord we have a cool bot called ?The Ultimate Hacking Bot? Really it's a bot that has a collection of pentesting tools one may find useful. With many tools come many issues... Dependency issues... If one of our many dependencies updated, our process was: 1. Update the | |
| | | | |
janik6n.net
|
|
| | | | | Run security scans on Terraform and OpenTofu project with Trivy and GitHub Actions | |
| | | | |
werat.dev
|
|
| | | Benchmarks are often underestimated and don't get the same attention as tests. However "performance is a feature" and when something is not tested it might as well be just broken. If the performance is not measured/tracked regressions are inevitable. Modern tooling makes it really easy to write benchmarks. Some languages have built-in support, for example, Rust comes with cargo bench (docs) and Go has go test -bench (docs). For C++ there is google/benchmark - not as streamlined as having it built into the language infrastructure, but still definitely worth the effort. | ||
