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

Fixes #1122 But in port service lookup that caused multiple entries of Port with same port number but different service name/description #1317

Merged
merged 13 commits into from
Jul 20, 2024

Conversation

yogeshojha
Copy link
Owner

  • Port service lookup is by default using whatportis, but when it fails, python's built in socket library will be used to query service name (no plans to remove whatportis anytime soon)
  • get_or_create was creating multiple entries of same port with different service name and description, in cases where whatportis fails. A new util function has been created to update the port info if it exists otherwise create it.
  • A tiny UI bug where badges for ports cannot take the entire row length has also been fixed.

… and running service from whatportis or socket, added db function to update or create port based on service name or description
@yogeshojha yogeshojha self-assigned this Jul 20, 2024
@yogeshojha yogeshojha linked an issue Jul 20, 2024 that may be closed by this pull request
1 task
Copy link
Contributor

👋 Hi @yogeshojha,
Thank you for sending this pull request.
Please make sure you have followed our contribution guidelines.
We will review this PR as soon as possible. Thank you for your patience.

@yogeshojha yogeshojha merged commit 2a2ce2c into master Jul 20, 2024
6 checks passed
@yogeshojha yogeshojha deleted the 1122-bug-port-not-correctly-recognized branch July 20, 2024 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug: port not correctly recognized
1 participant