I think that partyline shouldn't require user to be connected to network, because partyline doesn't have anything to do with network where it's connected.
I think that partyline shouldn't require user to be connected to network, because partyline doesn't have anything to do with network where it's connected.
<!-- github-sync-id:1791448 -->
If it wasn't the latest git (or in better words after 3947ea9) you should try it with git-latest because partyline didn't work after CIRCNetwork changes (#64) and maybe this patch:
a) solve this problem by default
b) show other hugh bugs that should be fixed to as the commit-msg says: I didn't test this fix at all. Any crashy (or weird behavioury) feedback welcome :)
PS.: If somebody really should take care of partyline he/she should also look at #21
what version did you try it?
If it wasn't the latest git (or in better words after 3947ea9) you should try it with git-latest because partyline didn't work after CIRCNetwork changes (#64) and maybe this patch:
a) solve this problem by default
b) show other hugh bugs that should be fixed to as the commit-msg says:
`I didn't test this fix at all. Any crashy (or weird behavioury) feedback welcome :)`
PS.: If somebody really should take care of partyline he/she should also look at #21
<!-- github-comment-id:2261797 -->
I am not sure what version I used when I opened this issue, but I upgraded to latest git version yesterday and this issue seems to still happen. So version is commit edaa20e59e .
I am not sure what version I used when I opened this issue, but I upgraded to latest git version yesterday and this issue seems to still happen. So version is commit edaa20e59eabd8483b4043491ae499b9c920bb94 .
<!-- github-comment-id:2332221 -->
It also seems that connecting without specifying network gives the following message after some time:
Closing link [Timeout]
It also seems that connecting without specifying network gives the following message after some time:
- Closing link [Timeout]
<!-- github-comment-id:2332453 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I think that partyline shouldn't require user to be connected to network, because partyline doesn't have anything to do with network where it's connected.
what version did you try it?
If it wasn't the latest git (or in better words after
3947ea9) you should try it with git-latest because partyline didn't work after CIRCNetwork changes (#64) and maybe this patch:a) solve this problem by default
b) show other hugh bugs that should be fixed to as the commit-msg says:
I didn't test this fix at all. Any crashy (or weird behavioury) feedback welcome :)PS.: If somebody really should take care of partyline he/she should also look at #21
I am not sure what version I used when I opened this issue, but I upgraded to latest git version yesterday and this issue seems to still happen. So version is commit
edaa20e59e.It also seems that connecting without specifying network gives the following message after some time: