Project

General

Profile

Actions
Copy link

Bug #3338

closed

checkGenericFileContent 2.1 and 3.0 have desynchronized code between metadata and promises, leading to inconsistencies or uncorrected bugs

Added by Nicolas CHARLES over 11 years ago. Updated over 11 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
Techniques
Target version:
2.4.4
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

For some reasons, some merge between branches 2.3 and 2.4 when astray for checkGenericFileContent, resulting in :
- For version 3, the fix for #3069 isn't applied (the directive needs content to add), and was directed to 2.1 (which is wrong)
- The promises for version 3 include the possibility to not force the creation of file (#2945), which should be applied on 3.1 (the metadata doesn't include this modification)

Others versions seems to be correct

We have to resynchronise manually these files

Actions
Copy link
 #1

Updated by Nicolas CHARLES over 11 years ago

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

Updated by Nicolas CHARLES over 11 years ago

  • Status changed from 8 to Pending release
  • % Done changed from 0 to 100

Applied in changeset commit:5c6c8c6a0e9af4f85ca5824d6345de32222a61e1.

Actions
Copy link
 #3

Updated by Nicolas CHARLES over 11 years ago

  • Assignee changed from Nicolas CHARLES to Jonathan CLARKE

Jon,

This correction is both a merge between 2.3 and 2.4 AND a bugfixe, so I couldn't split the two to follow the traditionnal workflow with pull request
Could you validate this modification ?

Thank

Actions
Copy link
 #4

Updated by Nicolas PERRON over 11 years ago

  • Status changed from Pending release to Released
Actions
Copy link

Also available in: Atom PDF