-
Notifications
You must be signed in to change notification settings - Fork 1
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
Plotly #341
Plotly #341
Conversation
Some notes:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't run the code, but here are my initial thoughts. Nothing too major, we could probably merge and address the comments later.
Applied most of the edits. Three things to note:
|
Responded to 1. I'll keep an eye on updates for the other 2, but I think if the 3rd issue isn't breaking anything, we can merge and deploy before the next contest starts. Let's see what's done by the 31st. |
Ok, I added some comments which hopefully cleared things up. I did not get into the step-by-step of the math, just explained the equations and what each block of code was doing. Yet another sporadic TypeError came up. Neither one I can reliably reproduce so I'm not sure if this is an artifact of the dev environment, but the two that have come up so far:
Sometimes I am getting a |
Theory: If |
Is it possible to have Edit: On second thought, looks like this wouldn't solve the issue of the memoized values that you mentioned. I think short-circuiting when |
Actually Based on how this error is not reproducible, it's possible the root cause it a fast refresh/hot reload in dev. I think we should check it out in staging / production, and re-investigate if it still happens live. |
Dashboard for analyzing user voting behavior