Simen Bekkhus
Simen Bekkhus
First step https://github.com/jestjs/jest/releases/tag/v30.0.0-alpha.6
>It seems relatively important to me that we keep running CITGM on Alpine hosts because many people use it in production. Agreed. Anecdotally, but I don't think I've encountered any...
Hmm, doing `connection.execute(sqlx::raw_sql(&sql)).await?;` rather than `sqlx::raw_sql(&sql).execute(connection).await?;` seems to work. Any reason not to do that?
CI is very unhappy here 😅 Some of the updates landed in #292, but happy to update more deps if you can make CI pass 🙂
FYI, I won't merge if it drops Node 16 as I need that version to be supported in Jest. Which probably means `test-exclude` needs to wait a cycle
https://github.com/jestjs/jest/releases/tag/v30.0.0-alpha.7
@MurakamiKennzo what do you expect "correct coverage" to be? All `0`? Unless tests actually execute, we have no way of knowing the coverage
@villelahdenvuo that's a separate issue from the OP, please include a reproduction (maybe in a new issue)
Ah, sorry, I missed the step editing the test while watch mode was running. @stipsan thoughts on how to fix this? You're my goto "coverage in watch mode" guy :D