arrow_backRetour aux issues
OpenHands/OpenHands
#15694
Débutant
Ouvrirarrow_forward
Débutant
Ouvrirarrow_forward
Débutant
Ouvrirarrow_forward
Bug: Enable/disable skills toggle resets to enabled state unexpectedly
ecoDébutant
bug
good first issue
descriptionDescription
## Description
The enable/disable toggle for skills does not persist its state reliably. After disabling a skill, the toggle reverts back to the enabled state on its own after a short delay (~5 seconds).
## Steps to Reproduce
1. Open the Skills settings
2. Toggle a skill to: disabled -> enabled -> disabled
3. Wait ~ 5 seconds
4. Observe the toggle — it resets back to **enabled** without any user interaction
## Expected Behavior
The toggle state (enabled/disabled) persists after being set. If a skill is disabled, it should remain disabled until the user explicitly re-enables it.
## Actual Behavior
After setting a skill to disabled, the toggle reverts to enabled after ~5 seconds, suggesting the state change is not being saved or is being overwritten by a background sync/poll.
https://github.com/user-attachments/assets/c1344865-cec9-46c1-ac77-497607105e61
## Additional Notes
- Delay before revert is approximately 5 seconds (may indicate a polling interval overwriting local state)
- Intermittent — does not always reproduce, but occurs consistently enough to be noticeable
---
_This issue was created by an AI agent (OpenHands) on behalf of the user._
Issues similaires
lingdojo/kana-dojo
star3.2k
Poids du dépôt lourd
[Good First Issue] 🐡 Add new Japan Fact 251 - Beginner-Friendly Open-source Contribution
## 🟢 Good First Issue: Add Japan Fact #251 — Beginner-Friendly Open Source Contribution ![Time: <1 minute](https://img…
TypeScript
enhancement
help wanted
WasiqB/multiple-cucumber-html-reporter
star281
Poids du dépôt moyen
Error bucketing
It would be great to bucket the errors in different types i.e. Code exception, configuration exception, environmental e…
TypeScript
enhancement
help wanted
StellarLock/StellarLock
star0
Poids du dépôt léger
LP lock links omit the /token|lp/ URL segment, causing wrong-type lookups on the detail page
## Summary Lock detail links should include the lock's kind in the URL, e.g. `/app/lock/lp/:id` or `/app/lock/token/:i…
TypeScript
bug
good first issue