Thomas Chopitea
Thomas Chopitea
To reproduce: 1. upload attachment with long filename (> 111 chars) 2. try to download attachment
We want a contributor's guide / help text that is a bit more verbose than what we have now, namely on code idiosyncracies: * How to write a good recipe...
- [ ] Docker - [ ] pypi - [ ] CD with Github actions
LocalPlasoProcessor should have a flag to use docker or not.
Should we move to f-strings? or keep using `format()`?
Given that recipes are starting to mushroom, tags and categories can be a good way to classify / group them.
It would be nice to have a preflight for workspace auth, as I can see this being used by future modules.
Some tests (e.g. tests/lib/collectors/aws_snapshot_s3_copy.py) build parameters dynamically from test / mock values, or complex control structures. Fore readability, ease of debug, etc. tests should be as literal and simple as...
It would be nice to have a `--mount-all` that would mount the FS of all container to given directory, e.g. `/mnt/docker-all/container1`, `/mnt/docker-all/container2`, etc.