Project

General

Profile

Actions
Copy link

User story #7407

closed

Display failed cf-promises to make it easier to re-run while debugging

Added by Jonathan CLARKE about 9 years ago. Updated about 9 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - UI & UX
Target version:
3.2.0~beta1
Pull Request:
https://github.com/Normation/rudder/p...
UX impact:
Suggestion strength:
User visibility:
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

1.png (22.3 KB) 1.png Jonathan CLARKE, 2015-11-13 16:30
Actions
Copy link
 #1

Updated by Jonathan CLARKE about 9 years ago

  • Status changed from New to In progress
Actions
Copy link
 #2

Updated by Jonathan CLARKE about 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
Actions
Copy link
 #3

Updated by Jonathan CLARKE about 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 9 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
Copy link

Also available in: Atom PDF