Modernize dependencies

[rtholmes]

Status

• Dependencies updated
• CircleCI updated

Overview

PR for fixing #428

• Node - existing: v12; current: v18 is LTS until 2025-05.
• Typescript - existing: 3.7.2; current: v4.8.4.
• Mongo - existing: 3.0.2; current: v5 is LTS until 2025. NOTE: just using the mongo:latest docker image.
• Restify v10

Notes worth knowing

• node-fetch has to stay at v2.X; v3 only supports ESM modules (which we don't want to transition to).

[coveralls]

Pull Request Test Coverage Report for Build d73ae85f-f1f1-4087-a108-236b4f50fea8

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 77 unchanged lines in 4 files lost coverage.
• Overall coverage increased (+0.1%) to 89.586%

---

Files with Coverage Reduction	New Missed Lines	%
src/server/BackendServer.ts	2	95.08%
src/server/common/ClasslistAgent.ts	3	95.52%
src/server/common/GeneralRoutes.ts	11	92.47%
src/controllers/GitHubActions.ts	61	88.75%

Totals
Change from base Build 6ba4e95e-c4ee-4e73-8a87-763e7010abd8:	0.1%
Covered Lines:	3634
Relevant Lines:	3987

---

💛 - Coveralls

[rtholmes]

Currently broken because of restify node18 problem.

Issue: restify/node-restify#1925
PR: restify/node-restify#1906

Sadly the public links to these projects cannot be hidden, sorry if you're here from Restify :(

[winstan]

Restify supports node18 today via:
PR: restify/node-restify#1929

[rtholmes]

@winstan This seems to be ready to try on a host. I can't merge to master because 310 is still taking changes and I don't want to risk the changes to the DB/Node this late in the term.

Is there a dev instance somewhere we can spin up from this PR?

[winstan]

I don't think you meant to change the container from nginx to node... I think you meant to change it to this?
FROM nginx:stable-alpine

[rtholmes]

fixed, good catch!

[rtholmes]

Also @winstan, if you happen to know what mongo image to use other than mongo:latest, I really struggled for the right version. v5 is in LTS, but v6 is out: it would be nice to have a v5latest image, but I couldn't find one.

[winstan]

Also @winstan, if you happen to know what mongo image to use other than mongo:latest, I really struggled for the right version. v5 is in LTS, but v6 is out: it would be nice to have a v5latest image, but I couldn't find one.

Sorry, nope. :(

[winstan]

@rtholmes : Dev hosts: classy-dev and cs210-dev. I've given you access to both. (Talk to Paul about cs210-dev.)
Be sure to use /opt/classy-scripts/fix-classy to reset permissions on /var/opt/classy so you can make changes (like nuke the database)
I got it to build on classy-dev, but the database isn't happy...

[winstan]

If you want a cs310-dev host, send a request to help@cs...

[rtholmes]

Also @winstan, if you happen to know what mongo image to use other than mongo:latest, I really struggled for the right version. v5 is in LTS, but v6 is out: it would be nice to have a v5latest image, but I couldn't find one.

Sorry, nope. :(

I almost wonder if we want to use mongo:5.0.14, just so we can be in control of updating the mongo image? I'm fine with node:lts-alpine since it's v18 and should be for a few years.

[winstan]

Playing some more with getting the db to run... Complained of missing processor extension AVX. I found a way to update the processor model for the VM and now everything seems to start up and run fine. (classy-dev)
I need to update the processor model for all Classy boxes now...

[rtholmes]

@winstan glad you got it going! I'm running a modern mongo on my local dev instance so the db behaviours should be ok, but I never thought about that kind of problem! I do know they changed the auth mechanism though (there have been warnings on the terminal for a while) so I'll have to look into those (next week) and see whether I need to change how we open connections to mongo.

[rtholmes]

@winstan I moved 310 onto a branch so this is probably good to merge to master. This might also be a good time (after the merge) to rename master to main, is that ok with you?

[winstan]

@winstan I moved 310 onto a branch so this is probably good to merge to master. This might also be a good time (after the merge) to rename master to main, is that ok with you?

Sure, sounds good.