mirror of
https://github.com/trezor/trezor-firmware.git
synced 2024-10-18 13:59:17 +00:00
0e650b1a5b
There's two udp calls in `UdpTransport._ping()`: - socket.sendall(b"PINGPING") -> this will be instanteous, AND it will raise if the receiving side is not listening. - socket.recv() -> this will wait for SOCKET_TIMEOUT seconds, but only in case the sendall() succeeded. This means that receiving side exists and we are now waiting until it's awake enough to respond. In conclusion, we avoid hammering emulator with PINGPINGs with a timeout so short we don't see an answer. This should avoid the problem occasionally seen in CI and described in #1668 |
||
|---|---|---|
| .github | ||
| ci | ||
| common | ||
| core | ||
| crypto | ||
| docs | ||
| legacy | ||
| python | ||
| storage | ||
| tests | ||
| tools | ||
| vendor | ||
| .clang-format | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| .yamllint.yml | ||
| build-docker.sh | ||
| CODEOWNERS | ||
| COMMITS.md | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| create_monorepo.py | ||
| LICENSE.md | ||
| Makefile | ||
| poetry.lock | ||
| poetry.toml | ||
| pyproject.toml | ||
| README.md | ||
| SECURITY.md | ||
| setup.cfg | ||
| shell.nix | ||
Trezor Firmware
Repository Structure
ci: Gitlab CI configuration filescommon/defs: JSON coin definitions and support tablescommon/protob: Common protobuf definitions for the Trezor protocolcommon/tools: Tools for managing coin definitions and related datacore: Trezor Core, firmware implementation for Trezor Tcrypto: Stand-alone cryptography library used by both Trezor Core and the Trezor One firmwaredocs: Assorted documentationlegacy: Trezor One firmware implementationpython: Python client library and thetrezorctlcommandstorage: NORCOW storage implementation used by both Trezor Core and the Trezor One firmwaretests: Firmware unit test suitetools: Miscellaneous build and helper scriptsvendor: Submodules for external dependencies
Contribute
See CONTRIBUTING.md.
Using Conventional Commits is strongly recommended and might be enforced in future.
Also please have a look at the docs, either in the docs folder or at docs.trezor.io before contributing. The misc chapter should be read in particular because it contains some useful assorted knowledge.
Security vulnerability disclosure
Please report suspected security vulnerabilities in private to security@satoshilabs.com, also see the disclosure section on the Trezor.io website. Please do NOT create publicly viewable issues for suspected security vulnerabilities.
Documentation
See the docs folder or visit docs.trezor.io.