dockertest icon indicating copy to clipboard operation
dockertest copied to clipboard

Cassandra Example

Open vtereso opened this issue 4 years ago • 4 comments

Describe the bug

The Cassandra example does not work. I am not sure what has changed, but the session consistently errors within the retry with the following: connect: connection refused.

To Reproduce

Run the Cassandra Example. I believe all tags fail.

Expected behavior

A gocql session should be returned.

Environment

  • Version: dockertest (github.com/ory/dockertest/v3) v3.7.0
  • Environment: MacOS Big Sur (11.5.2), Docker (v20.10.7)

vtereso avatar Sep 08 '21 22:09 vtereso

The mount appears to be problematic: Mounts: []string{"/tmp/local-cassandra:/etc/cassandra"}. Also, in older versions of gocql, the host lookup needs to be disabled: DisableInitialHostLookup.

vtereso avatar Sep 09 '21 21:09 vtereso

Should I update the example with these changes?

vtereso avatar Sep 09 '21 21:09 vtereso

Yes please!

aeneasr avatar Sep 10 '21 10:09 aeneasr

@vtereso are you still facing the issue ? I think the mount is working perfectly fine , we don't need any changes in cassandra example .

@aeneasr If we have no further problem on this, then we can close the issue .

scortier avatar Jan 21 '22 19:01 scortier

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas on how you could contribute towards resolving it;
  • leave a comment and describe in detail why this issue is critical for your use case;
  • open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

github-actions[bot] avatar Jan 22 '23 00:01 github-actions[bot]