chriswininger
commented
1 year ago - Thread through Sequelize logging enabled/disabled flag properly so we're not constantly overwhelmed by sequelize logs
- Handle conditions where the app doesn't start properly more gracefully so the real issue is less likely to get masked by null pointers
- Upgrade testcontainers. The newer version of testcontainers, which is used to start and stop the db durring testing seems to play nicer with mac virutalized docker environments and m1/m2 hardware