ticker.sh

ticker.sh copied to clipboard

Think it is the cookie stuff. It stopped on one machine a few days ago and I copied the cook cache from another machine and it started working. Now fails on all systems

This does appear to be wider spread than just to this piece of code. In that same thread a user reports a different endpoint as still valid, but requires some adjustment to account for the change in results.

Not sure how long that will last. Seems like Yahoo might be playing around with their APIs.

This image appears when navigating the URL reported in the API_ENDPOINT

{"finance":{"result":null,"error":{"code":"Unauthorized","description":"Invalid Crumb. For Developers - https://bit.ly/yahoo-finance-api-feedback"}}}

Followed by a survey ending with:

Similar to like what they did a few months ago :/ :disappointed:

Here we go. Everything that happened during the last couple of weeks pointed towards this.

Yep. Mine stopped working again as well. Is there a chance we can switch to Google Finance or is that not an option

there is tickr and from a quick look at code it uses yahoo. it is working. not sure if the code can provide a hint as to what to change to get working again

so I guess we're just waiting at this point to see what yahoo does? there does appear to be some endpoints that are still active, like: https://query1.finance.yahoo.com/v8/finance/chart/AAPL for example. /quote seems to be dead though.

This pretty much sums it up, unfortunately. I‘m looking for alternatives, but haven’t been able to find any so far.

I created PR#46 if y'all would like to give that a play with :penguin:

I created PR#46 if y'all would like to give that a play with penguin

seems to be working for me

I created PR#46 if y'all would like to give that a play with penguin

seems to be working for me

I can confirm it's working for me as well.

If it is working, will the PR #46 merge be done?

I‘m honestly not convinced that a request per ticker is a good solution, even if it‘s the only way to make it work. Thoughts?

as you say, the only way to make it work. i can live with this versus not having the capability.

PR #46 needs to add support for NOCOLOR

PR #46 needs to add support for NOCOLOR

I see in the original code:

if [ -z "$NO_COLOR" ]; then
  : "${COLOR_BOLD:=\e[1;37m}"
  : "${COLOR_GREEN:=\e[32m}"
  : "${COLOR_RED:=\e[31m}"
  : "${COLOR_RESET:=\e[00m}"
fi

I'll try to find some time to learn how to get that in place :)

@pcause I believe I might have got it. Can you try the latest commit to PR#46 and let me know? :penguin:

in my use case it looks like it works. thanks

the pr 46 version seems to have stopped working today

it feels like every solution using Yahoo Finance will be short-lived from now on.

the pr 46 version seems to have stopped working today

I wonder if it might be location based? At the moment, it is still working for me. What error are you getting? and I'll see if I can recreate/play with it on my end too :)

interesting. it worked on my linux system but not wsl2 on windows

@pcause sorry I haven't responded in a bit for this, for WSL issue, I am afraid I am not have much success getting my windows & hardware to work with wsl in general to effectively troubleshoot (this is a me issue on my part) :(

np. figured it out. was the python issue that someone else posted about separately

:wave: Team,

I adjusted the script to not use python, and added a check for bc for use with NO_COLOR recommended by @milanico2309

At first I was going to try to stick with python, but then I was worried about users who require python2 and then I was trying to find logic to get around that, tl'dr ... it got messy.

I think its also faster now :thinking:

pr45 version - there is a small bug. then computing the percentage change it should be scale=4. bc will calculate to 4 decimal places and the multiply result will give you a percent and factional percent result with this change.

Is there some way to get a clean version. it is hard to find the latest.

👋 @pcause

I have my fork here with the master branch currently what I am running for my day-to-day. (In all openness, I am uncertain if it's bug free, but just let me know and Ill be happy to review)

the one I have uses bc but that version doesn't. it has:

percentChange=$(printf "%.2f" $(echo "scale=4; (($currentPrice - $previousClose) / $previousClose) * 100" | bc))

(original had scale=2)

seems you changed at some point?

Ah yes! I remember now, yes, I was also using bc originally, but I kept running against math'ing errors that I couldn't quite figure out. Ran it through AI and it suggested my issue was something to do with bc and floating-point arithmetic and routing or some other way above my head. The AI made the awk suggestion to use instead and so far 🤞 🤞

interesting. i've been using the bc version without issues other than the one above.

I'd be happy to revert and try that scale=2 variable. Not sure if that was something I tried to adjust when trying to get it to work. Might need a bit of time to play with it.

not worth the effort. i'll grab your version but stash away the one i'm using