8000 Use query_port in async_query() calls by yousefalshaikh17 · Pull Request #1009 · py-mine/mcstatus · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Use query_port in async_query() calls #1009

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

Merged
merged 2 commits into from
May 13, 2025

Conversation

yousefalshaikh17
Copy link
Contributor

Primarily referring to commit 8202888.

Changes

Currently, query() makes use of the query_port value, but async_query() does not.

return await self._retry_async_query(Address(ip, self.address.port), tries=tries)

This PR introduces a small change to ensure that async_query() also utilizes the query_port value, making the behavior consistent with query().

Reasoning

The change ensures that the async_query() function behaves in a similar manner to query(). This should prevent potential issues for users who rely on the query_port value for their queries.

Tests

No additional tests should be needed, as the existing tests already cover the relevant scenarios. If further clarification or adjustments are required, I'd be happy to add them.

Based on upstream commit 8202888
Copy link
Member
@PerchunPak PerchunPak left a comment

Choose a reason for hiding this comment

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

Miss click, ignore me

@PerchunPak PerchunPak merged commit 6cb8bc8 into py-mine:master May 13, 2025
11 checks passed
@yousefalshaikh17 yousefalshaikh17 deleted the async-query-port-support branch May 13, 2025 08:51
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
0