You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was observed when writing integration tests for an application with dht.neo support. It occurs when the app is configured to use the dht.neo.mirror request.
When the integration tests use turtle dht.put to write to the fake DHT, the test suite hangs. If the app is tweaked to use legacy mirror functionality (Listen + periodic GetAll) instead of the neo request, the test suite works fine.
It is not clear at this stage whether this is a problem with how the fake DHT handles neo mirror requests, or whether it is a more general problem with the neo mirror request itself. I'll try to test with an up to date neo-supporting dhtnode instance to verify.
The text was updated successfully, but these errors were encountered:
I've tried the app in local tests with neo-supporting DHT nodes, and neo mirror request seems to work OK (i.e. new profiles come through, the app reacts accordingly). So without further information it seems possible that the problem is specific to test-suite fakeDHT (or at least, that it's only visible via fakeDHT).
This was observed when writing integration tests for an application with dht.neo support. It occurs when the app is configured to use the
dht.neo.mirror
request.When the integration tests use turtle
dht.put
to write to the fake DHT, the test suite hangs. If the app is tweaked to use legacy mirror functionality (Listen
+ periodicGetAll
) instead of the neo request, the test suite works fine.It is not clear at this stage whether this is a problem with how the fake DHT handles neo mirror requests, or whether it is a more general problem with the neo mirror request itself. I'll try to test with an up to date neo-supporting
dhtnode
instance to verify.The text was updated successfully, but these errors were encountered: