Skip to content

Hotfix/v0.1.2#47

Merged
thinker8581 merged 7 commits intorelease-0.1from
hotfix/v0.1.2
Dec 23, 2025
Merged

Hotfix/v0.1.2#47
thinker8581 merged 7 commits intorelease-0.1from
hotfix/v0.1.2

Conversation

@weilaaa
Copy link
Collaborator

@weilaaa weilaaa commented Dec 23, 2025

Description

Add a concise overview of what this PR aims to achieve. Reference related GitHub issues and PRs.

Fixes # (issue)

PR Title Format

Please format the PR title as {type}: {description}.

  • Types: feat, fix, refactor, chore, test, docs.
  • Example: feat: support new llm provider

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactoring (no functional changes, no api changes)

Testing

Please describe the tests that you ran to verify your changes. For UI changes or specific hardware integration, please provide screenshots or logs.

  • Unit Tests
  • Manual Verification
  • End-to-End Tests

API and Design Changes (Optional)

If this PR introduces API changes or complex design modifications, please describe them here.

# Example usage if applicable

Checklist

  • My code follows the style guidelines of this project.
  • I have run pre-commit run --all-files to ensure code quality.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation.
  • I have added tests that prove my fix is effective or that my feature works.

weilaaa and others added 7 commits December 23, 2025 10:43
Make timeout of zabbix and intelligent threshold configurable
…ata (#41)

Change-Id: Ie529ccfd7e99c843fc6457d423782a6cd735bf1c

## Description

> Add a concise overview of what this PR aims to achieve. Reference
related GitHub issues and PRs.

Fixes # (issue)

## PR Title Format

Please format the PR title as `{type}: {description}`.
- **Types**: `feat`, `fix`, `refactor`, `chore`, `test`, `docs`.
- **Example**: `feat: support new llm provider`

## Type of Change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Documentation update
- [ ] Refactoring (no functional changes, no api changes)

## Testing

> Please describe the tests that you ran to verify your changes. For UI
changes or specific hardware integration, please provide screenshots or
logs.

- [ ] Unit Tests
- [ ] Manual Verification
- [ ] End-to-End Tests

## API and Design Changes (Optional)

> If this PR introduces API changes or complex design modifications,
please describe them here.

```python
# Example usage if applicable
```

## Checklist

- [ ] My code follows the style guidelines of this project.
- [ ] I have run `pre-commit run --all-files` to ensure code quality.
- [ ] I have performed a self-review of my own code.
- [ ] I have commented my code, particularly in hard-to-understand
areas.
- [ ] I have made corresponding changes to the documentation.
- [ ] I have added tests that prove my fix is effective or that my
feature works.
#45)

> Add a concise overview of what this PR aims to achieve. Reference
related GitHub issues and PRs.

Fixes # (issue)

Please format the PR title as `{type}: {description}`.
- **Types**: `feat`, `fix`, `refactor`, `chore`, `test`, `docs`.
- **Example**: `feat: support new llm provider`

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Documentation update
- [ ] Refactoring (no functional changes, no api changes)

> Please describe the tests that you ran to verify your changes. For UI
changes or specific hardware integration, please provide screenshots or
logs.

- [ ] Unit Tests
- [ ] Manual Verification
- [ ] End-to-End Tests

> If this PR introduces API changes or complex design modifications,
please describe them here.

```python
```

- [ ] My code follows the style guidelines of this project.
- [ ] I have run `pre-commit run --all-files` to ensure code quality.
- [ ] I have performed a self-review of my own code.
- [ ] I have commented my code, particularly in hard-to-understand
areas.
- [ ] I have made corresponding changes to the documentation.
- [ ] I have added tests that prove my fix is effective or that my
feature works.
Description
This PR improves the display of labels in the Intelligent Threshold
Cleaning Result table.
Previously, long labels were not properly truncated, causing layout
issues. This change:

Truncates long labels with an ellipsis (...) by limiting the maximum
width.
Adds a tooltip that displays the full label content on hover for better
readability.
Utilizes Tailwind CSS for styling the tooltip wrapper.
Type of Change
 Bug fix (non-breaking change which fixes an issue)
 New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality
to not work as expected)
 Documentation update
 Refactoring (no functional changes, no api changes)
Testing
Verified the changes locally:

Checked the "Cleaning Result" table in the Intelligent Threshold Task
Configuration.
Confirmed that long labels are now truncated with an ellipsis.
Confirmed that hovering over a truncated label correctly displays the
full text in a tooltip.
## Description

> Add a concise overview of what this PR aims to achieve. Reference
related GitHub issues and PRs.

Fixes # (issue)

## PR Title Format

Please format the PR title as `{type}: {description}`.
- **Types**: `feat`, `fix`, `refactor`, `chore`, `test`, `docs`.
- **Example**: `feat: support new llm provider`

## Type of Change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Documentation update
- [ ] Refactoring (no functional changes, no api changes)

## Testing

> Please describe the tests that you ran to verify your changes. For UI
changes or specific hardware integration, please provide screenshots or
logs.

- [ ] Unit Tests
- [ ] Manual Verification
- [ ] End-to-End Tests

## API and Design Changes (Optional)

> If this PR introduces API changes or complex design modifications,
please describe them here.

```python
# Example usage if applicable
```

## Checklist

- [ ] My code follows the style guidelines of this project.
- [ ] I have run `pre-commit run --all-files` to ensure code quality.
- [ ] I have performed a self-review of my own code.
- [ ] I have commented my code, particularly in hard-to-understand
areas.
- [ ] I have made corresponding changes to the documentation.
- [ ] I have added tests that prove my fix is effective or that my
feature works.
@weilaaa weilaaa requested a review from thinker8581 December 23, 2025 06:52
@thinker8581 thinker8581 merged commit c45a3dd into release-0.1 Dec 23, 2025
8 checks passed
@thinker8581 thinker8581 deleted the hotfix/v0.1.2 branch December 23, 2025 06:57
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.

5 participants