Project

General

Profile

Actions
Copy link

Bug #8020

closed

Bridge does not corrupt job when Core provides incorrect report attributes

Added by Evgeny Novikov about 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
High
Assignee:
Vladimir Gratinskiy
Category:
Bridge
Target version:
-
Start date:
03/09/2017
Due date:
06/13/2017
% Done:

100%

Estimated time:
Detected in build:
svn
Platform:
Published in build:

Description

I noticed this when attributes looks like [{"a": "b", "c": "d"}] but perhaps there are other cases when Bridge does not check attributes validity.

Related issues 1 (0 open — 1 closed)

Related to Klever - Bug #7526: Bridge should reject child reports that overwrite values of parent report attributesClosedVladimir Gratinskiy08/23/201602/16/2017

Actions
Actions
Copy link
 #1

Updated by Vladimir Gratinskiy almost 7 years ago

  • Due date set to 06/13/2017
  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Fixed in fix_8020.

Actions
Copy link
 #2

Updated by Evgeny Novikov almost 7 years ago

  • Status changed from Resolved to Closed

I merged the branch to master in 25010f17 although indeed Core more than a year processes all attributes so that the case mentioned in the issue description don't happen. But suddenly that can happen.

Actions
Copy link

Also available in: Atom PDF