manage byproducts
Open
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 159
- PR merge metrics
- No merged PRs in 30d
Description
While running bigflow program, I find it will output some byproducts, e.g.,
entity-*
.flume
...
After several times, it will make the folder in a mess.
Could you please put those byproducts into a pre-specified subfolder, in order to conveniently manage.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating where Bigflow creates the entity-* and .flume byproducts, then trace how an output subfolder could be specified. Done means those artifacts are consistently placed in the specified subfolder after repeated runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100