Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Align RepairnatorConfig with set_env_variable.sh and use config intensively in all modules.
See original GitHub issueRepairnatorConfig is highly related to the pipeline, but we use it for all modules now. What about creating one config for each module? Then we init the config for a given module with all args in that module, thus we don’t need to retrieve specific args in any other location in the code?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Deal.
Hmmmm. Actually I like the idea, but I maintain we should only keep one RepairnatorConfig:
Not necessarily. Have a look on https://github.com/Spirals-Team/repairnator/blob/master/repairnator/scripts/set_env_variable.sh actually it should contain almost the same parameters.