Project

General

Profile

Actions
Copy link

Bug #6318

closed

ncf api error should be properly interpreted

Added by Benoît PECCATTE over 9 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Technique editor
Target version:
ncf-0.x
Pull Request:
Severity:
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

Some try/catch are missing in ncf api and in ncf post hooks to properly examine errors and interpret them.
We should examine ncf source code ad add proper error detection.

Related issues 1 (0 open — 1 closed)

Has duplicate Rudder - Bug #6306: Complete error logging for ncfRejectedBenoît PECCATTEActions
Actions
Copy link
 #1

Updated by Alexis Mousset over 8 years ago

  • Category set to Technique editor - API
Actions
Copy link
 #2

Updated by Jonathan CLARKE over 7 years ago

  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
Actions
Copy link
 #3

Updated by François ARMAND over 7 years ago

  • Status changed from New to Rejected
  • Priority set to 0

It should be done by now. If there is still errors, please open a new ticket with the exact place where the error is and try/catch should be put.

Actions
Copy link
 #4

Updated by Alexis Mousset over 2 years ago

  • Target version changed from 0.x to ncf-0.x
Actions
Copy link
 #5

Updated by Alexis Mousset over 2 years ago

  • Project changed from 41 to Rudder
  • Category changed from Technique editor - API to Web - Technique editor
Actions
Copy link

Also available in: Atom PDF