Barrett Strausser

@lunamidori5 Quick question. I didn't see a guide on contributing. Is there a typical developer flow people are using? Namely, test strategies?

@efekarakus A major limitation of Fargate is the caching story. In the AI/Robotics domain the images produced can be very large due to the size of the libraries. For instance...

I hit this as well. Think it is the same as - https://github.com/go-co-op/gocron/issues/706 What is happening is that https://github.com/go-co-op/gocron/blob/v2/executor.go#L306 sends out for reschedule but https://github.com/go-co-op/gocron/blob/v2/executor.go#L171 also does. The job doesn't...

I think your right, I missed that. In this case https://github.com/go-co-op/gocron/blob/v2/executor.go#L99 and https://github.com/go-co-op/gocron/blob/v2/executor.go#L135 are both rescheduling

Any update on this. Fargate has some severe limitations. Namely the well-known caching issue.

@lemire Is this issue still valid? I wanted to contribute - the good first issue list seems stale https://github.com/RoaringBitmap/roaring/contribute though

@lemire Once the validation stuff gets in I'll grab this. I think have a good enough grasp on the data structures to do this.

I recently update devcontainers to use the poetry flow. I can't reproduce this in my devcontainer (dind) using the integrated terminal. ``` (testcontainers-_53phrdA-py3.11) vscode ➜ /workspaces/testcontainers-python (feature/nats) $ poetry run...

I haven't contributed to this project before. I'll grab this as it looks not-stale and has the good first issue tag.

@qwerty287 I had looked at this, and it the scope wasn't obvious. I might be over-complicating it and the scope is smaller than I think My high-level thinking on this...