tbi88
tbi88
@StarGateMiner btc.zsolo.bid:6057
Crazy! Mine is running since > 24 hours with btc.zsolo.bid:6057 with v1.5.1. Before with v1.4.0 I never had anything more than two hours. Are we using the same hardware revisions?
any update regarding this? Will it be TLS for the connection or are you planning to encrypt the content itself?
Sure, we could test it, but honestly I would prefer TLS at the end. Unencrypted communication with encrypted content will lead to pentesting findings at the end. But still better...
> > Hey! > > So what you're saying is that the node ends up sending/running multiple times? There is no hard limit on sizes that we have put in...
hmm not really, just went up to 7.5 MB and it seems to work fine. Any other reason why "shuffle-tools" should get back a 401 from the worker container?
the node is "shuffle-tools" running python code which returns the large json data. It is the second last node of the worklow, the result of that node is sent to...
nope, the subflow never starts. The shuffle-tools node fails and the execution stops (shown as Red in the UI)...
still having this issue with 1.4.2. Any ideas?
Hi Still seeing this issue from time to time. Until it gets fixed in the code, is there any way I can increase the limit? Regards