-
Notifications
You must be signed in to change notification settings - Fork 3
Compulsively optimize async calls #80
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
base: master
Are you sure you want to change the base?
Compulsively optimize async calls #80
Conversation
KyleBrownCS
left a comment
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.
Didn't run it to test, but looks good
James-Firth
left a comment
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.
Looks good just needs a manual test on the live deployment :)
James-Firth
left a comment
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.
Looks like something wasn't working :(
src/lib/slack/common.js
Outdated
| async function generateAndSendBootMessage(channel = null, { msgText = null } = {}) { | ||
| const { available, benched } = await users.listAllUserNamesByAvailability(); | ||
| const SHA = await simpleGit.revparse(['HEAD']); | ||
| const [{ availableUsers, benchedUsers }, SHA] = await Promise.all([ |
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 think there's an edge-case here.
it generated the initial boot message fine but then admins saying overview was giving an empty list back.
Collapse async calls to run concurrently where possible.