Sergey Krasnikov
Sergey Krasnikov
Half day stuck because of these nulls in logged arrays!
Yes, got this error too after some time after upgrade to 1.8. Before it version 1.7 worked perfectly over more one year on different installations. Got on high load.
Thinking (but not tested) it related to this commit: https://github.com/kelektiv/node-cron/commit/e1b392f244025bbc833d648b33d01ee191640890 Can anyone test without it? Reverted back to 1.7.2 for now.
> I have the same problem, any fix for that? Revert to 1.7.2 for now. For me 1.7.2 was bugless.
@ncb000gt From my perspective - used this module in production high load systems since 2016 and not got critical (uncatchable?) error even once and this module worked like a charm....
And not mention causes - it for now is bug. If it can't be reverted or fixed suggesting 2.0.0 version of component with breaking changes and example of catching and...
Great PR - it converts bug to feature, but if default for softTimeout is false - it is breaking change (with main commit caused this issue). And after upgrade to...
Hello! +100500 quotes to this. It is critical functional for json editor. For now it is not JSON editor. It is just JS-object editor. It converts json to js forcibly...
Hello! Want to reopen this because lot of json postgresql operators absent in Sequelize. In particular it will be convinient to have some function to register own operators like '?'...
> Hi there. Did you try extending the SequelizeStorage to do this? Would that work for your use case? I did monkey patch that removed this sync() methods from SequelizeStorage...