Not all invs relayed #1155

New Issue

2018-03-13T15:07:17+01:00

PeterSurda commented

2018-03-13 15:07:17 +01:00

(Migrated from github.com)

it looks like if a connection is established, it does not relay all invs, although the initial "big inv" seems to work correctly. You can reproduce it by using a trustedpeer, and after a couple of hours restart, new objects will show up for syncing
ACKs sent via Dandelion don't seem to enter stem phase correctly
it could also affect locally created objects

- it looks like if a connection is established, it does not relay all invs, although the initial "big inv" seems to work correctly. You can reproduce it by using a trustedpeer, and after a couple of hours restart, new objects will show up for syncing - ACKs sent via Dandelion don't seem to enter stem phase correctly - it could also affect locally created objects

g1itch commented

2019-07-22 13:32:10 +02:00

(Migrated from github.com)

Was it fixed by #1483?

PeterSurda commented

2019-07-22 15:02:54 +02:00

(Migrated from github.com)

Unfortunately I don't have a good way of testing it. I hope it was but I don't know for sure.

navjotcis commented

2020-10-01 16:28:00 +02:00

(Migrated from github.com)

I have tested it and I faced issues like some times the autoresponder does not reply and shows the status of waiting for the encryption key. I have wait for a couple of hours but I did not get the response so I think there are some issues with the autoresponder.

PeterSurda commented

2024-06-11 11:02:44 +02:00

(Migrated from github.com)

Doesn't seem to be happening anymore, was probably fixed in #1483

This repo is archived. You cannot comment on issues.