Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chart not opening error and corresponding message of no signals set #117

Closed
debonair99 opened this issue Jul 6, 2024 · 12 comments
Closed
Assignees
Labels

Comments

@debonair99
Copy link

Tried using latest version of Kairos with the below screenshots when running

1
2

Please assist, I have tried using StockOverflow but to no avail
Thanks!

@jerajx
Copy link

jerajx commented Jul 19, 2024

Hi, I have the same problem. It seems it stucks when opening the wachlist.

@timelyart timelyart self-assigned this Jul 19, 2024
@timelyart timelyart added the bug Something isn't working label Jul 19, 2024
@timelyart
Copy link
Owner

Probably something in the DOM changed. I'll try to get a fix in within a week.

@timelyart
Copy link
Owner

Well... I don't know what to say. I have no issues. It might be that the DOM changes haven't been rolled out to the server that serves me. This has happened in the past. All I can do is wait until it starts breaking for me as well.

I did notice you have a lower DELAY_KEYSTROKE at 0.01 than my 0.05. So, you might try a higher value. Can you tell what you were trying to do? Setting alerts? Back testing strategies? Or, triggering signals?

@jerajx
Copy link

jerajx commented Jul 24, 2024

DELAY_KEYSTROKE at 0.01 is default, anyway I changed it to 0.05, no change. I'm attaching some logs. I tried export and browse.yaml. Logs are from browse. script logs in OK, and then stops when it should open the watchlist.

browse-log10.txt

browse-log20.txt

@timelyart
Copy link
Owner

Thank you for giving the additional information.

The only thing I can think of now is to clear your browser cache, run python main.py -cls and run Kairos as you would do normally (in that order). This makes sure the cache gets purged from the Kairos Chrome container.
Let me know whether this solves the issue.

@jerajx
Copy link

jerajx commented Jul 24, 2024 via email

@timelyart
Copy link
Owner

In that case... we just have to wait until the DOM changes for me as well which will hopefully be sooner than later. I'll check it daily.

@timelyart
Copy link
Owner

Fixed in v3.16.

@jerajx
Copy link

jerajx commented Jul 26, 2024 via email

@johnmolino
Copy link

broke again?

@jerajx
Copy link

jerajx commented Sep 11, 2024 via email

@timelyart
Copy link
Owner

broke again?

Are you running v3.17?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants