Skip to content

Conversation

@ManethKulatunge
Copy link
Contributor

@ManethKulatunge ManethKulatunge commented Dec 30, 2019

Tickets:

List of changes:

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update

How has this been tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Added many integration tests, and also did some manual postman tests.

Questions for code reviewers?

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • Listed change(s) in the Changelog
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have made corresponding changes to the documentation
  • Any dependent changes have been merged and published in downstream modules

@ManethKulatunge ManethKulatunge changed the title Feature/153 accept multiple hackers Feature/153 accept multiple hackers (batchAccept) Dec 30, 2019
Ty-Won
Ty-Won previously requested changes Jan 1, 2020
Copy link
Member

@Ty-Won Ty-Won left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we write some tests for this new route? The code seems okay at a glance but I would like to have something that checks the functionality

@ManethKulatunge ManethKulatunge force-pushed the feature/153-accept-multiple-hackers branch from 63d8cc8 to 2722d76 Compare January 11, 2020 07:33
@pierreTklein pierreTklein requested review from Ty-Won and logan-r and removed request for Ty-Won July 26, 2020 04:53
@pierreTklein
Copy link
Member

pierreTklein commented Jul 26, 2020

@loreina @logan-r please have a look now at the code. I finished this code, added tests, and also manually tested.

After this goes in, we will need to do the following:

  1. npm run seed to add the new route
  2. npm run docs to generate the docs

@pierreTklein pierreTklein dismissed Ty-Won’s stale review July 26, 2020 05:31

Ty-won is no longer part of HackMcGill

@krubenok
Copy link
Member

krubenok commented Jul 26, 2020

🚨DANGER🚨

We still don't know how to repeatedly fix DB incompatibilities that we suspect are caused by npm run seed. See the great chaos of production roll out circa December 2019.

@pierreTklein
Copy link
Member

Lemme see if I can rewrite npm run seed to be less dangerous, lol

Copy link
Member

@loreina loreina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, just had a few comments

also I don't think we should run npm run seed now with its issues. if we keep it as is, we should only run it once a year right before apps launch. it's pending a refactor sometime this year before apps do drop tho @pierreTklein if you can look into it that would be epic ❤️

@loreina loreina changed the title Feature/153 accept multiple hackers (batchAccept) feat: add batchAccept route to accept multiple hackers at once Jul 26, 2020
@loreina
Copy link
Member

loreina commented Jul 26, 2020

for npm run docs is there a way to trigger between v1, v2, v3? we'd probably have to do some back tracing to config that tho

@krubenok
Copy link
Member

we should only run it once a year right before apps launch.

I disagree. If we can gain confidence in npm run seed it should be part of the CI/CD for deploying to production.

@loreina loreina closed this Jul 26, 2020
@loreina loreina reopened this Jul 26, 2020
@loreina
Copy link
Member

loreina commented Jul 26, 2020

accident 🙃

Copy link
Member

@loreina loreina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry didn't see hacker.middleware.js before, looks great !!

@pierreTklein
Copy link
Member

#652 fixes all of our worries about npm run seed. We should be able to integrate it with CI/CD in the future.

That being said, there is a brief moment when running the script where NOBODY has permissions (we basically do a DROP TABLE; CREATE TABLE), so it's probably worth disabling npm run seed when apps are open / near deadline.

@pierreTklein pierreTklein merged commit 28e074f into develop Jul 27, 2020
@pierreTklein pierreTklein deleted the feature/153-accept-multiple-hackers branch July 27, 2020 01:58
@loreina loreina mentioned this pull request Jul 30, 2020
16 tasks
loreina pushed a commit that referenced this pull request Jul 30, 2020
* feat: Add HACKER_UPDATE_BATCH success message

* feat: Add promise.allsettled so that we can wait for many promises to complete

* feat: Add findByHackerId function to Account

* feat: Add updatedHackerBatch controller function, generalize validation function, fix router

* fix: resolve bug where requests hang when response is null

* feat: set route apiVersion number to be 3.0.0

* feat: create parseAcceptBatch

Co-authored-by: Pierre Theo Klein <pierre.klein@mail.mcgill.ca>
janekhuong pushed a commit that referenced this pull request Oct 30, 2025
* feat: Add HACKER_UPDATE_BATCH success message

* feat: Add promise.allsettled so that we can wait for many promises to complete

* feat: Add findByHackerId function to Account

* feat: Add updatedHackerBatch controller function, generalize validation function, fix router

* fix: resolve bug where requests hang when response is null

* feat: set route apiVersion number to be 3.0.0

* feat: create parseAcceptBatch

Co-authored-by: Pierre Theo Klein <pierre.klein@mail.mcgill.ca>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants