verify: ## verify minio various setups
	@echo "Verifying build with race"
	@GORACE=history_size=7 CGO_ENABLED=1 go build -race -tags kqueue -trimpath --ldflags "$(LDFLAGS)" -o $(PWD)/minio 1>/dev/null
	@(env bash $(PWD)/buildscripts/verify-build.sh)

verify-healing: ## verify healing and replacing disks with minio binary
	@echo "Verify healing build with race"

### Summary

I used to say I didn't like history that much... and look at me now giving "tech history" lessons. 😅

the defaults for the Go toolchain used to build the program,
amended to match the Go version listed in `go.mod`,
and then overridden by explicit `//go:debug` lines in the program.

The [GODEBUG History](#history) gives the exact defaults for each Go toolchain version.
For example, Go 1.21 introduces the `panicnil` setting,
controlling whether `panic(nil)` is allowed;
it defaults to `panicnil=0`, making `panic(nil)` a run-time error.

 * See https://www.jetbrains.com/help/teamcity/teamcity-data-clean-up.html#Clean-up+Rules
 *
 * @param historyDays days number of days to store build history .
 * @param artifactsDays number of days to store artifacts. In the stored history, artifacts older than this number will be cleaned up.
 * @param artifactPatterns patterns for artifacts clean-up. If not specified, all artifacts will be removed.
 */

See the [XDS Evolution](https://docs.google.com/document/d/1V5wkeBHbLSLMzAMbwFlFZNHdZPyUEspG4lHbnB0UaCg/edit) document for more history and details.

The `Workload` aims to represent everything about a workload (generally a `Pod` or `WorkloadEntry`).

- fastapi-people.md
- Resources:
  - resources/index.md
  - project-generation.md
  - external-links.md
  - newsletter.md
- About:
  - about/index.md
  - alternatives.md
  - history-design-future.md
  - benchmarks.md
- Help:
  - help/index.md
  - help-fastapi.md
  - contributing.md
- release-notes.md
markdown_extensions:
  toc:
    permalink: true

    "ignore:'cgi' is deprecated:DeprecationWarning",
    # For passlib
    "ignore:'crypt' is deprecated and slated for removal in Python 3.13:DeprecationWarning",
    # see https://trio.readthedocs.io/en/stable/history.html#trio-0-22-0-2022-09-28
    "ignore:You seem to already have a custom.*:RuntimeWarning:trio",
    "ignore::trio.TrioDeprecationWarning",
    # TODO remove pytest-cov

ASizes‘|¤Size|¥MTimeÓ É ¥— H§MetaSys ¼x-minio-internal-inline-dataÄ true§MetaUsr‚¤etagÙ cfc3c55bdcdef4cf23f6¬content-typeªtext/plain¡v ίFwÆ ¤nullÄ2 w ´zrETç™ËÝÜÆà áÎÅFHM!…JE¼wu?ÐngConfiguration> multisitea/data/disterasure/xl3/.minio.sys/config/history/38a3dbcb-a58f-4811-bf09-3bc6b7fbee05.kv/xl.meta XL2 Æ w Ä$•Ä Ó É ¸í80Ä yÅ Y Å Kƒ¤Type ¥V2ObjÞ ¢IDÄ ¤DDirÄ ‰ Z•`=A#µß ñN`áÚ¦EcAlgo £EcM £EcN §EcBSizeÒ §EcIndex ¦EcDistœ ¨CSumAlgo ¨PartNums‘ ©PartETagsÀ©PartSizes‘ ªPartASizes‘ ¤Size ¥MTimeÓ É ¸í80§MetaSys...

* Add translation to Portuguese for [History, Design and Future - História, Design e Futuro](https://fastapi.tiangolo.com/pt/history-design-future/). PR [#1249](https://github.com/tiangolo/fastapi/pull/1249) by [@marcosmmb](https://github.com/marcosmmb).

¡No! Esa no es la moraleja de la historia.

La concurrencia es diferente al paralelismo. Y es mejor en escenarios **específicos** que implican mucha espera. Debido a eso, generalmente es mucho mejor que el paralelismo para el desarrollo de aplicaciones web. Pero no para todo.

Entonces, para explicar eso, imagina la siguiente historia corta:

> Tienes que limpiar una casa grande y sucia.