Merging some more PRs, this time auto-mergable

[c0sc0]

see #32 #33 #34 #40

shout out to @alexshirley for the pandas refactor!

[c0sc0]

Confirmed the off-by-one bug (fixed it already), just ran the fixed script and it picked up $ADT, $DPHC, $DTSS, $FORD, and $HIHO for today

@SamPom100

[c0sc0]

Now tracking number of deviations from mean. The dynamic site handles multi-variate sorting so I cranked down the STD limit and it's working great!

(I commented out the customPrints because they were starting to slow down the script with a bunch of hits, left it there for testing purposes but everything's printed out at the end)

also started a todo list in the readme

[c0sc0]

Can now rescan directly from the dynamic web interface!

Will try rescanning on a timer and make the dynamic page auto refresh so I can toss this onto a Hetzner box or a DO droplet or something. In the meantime, this is LAN-only. Should really add a server-side mutex on reloading but whatever (don't want to give users that control anyways hahaha)

@SamPom100

Reloading

Reloaded

[c0sc0]

Also, the dynamic site (mostly the input validation) is hilariously broken on mobile (in portrait). Not really worried about it tbh. Just be careful ;)

edit: nevermind, flexbox fixes everything (except for the input). Ticker in table is still cut off but landscape looks good

[SamPom100]

new website looks good, but most people have been browsing from mobile so I'd like it to work in portrait and scale. Fixed the T-1 bug. Also, most of the feedback I got on reddit asked for easy variables to adjust, thats why I declare them above instead of as arguments.

[c0sc0]

I'm working on fixing portrait now (damn DataTables)

The reason I did it with member variables is so I can import the scanner module in a different script and change things up like i do in flask_server when rescanning

stonk_search = mainObj(_month_cuttoff=month_cut,_day_cuttoff=day_cut,_std_cuttoff=std_cut)

Will add command line arguments (eg, python market_scanner.py 6 3 9) and if they aren't provided, prompt the user to enter their cutoffs (and suggest defaults). Sounds like a good compromise!

[elizabethshirley]

Tyyyyler, wrap up this PR!

[c0sc0]

hahaha sorry I just kept on adding shit

[elizabethshirley]

Yeah, but no one else can effectively add or clean up while the PR is open

…

On Wed, Aug 5, 2020, 10:43 PM Tyler Cosculluela ***@***.***> wrote: hahaha sorry I just kept on adding shit — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#41 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACV54DGEW2WEIFCCXWPXP2DR7G75XANCNFSM4PSTFNXA> .

[Stjernex24]

Also, the dynamic site (mostly the input validation) is hilariously broken on mobile (in portrait). Not really worried about it tbh. Just be careful ;)

edit: nevermind, flexbox fixes everything (except for the input). Ticker in table is still cut off but landscape looks good

Only works for desktop atm got it. Noticed major delay for ticker ALIM around 3pm or so on mobile. What could I do to get the alert asap

[c0sc0]

am a GitHub scrub ;) will fix my shit when I get home

[c0sc0]

Tyyyyler, wrap up this PR!

wrapped! #49

[elizabethshirley]

👏👏👏👏 yaaaassssss Real talk, but I know (from dealing with enough juniors) you won't listen until you go through your first regression: You want logically short Pull-requests - like a feature or bug fix. When you have a regression, and you find the bug is in *this* PR, you won't feel like you lost all of this hard work, when you need to revert the merge on master. When you fail to merge reasonably, submitters also need to constantly update their PRs, to stay mergable, that makes their PR harder and harder to read too. The second point I was going to bring up was keep your git history clean, with `git rebase`, and find bugs with `git bisect`, but you'll have to discover those on your own ;)

…

On Thu, Aug 6, 2020, 3:37 AM Tyler Cosculluela ***@***.***> wrote: Tyyyyler, wrap up this PR! wrapped! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#41 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACV54DAF52453XDM76UM7MDR7ICMVANCNFSM4PSTFNXA> .