JH

Same issue here. Any solutions so far?

Weights needed here too. Thanks!

I had the same issue. Was able to create a workaround by implementing my own APIBackend class

> Hi, @JakobWong , First of all thank you for contributing the code, I see that the description of this pull request implements a lot of functionality. However, it doesn't...

> @JakobWong please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information. > > ``` > @microsoft-github-policy-service agree [company="{your company}"] >...

> Hi, @JakobWong First of all, thank you for your contribution to qlib, secondly, I would like to know where did you get this data `~/.qlib/qlib_data/crypto_data_perp` from? I think it...

> Hi, @JakobWong I tried to test the code `qlib/example/workflow_by_code_longshort_crypto.py`, and found a problem with the circular import. > > `workflow_by_code_longshort_crypto.py → qlib.workflow.record_temp → qlib.contrib.evaluate → qlib.strategy.base → qlib.backtest →...

> Hi, @JakobWong > > Thanks for fixing bug, I'm trying to run the sample code on the latest modification. Some issues were found: > > * `workflow_by_code_longshort_crypto.py` reports: `crypto_qlib_config.py`...

> Hi, @JakobWong Thanks for fixing the previously mentioned bugs, I tried to run `shortable_backtest_crypto_loop.py`, and the problem disappeared, which is good news. But `workflow_by_code_longshort_crypto.py` found a new problem during...

> Hey, @JakobWong Thanks for fixing these issues, the sample code in examples currently works. This is good news. I see that there are still some Chinese comments, please revert...