Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0013363 | Openbravo ERP | Z. Others | public | 2010-05-18 12:13 | 2010-05-21 00:00 |
|
Reporter | shuehner | |
Assigned To | shuehner | |
Priority | immediate | Severity | critical | Reproducibility | have not tried |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | pi | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | No |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0013363: api check build 393 fails |
Description | This api check build fails:
http://builds.openbravo.com/job/erp_devel_pi-module-integrity-test/393/console [^]
[checkAPI] 34875 ERROR - +++++++++++++++++++++++++++++++++++++++++++++++++++
[checkAPI] 34882 ERROR - Errors in API data validation
[checkAPI] 34888 ERROR - +++++++++++++++++++++++++++++++++++++++++++++++++++
[checkAPI] 34895 ERROR - Not Allowed insertions in AD_PROCESS_PARA table. ID: 7144D3B5D3254D118A501450DD94CC70
[checkAPI] 34899 ERROR - Not Allowed insertions in AD_PROCESS_PARA table. ID: DD67C43EBCE14230AC3F04A2904231EB
|
Steps To Reproduce | |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | defect | 0012939 | | closed | vmromanos | Purchase invoice payment is not cancelled when it contains withholding |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2010-05-18 12:13 | shuehner | New Issue | |
2010-05-18 12:13 | shuehner | Assigned To | => vmromanos |
2010-05-18 12:13 | shuehner | OBNetwork customer | => No |
2010-05-18 12:13 | shuehner | Relationship added | related to 0012939 |
2010-05-18 13:16 | vmromanos | Note Added: 0027418 | |
2010-05-18 13:16 | vmromanos | Status | new => acknowledged |
2010-05-18 18:27 | vmromanos | Assigned To | vmromanos => pjuvara |
2010-05-18 20:42 | gorka_gil | Issue Monitored: gorka_gil | |
2010-05-19 10:06 | pjuvara | Status | acknowledged => scheduled |
2010-05-19 10:06 | pjuvara | Note Added: 0027548 | |
2010-05-19 10:06 | pjuvara | Assigned To | pjuvara => shuehner |
2010-05-19 10:06 | pjuvara | fix_in_branch | => pi |
2010-05-19 11:22 | hgbot | Checkin | |
2010-05-19 11:22 | hgbot | Note Added: 0027552 | |
2010-05-19 11:22 | hgbot | Status | scheduled => resolved |
2010-05-19 11:22 | hgbot | Resolution | open => fixed |
2010-05-19 11:22 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/api-checks/rev/1a1155cd07e48413fbd6cea75d689b3fb8d41f18 [^] |
2010-05-19 11:48 | shuehner | Note Added: 0027554 | |
2010-05-19 11:48 | shuehner | Status | resolved => closed |
2010-05-21 00:00 | anonymous | sf_bug_id | 0 => 3004962 |
Notes |
|
|
From my point of view this is a false API change.
My code adds two new optional parameters to a database procedure. As optional parameters, they don't modify the existing functionality of the procedure. It continues to work as usual if the user does not introduce a value to these parameters.
I think we should review the validation we do to check this scenario. ALO is aware of this issue. |
|
|
|
Acknowledged as false positive. Please ignore. |
|
|
(0027552)
|
hgbot
|
2010-05-19 11:22
|
|
|
|
|
api-change issue, build ok -> closing |
|