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

fix: better error message for ./risedev d timeout #18756

Merged
merged 1 commit into from
Sep 29, 2024

Conversation

yihong0618
Copy link
Contributor

@yihong0618 yihong0618 commented Sep 29, 2024

For the reason when use ./risedev d failed to start, when the server and port is in used the error only shows failed to wait for closing This patch make the message better. Also make docker kill the containers named risingwave(which started by docker-compose.

when start docker-compose

cd risingwave/integration_tests/ad-ctr
docker compose up -d

then forget to close the docker container by compose down
./risedev d error message only failed to wait for closing this path make the error message better
also fix the ./risedev k only kill the container named risedev this patch add risingwave name to
./risedev k to make it easy to use

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Checklist

  • I have written necessary rustdoc comments
  • I have added necessary unit tests and integration tests
  • I have added test labels as necessary. See details.
  • I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
  • My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
  • All checks passed in ./risedev check (or alias, ./risedev c)
  • My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)
  • My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

  • My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

For the reason when use `./risedev d` failed to start, when the
server and port is in used the error only shows `failed to wait
for closing` This patch make the message better. Also make docker
kill the containers named risingwave(which started by
docker-compose.

Signed-off-by: yihong0618 <[email protected]>
Copy link
Member

@fuyufjh fuyufjh left a comment

Choose a reason for hiding this comment

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

Thanks!

@@ -713,7 +713,7 @@ ${TMUX} list-windows -F "#{window_name} #{pane_id}" \
| xargs -I {} ${TMUX} send-keys -t {} C-c

# Stop docker components
containers=$(docker ps -a -q -f name=risedev- 2>/dev/null) || true
containers=$(docker ps -q -f name='risedev|risingwave'- 2>/dev/null) || true
Copy link
Member

Choose a reason for hiding this comment

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

The risedev k command is only supposed to kill services started by risedev 🤔. But I don't mind too much it killing other risingwaves anyway.

Copy link
Member

Choose a reason for hiding this comment

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

I find it a bit weird though... since running two instances does not imply they are working on the same ports.

What if the developer intends to run one production instance with docker and one development instance with risedev together, for example, to compare their behaviors?

Copy link
Member

Choose a reason for hiding this comment

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

I guess a better way is to show the name of process which uses the port we need, and let the user to decide what to do next.

Copy link
Member

Choose a reason for hiding this comment

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

What if

I don't like to talk about imaginary problems, and I don't have preferences on this specific issue. 😄

I guess a better way is to show the name of process which uses the port we need, and let the user to decide what to do next.

elegant!

@xxchan xxchan added this pull request to the merge queue Sep 29, 2024
Merged via the queue into risingwavelabs:main with commit e6435e6 Sep 29, 2024
36 of 37 checks passed
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.

4 participants