11 Commits (6be367bf8b591d48e1e74d709c34319cff9df1d1)

Author	SHA1	Message	Date
Pavol Rusnak	50fdd183c2	ci: enable editorconfig checks, fix whitespace issues	4 years ago
Martin Milata	c89a8b7bd5	ci(core): add memory profiler job	4 years ago
Pavol Rusnak	063aba910d	core: rename emulator to trezor-emu-core	4 years ago
matejcik	72cde5a57d	core: disallow parsing options after command (fixes #951)	4 years ago
matejcik	5bd8d9b5bb	core/sdcard: make allocating new SD card for emulator fast	4 years ago
matejcik	1d41141a1f	core/emulator: properly ignore inotify problems (fixes #854)	4 years ago
matejcik	4c8c96272c	emu: fix flag options with defaults ... Click REALLY INSISTS you provide on/off switches for your options. You can use is_flag, but then the presence of the option changes based on the default value. Which makes sense, really: @option("-f", "foobar", is_flag=True, default=False) you would expect `./cli -f` to have `foobar is True` whereas with @option("-f", "foobar", is_flag=True, default=True) you would expect `./cli -f` to have `foobar is False`, otherwise it's a no-op this becomes fun with `default=os.environ.get("SOMETHING")`, because then the effect of the option CHANGES with a value of environment variable! there's two ways around this: a) don't use defaults, update the flag explicitly, like: foobar = foobar or os.environ.get("FOOBAR") == "1" b) forget about is_flag and specify an on/off switch, where the default value works as intended since the latter is also technically speaking more correct, i'm doing it	4 years ago
matejcik	271da3fa39	python: add detailed logging to emulator runner	4 years ago
Tomas Susanka	4850eaf534	emu.py: remove frozen variable	4 years ago
matejcik	a3d309eca2	core/prof: make sure coverage data is generated with absolute paths	4 years ago
matejcik	8dce2cf98c	core: introduce emulator runner (fixes #466)	4 years ago