-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
MAX_PRICE_SERIES_RX6800XT= not being honored #1052
Comments
Anyone have ideas on this? I saw the other day on the discord server someone showing their logs, it looks like I should be seeing a message about the card being over the max set. |
Probably has to do with the container not correct. I'll do some testing. |
Reopen if it seems to persist. That should do it though. |
I'll grab the next nightly docker build and will test out. |
Is there anything you'd like me to look at as well? |
Is this still happening? |
when I ran into it last yes, but figured it might have been doing something wrong. I haven't been running app the last few days so not sure, can run again to see. |
Description
.env file has price set to 900 - This should cover MSRP prices but ignore insane prices. The hit was on a 3rd party selling of the card for $1699.
In testing I've set this max price to 100 to see if changes any behavior, it still seems to check stock so I'm not 100% how its suppose to look with the max price set. I've done the same with the 3080 max price and did not see any changes in the logs.
.env
:logs
:Running last night "nightly" docker code. (11/29/2020)
Hopefully if I'm missing something it will be pretty apparent, I guess I was thinking that if the card is above x price it wouldn't look for it, but I could see that it still needs to look / understand price, see its over max price and move on w/o alerting it's in stock...
If that's the case please inform and I'll close this PR.
Ugh I can't get the damn logs to format correctly. Sorry :\
edit (jef): no worries 😄 fixed it up for ya
The text was updated successfully, but these errors were encountered: