Alexey
Alexey
``` Environment.TickCount64 > DateTime.UtcNow > DateTime.Now ^ no sync/update issues ^ no day-light saving time issues ``` I did not face such issues, but I believe if they will appear,...
Propose local deployment set up for convenient development
I've just fixed it by patching some packages, I have [email protected] btw To fix the issue you need to find `node_modules/browser-request/index.js` and make `function is_crossDomain(url)` return true. Otherwise it uses...
@kamilchodola I'll take a look in next couple of weeks if no one picks
A thing to consider is [the netty implementation ](https://github.com/netty/netty/blob/4.1/handler/src/main/java/io/netty/handler/traffic/ChannelTrafficShapingHandler.java) of similar requirement.
@vyzo I'm experiencing something similar, after some time receiver gets a part of a pubsub message, and then the peer stops sending to the receiver at all, displaying `queue full`....
> That sounds like backpressure from the network stack, is the receiver live? Yes, peers continue exchange with pings via yamux, for example. I've found no closing signals like FIN/RST...
Btw what I do: send a message every 300 ms. What has been found right now: the problem happens when total size of the messages is near 256kB! So let...
@vyzo solved on dotnet side, thanks for the fast response!
> Care to elaborate for future reference? .NET yamux implementation simply did not grow window