Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft: feat: implement markDead and markAlive in Connection [CCI] #477

Closed
wants to merge 2 commits into from

Conversation

timursaurus
Copy link
Collaborator

@timursaurus timursaurus commented Apr 6, 2023

Description

Implements markDead and markAlive in the Connection class

Check List

  • New functionality includes testing.
    • All tests pass
  • Linter check was successfull - yarn run lint doesn't show any errors
  • Commits are signed per the DCO using --signoff
  • Changelog was updated.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@timursaurus timursaurus changed the title feat: implement markDead and markAlive in Connection Draft: feat: implement markDead and markAlive in Connection [CCI] Apr 6, 2023
url: new URL('http://localhost:9200'),
});
connection.markDead();
connection.markAlive();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So is this code allowed?

connection.markDead();
connection.markDead();

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see why not?

@timursaurus timursaurus marked this pull request as draft April 12, 2023 10:06
@nhtruong
Copy link
Collaborator

Too stale

@nhtruong nhtruong closed this Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants