Skip to content

Conversation

@mayanje
Copy link
Contributor

@mayanje mayanje commented Oct 13, 2021

No description provided.

@mayanje mayanje requested review from fm-117 and smedilol October 13, 2021 14:42
@mayanje mayanje self-assigned this Oct 13, 2021
@trafico-bot trafico-bot bot added the 🔍 Ready for Review Pull Request is not reviewed yet label Oct 13, 2021
//missingCopiesParam.Copies = lookup[false].ToList();
//missingCopiesParam.CpyCopies = lookup[true].ToList();
//----------------------------------------------------------
missingCopiesParam.Copies = copiesName;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't seems related with #2046. Is it an error ?

@trafico-bot trafico-bot bot added ⚠️ Changes requested Pull Request needs changes before it can be reviewed again and removed 🔍 Ready for Review Pull Request is not reviewed yet labels Oct 13, 2021
@smedilol
Copy link
Contributor

The name of the branch is not correct. It's not 1.5.7 but should be 2046_Fix_NPE. Because you don't know if another PR will be merged into develop before the actual 1.5.7 will be created.

@mayanje mayanje closed this Oct 13, 2021
@mayanje mayanje deleted the v1.5.7 branch October 13, 2021 15:15
Comment on lines +176 to +185
//----------------------------------------------------------
// We need to review this mechanism with RTC.
// Because actually it produces bad results and it will
// be clarified with RTC specifications. (see TFS 117645)
//----------------------------------------------------------
//missingCopiesParam.Copies = lookup[false].ToList();
//missingCopiesParam.CpyCopies = lookup[true].ToList();
//----------------------------------------------------------
missingCopiesParam.Copies = copiesName;
missingCopiesParam.CpyCopies = new List<string>();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It may produce bad results but it is not related to this issue. I don't see any null refs in the original code so maybe revert this and create a dedicated issue ?

Copy link
Contributor Author

@mayanje mayanje Oct 14, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The fact is that, this is not compatible with current CobolEditorEI version that's all, so I was not able to test. And in the current version of CobolEditorEI, this concept does not work,

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, but what about #1975 that request this change. Is it still needed or not ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right, it was supposed to be an alternative in editor, but even with that the algorithm suggested in TFS 117645 is not good, so we need to refer to new specification in our internal R 387225.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug ⚠️ Changes requested Pull Request needs changes before it can be reviewed again Cobol Editor

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants