Hi Ole,
The patches you pushed last Friday indeed fixed all my buggy calls.
Thank you for this.
FYI, I think it broke the vpp-python-api rpm packaging however:
rpm -qpl build-root/vpp-python-api-17.01-rc0~187_gbed29e8.x86_64.rpm
/usr/lib/python2.7/site-packages/vpp_papi/easy-install.pth
/usr/lib/python2.7/site-packages/vpp_papi/vpp_papi-1.3-py2.7-linux-x86_64.egg
So this means installing the rpm will install an easy-install file
within the vpp_papi folder instead of updating the global easy-install file.
As a result import vpp_papi fails.
I moved the line "./vpp_papi-1.3-py2.7-linux-x86_64.egg" from
vpp_papi/easy-install.pth to easy-install.pth, and then everything (vpp
import, load, calls ...) works as expected.
Best regards,
On 12/02/16 12:00, Ole Troan wrote:
> Gabriel,
>
>> Since commit: aff7077d2031545a15efd12e7f65eac723799491 I have the
>> following warning, then error :
>>
>> I looked at the commit, but I cannot find what's wrong with it. Is there
>> something changed with the way I should call the API ?
> The Python API is out of sync with the VPP API.
> Since the delete loopback handler is called.
>
> We're putting in a set of changes for the API split now.
> The CRC, API split and Java code went in earlier.
>
> The JSON packaging is going in now and I'll commit the Python updates (which
> depends on the packaging) immediately after that.
>
> I thought I didn't break existing Python, but clearly I did. Can you hold on
> for a day?
>
> Cheers,
> Ole
>
>
>>
>> [python]
>> import vpp_papi
>> vpp_papi.connect('test')
>> vpp_papi.sw_interface_dump(1, 'test')
>>
>> [vpp]
>>
>> DBGvpp# 0: vl_msg_api_handler_with_vm_node:487: no hander for msg id 13
>> 0: /home/sources/vpp3/build-data/../vnet/vnet/ethernet/interface.c:264
>> (ethernet_delete_interface) assertion `! pool_is_free (em->interfaces,
>> _e)' fails
>>
>> #0 0x00007ffff518c1d7 in raise () from /lib64/libc.so.6
>> #1 0x00007ffff518d8c8 in abort () from /lib64/libc.so.6
>> #2 0x0000000000c2bf5f in os_panic () at
>> /home/sources/vpp/build-data/../vpp/vnet/main.c:314
>> #3 0x00007ffff605392b in debugger () at
>> /home/sources/vpp/build-data/../vppinfra/vppinfra/error.c:84
>> #4 0x00007ffff6053d32 in _clib_error (how_to_die=2, function_name=0x0,
>> line_number=0, fmt=0x7ffff715e5e8 "%s:%d (%s) assertion `%s' fails") at
>> /home/sources/vpp/build-data/../vppinfra/vppinfra/error.c:143
>> #5 0x00007ffff6bfe536 in ethernet_delete_interface (vnm=0x1245880
>> <vnet_main>, hw_if_index=0) at
>> /home/sources/vpp/build-data/../vnet/vnet/ethernet/interface.c:264
>> #6 0x00007ffff6c0021b in vnet_delete_loopback_interface (sw_if_index=0)
>> at /home/sources/vpp/build-data/../vnet/vnet/ethernet/interface.c:562
>> #7 0x0000000000c718a2 in vl_api_delete_loopback_t_handler
>> (mp=0x304a6be0) at /home/sources/vpp/build-data/../vpp/vpp-api/api.c:3451
>> #8 0x00007ffff7bcc9cb in vl_msg_api_handler_with_vm_node (am=0x1246200
>> <api_main>, the_msg=0x304a6be0, vm=0x1245b20 <vlib_global_main>,
>> node=0x7fffb4ffd000)
>> at /home/sources/vpp/build-data/../vlib-api/vlibapi/api_shared.c:481
>> #9 0x00007ffff79b157f in memclnt_process (vm=0x1245b20
>> <vlib_global_main>, node=0x7fffb4ffd000, f=0x0) at
>> /home/sources/vpp/build-data/../vlib-api/vlibmemory/memory_vlib.c:484
>> #10 0x00007ffff74ef407 in vlib_process_bootstrap (_a=140736231382224) at
>> /home/sources/vpp/build-data/../vlib/vlib/main.c:1216
>> #11 0x00007ffff6077bcc in clib_calljmp () at
>> /home/sources/vpp/build-data/../vppinfra/vppinfra/longjmp.S:110
>>
>>
>> Regards,
>>
>> --
>> Gabriel Ganne
>>
>> This message and any attachments (the "message") are confidential, intended
>> solely for the addressees. If you are not the intended recipient, please
>> notify the sender immediately by e-mail and delete this message from your
>> system. In this case, you are not authorized to use, copy this message
>> and/or disclose the content to any other person. E-mails are susceptible to
>> alteration. Neither Qosmos nor any of its subsidiaries or affiliates shall
>> be liable for the message if altered, changed or falsified.
>>
>> Ce message et toutes ses pièces jointes (ci-après le "message")sont
>> confidentiels et établis à l'intention exclusive de ses destinataires. Si
>> vous avez reçu ce message par erreur, merci d’en informer immédiatement son
>> émetteur par courrier électronique et d’effacer ce message de votre système.
>> Dans cette hypothèse, vous n’êtes pas autorisé à utiliser, copier ce message
>> et/ou en divulguer le contenu à un tiers. Tout message électronique est
>> susceptible d'altération. Qosmos et ses filiales déclinent toute
>> responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié.
>> _______________________________________________
>> vpp-dev mailing list
>> vpp-dev@lists.fd.io
>> https://lists.fd.io/mailman/listinfo/vpp-dev
--
Gabriel Ganne
This message and any attachments (the "message") are confidential, intended
solely for the addressees. If you are not the intended recipient, please notify
the sender immediately by e-mail and delete this message from your system. In
this case, you are not authorized to use, copy this message and/or disclose the
content to any other person. E-mails are susceptible to alteration. Neither
Qosmos nor any of its subsidiaries or affiliates shall be liable for the
message if altered, changed or falsified.
Ce message et toutes ses pièces jointes (ci-après le "message")sont
confidentiels et établis à l'intention exclusive de ses destinataires. Si vous
avez reçu ce message par erreur, merci d’en informer immédiatement son émetteur
par courrier électronique et d’effacer ce message de votre système. Dans cette
hypothèse, vous n’êtes pas autorisé à utiliser, copier ce message et/ou en
divulguer le contenu à un tiers. Tout message électronique est susceptible
d'altération. Qosmos et ses filiales déclinent toute responsabilité au titre de
ce message s'il a été altéré, déformé ou falsifié.
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
