Actions
User story #7407
closedDisplay failed cf-promises to make it easier to re-run while debugging
Effort required:
Name check:
Fix check:
Regression:
Description
Whenever Rudder fails on promise generation, I see a frustrating message like this:
This is useful enough, but I would really like to be able to reproduce that error for myself on the command line, and run it until I have managed to solve the problem.
I therefore propose that this error message tells us what command exactly to run, so users can just copy/paste that and run it themselves.
Files
Updated by Jonathan CLARKE almost 9 years ago
- Status changed from New to In progress
Updated by Jonathan CLARKE almost 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/959
Updated by Jonathan CLARKE almost 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|b2219f354bf78b350e59b3e73fef45b025c36632.
Updated by Vincent MEMBRÉ almost 9 years ago
Applied in changeset rudder|746edcb4081a3a165fee4ada15cc3c29bcd9d38b.
Updated by Vincent MEMBRÉ over 8 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.2.0~beta1 which was released today.
Actions