H0w Xd

@dimitropoulos I believe this one would do: [curl.txt](https://github.com/Kong/insomnia/files/7032720/curl.txt)

If anyone's interested in this feature, I've added support for specifying exact value in a commit on my repo https://github.com/h0wXD/lightweight-charts/commit/f95891c21f8fefe36ab56d8117897f23c6756f76 , but I'm not sure if the firstValue parameter is...

I've ran into the same limitation and solved the problem in a way with minor refactoring, although may not be a great solution to be PR'd. It would require points...

With this you may want to add `npm install --legacy-peer-deps`, so deprecated packages can be installed in v14+, else people will run into errors: ``` lightweight-charts>npm i npm ERR! code...

I am having the same problem with latest library @microsoft/applicationinsights-web 2.7.2. I am calling startTrackPage at 2021-12-13T03:46:27.423Z and calling stopTrackPage at 2021-12-13T03:46:40.206Z. The loading time of the page is 12.8...

Also looking for this feature. Is there any update for this? Would be incredibly useful to debug test cases from inside VSC.

> > If anyone's interested in this feature, I've added support for specifying exact value in a commit on my repo [h0wXD@f95891c](https://github.com/h0wXD/lightweight-charts/commit/f95891c21f8fefe36ab56d8117897f23c6756f76) , but I'm not sure if the firstValue...

@kernc that works perfectly, thanks for the quick response after doing the following before passing it to backtest ```python AAPL1H.index = AAPL1H.index.tz_convert(None) ``` now the Equity results are correct comparing...

I still think this should be handled by the library when library users do use unintended datetime formats, as using date time dataset with offset causes invalid backtest results, this...