Uh oh!
There was an error while loading. Please reload this page.
api: remove empty response parameters - #2751
Conversation
borisstoyanov
commented
Jul 19, 2018
@blueorangutan package |
blueorangutan
commented
Jul 19, 2018
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
borisstoyanov
commented
Jul 19, 2018
Hi @marcaurele, thanks for this fix. Can you please share some examples how you've tested it? |
218bfef to
6452be8Compare@borisstoyanov I simply did a local compilation but I pushed before checking it went fine. I missed a line removal. I just force pushed an amend. To test: you can check the actual empty parameters with the cs python lib: |
borisstoyanov
commented
Jul 19, 2018
Thanks @marcaurele, let me try that and will run smoketests as well |
DaanHoogland
commented
Jul 19, 2018
looks good, Marc-aurele but are we sure they are really never filled in a response? |
marcaurele
commented
Jul 19, 2018
@DaanHoogland yes, otherwise the code won't compile. |
DaanHoogland
commented
Jul 19, 2018
not if reflection is somehow used. not to blame you but I am a bit wary with these kind of left-overs. Actually in this case I think you are right. |
blueorangutan
commented
Jul 19, 2018
Packaging result: ✖centos6 ✖centos7 ✔debian. JID-2186 |
borisstoyanov
commented
Jul 19, 2018
@blueorangutan package |
blueorangutan
commented
Jul 19, 2018
@borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
blueorangutan
commented
Jul 19, 2018
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-2190 |
borisstoyanov
commented
Jul 19, 2018
@blueorangutan test |
blueorangutan
commented
Jul 19, 2018
@borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
blueorangutan
commented
Jul 19, 2018
Trillian test result (tid-2867)
|
Description
Remove response parameters missing a description, and which are not used, creating an empty entry in
listApiscall (see the empty{}below):Types of changes
GitHub Issue/PRs
How Has This Been Tested?
Checklist:
Testing