NoReply: Method call timed out about adbus

[charleseidsness]

It's not a bad idea, we'll have a look at implementing it in a few days.

[charleseidsness]

I just checked in an update that adds an optional timeout_ms to update, it also returns its self so that you can use that single line syntax in your example.

[Kavan72]

@charleseidsness are you here ?

[Kavan72]

adbus.sdbus.SdbusError: org.freedesktop.DBus.Error.NoReply: Method call timed out

maybe, you are missing something. cuz it's still waiting 120 sec (that is by default on dbus) i think you have to raise custom timeout error if no update

[Kavan72]

something like this await asyncio.wait_for(call.event.wait(), int(5)) in call.py

[Kavan72]

@charleseidsness sir, am i right ?

[charleseidsness]

You're going to have to be more specific, can you send the error that is raised, including the traceback?

[Kavan72]

Fri Jul 19 18:12:41 2019
Start_time_in_call_dbus =>  Fri Jul 19 18:12:41 2019
Start_time_in_Scall =>  Fri Jul 19 18:12:41 2019
Stop_time_in_Scall =>  Fri Jul 19 18:12:41 2019

Ignoring exception in command test:
Traceback (most recent call last):
  File "/media/kavan/DATA/discord_bots/wfbot/venv/lib/python3.7/site-packages/discord/ext/commands/core.py", line 79, in wrapped
    ret = await coro(*args, **kwargs)
  File "/media/kavan/DATA/discord_bots/wfbot/test/test_bot.py", line 38, in test
    await proxy.update(timeout_ms=5000)
  File "/media/kavan/DATA/discord_bots/wfbot/venv/lib/python3.7/site-packages/adbus/client/proxy.py", line 477, in update
    timeout_ms=timeout_ms,
  File "/media/kavan/DATA/discord_bots/wfbot/venv/lib/python3.7/site-packages/adbus/client/call.py", line 59, in call
    raise call.response
  File "adbus/sdbus/call.pxi", line 14, in adbus.sdbus.call_callback
  File "adbus/sdbus/message.pxi", line 32, in adbus.sdbus.Message.import_sd_bus_message
adbus.sdbus.SdbusError: org.freedesktop.DBus.Error.NoReply: Method call timed out

this is full traceback which is i got

[charleseidsness]

We're not able to replicate this, it's working for us That timeout is actually returned from the systemd dbus library, which will be set to 5 seconds using the latest version in git. You're free to add an additional timeout to your own code. == Charles Eidsness Chief Engineer *CCX Technologies* [phone]

…

On Fri, 19 Jul 2019 at 08:46, Hidan ***@***.***> wrote: Fri Jul 19 18:12:41 2019 Start_time_in_call_dbus => Fri Jul 19 18:12:41 2019 Start_time_in_Scall => Fri Jul 19 18:12:41 2019 Stop_time_in_Scall => Fri Jul 19 18:12:41 2019 Ignoring exception in command test: Traceback (most recent call last): File "/media/kavan/DATA/discord_bots/wfbot/venv/lib/python3.7/site-packages/discord/ext/commands/core.py", line 79, in wrapped ret = await coro(*args, **kwargs) File "/media/kavan/DATA/discord_bots/wfbot/test/test_bot.py", line 38, in test await proxy.update(timeout_ms=5000) File "/media/kavan/DATA/discord_bots/wfbot/venv/lib/python3.7/site-packages/adbus/client/proxy.py", line 477, in update timeout_ms=timeout_ms, File "/media/kavan/DATA/discord_bots/wfbot/venv/lib/python3.7/site-packages/adbus/client/call.py", line 59, in call raise call.response File "adbus/sdbus/call.pxi", line 14, in adbus.sdbus.call_callback File "adbus/sdbus/message.pxi", line 32, in adbus.sdbus.Message.import_sd_bus_message adbus.sdbus.SdbusError: org.freedesktop.DBus.Error.NoReply: Method call timed out``` this is full traceback which is i got — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#50?email_source=notifications&email_token=AAOXWWQI66L6GIMKIRITW6DQAGZT5A5CNFSM4H7SEU7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2LQYYI#issuecomment-513215585>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOXWWR3PBWNFQZU6K63VXLQAGZT5ANCNFSM4H7SEU7A> .

[Kavan72]

ok np i will fork and edit it for me 😃

[charleseidsness]

Sounds good! == Charles Eidsness Chief Engineer *CCX Technologies* [phone]

…

On Fri, 19 Jul 2019 at 09:23, Hidan ***@***.***> wrote: ok np i will fork and edit it for me 😃 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#50?email_source=notifications&email_token=AAOXWWWQ56VWZ7MKYW5AWWLQAG54ZA5CNFSM4H7SEU7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2LTRCI#issuecomment-513226889>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOXWWS76QV26XS2FBYU2XDQAG54ZANCNFSM4H7SEU7A> .

[Kavan72]

when you free check this https://github.com/Kavan72/adbus/commit/cc234531889bd1e2d726bd1a41d531a9e30b5cb7

[charleseidsness]

I'd prefer to try to figure out why the dbus time out isn't working in your case, and only add that extra timeout as a last resort. We can have another look in a couple of weeks, once we have more time. == Charles Eidsness Chief Engineer *CCX Technologies* [phone]

…

On Fri, 19 Jul 2019 at 09:56, Hidan ***@***.***> wrote: when you free check this ***@***.*** <Kavan72/adbus@cc23453> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#50?email_source=notifications&email_token=AAOXWWRMQFNRGYQM3I2V5YTQAHB2TA5CNFSM4H7SEU7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2LWJUI#issuecomment-513238225>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOXWWXJNVOJ2CYVMQAQ5NLQAHB2TANCNFSM4H7SEU7A> .