movy

Redis persistence is what is needed here I think, good catch @jgoclawski , will try this on next update.

As a temporary solution I wrapped `.fit()` with `try...except` and at least I can terminate such problematic trials: ```py try: results = tune.Tuner(tune.with_resources(backtest_rungs, param_space=hyperparams, tune_config=tune_config, run_config=run_config).fit() except Exception as e:...

Thanks for all your input, I tried `[RAY_TASK_MAX_RETRIES=0]` -- did not help, @stephanie-wang how to use `ray stack`? I have a hung ray process with the message ``` [2023-12-14 08:56:35,320...

Still seeing lots of these messages when ingesting lots of data, glusterfs 11.1, is this fix in the upstream yet? ```log [2025-02-06 08:17:42.876835 +0000] E [nl-cache-helper.c:405:nlc_set_dir_state] (-->/usr/lib/x86_64-linux-gnu/glusterfs/11.1/xlator/features/utime.so(+0x42ea) [0x75ab83a262ea] -->/usr/lib/x86_64-linux-gnu/glusterfs/11.1/xlator/performance/nl-cache.so(+0x917b) [0x75ab8097817b]...

Thanks for prompt response, I use one route + one extra_route, and not using new `fast_mode` for now, as it fails for different reasons with my strategies (will investigate this...

So, good news and bad news: this regression was not caused by 0.48 (i.e. 0.48.1. did not fix it). The last version that does not hang is 0.45, so I'm...

Yes, I cancel on every candle if order was not executed. This never was a problem prior to 0.46.

Thank you, @yakir4123 , I tried your branch, unfort same result. I will try to create a small script that consistently reproduces problematic behaviour, will post it here later.

0.45 is the final version working w/o hanging, 0.46 introduced this bug

@yakir4123 , still hangs unfort. But I think you're moving in the right direction with identifying orders that are updated on each candle. My strategy logic is such that I...