Mathieu Boudreau, PhD

Hum, looks like we had this issue recently in this PR: https://github.com/axondeepseg/axondeepseg/pull/777 For that one, it seems to have been related to memory consumption, but here the tests pass so...

Seems like the issues stems from using two different Coverals services; the pip coveralls for each parallel test running, and then the Github Actions coveralls service to combine them all...

The coveralls issue can be handled in it's own PR, I'll force approve this one

Thanks @joshuacwnewton ! Yes we should really regularly check the stale branches, I'll set myself a monthly reminder to check that, also find a mechanism to remind the person that...

Also, maybe a good idea to revisit #464, which was started to prevent the mistake I made in stoyan's branch of accidentally pushing large files. @joshuacwnewton do you guys have...

Cleaning up the branches cut down the repo size by slightly more than half: ``` (base) mathieuboudreau@Mathieus-MacBook-Pro cleanup % git clone https://github.com/axondeepseg/axondeepseg.git Cloning into 'axondeepseg'... remote: Enumerating objects: 6130, done....

Another thing we could do is for *users*, give them instructions in our docs to clone with a depth of 1, that should speed things up for them at least!

@joshuacwnewton just discovered that Github now has this option: https://github.blog/changelog/2024-04-18-push-rules-public-beta/

> Any ideas on how to fix this? thanks! > I am getting the same error when I give the Docker pipeline a T2w image to segment, @jcupitt any clue?