-
Notifications
You must be signed in to change notification settings - Fork 314
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
Asset configuration reseted after uploading new channels #2639
Comments
Hi, are the configurations that get deleted already saved or are you uploading your channels before applying changes? In case of the latter it is intended to work that way. |
Yes, I saved the configurations before uploading the channels |
@manuelfa we tried to reproduce the issue but, unfortunately, we couldn't confirm it. Could you please provide us with more details, maybe the configuration you are using so that we can double-check? |
I tried to reproduce it with the "normal" kura version but the bug appears too @MMaiero what kind of detail will help, the snapshot0 ? |
@manuelfa Thank you for the prompt response. That's definitely a bug. Thank you for reporting. |
"Upload Channels" causes the reset of asset configurations like the timestamp.mode
Steps to reproduce the behavior:
Expected behavior
Kura maintains the configuraton during the channel-update
Target Environment:
Additional context
We are working with a self-configured version of Kura 4.1.
It would be interesting if someone is able to reproduce this bug in order to know that this problem is not caused by our own changes.
The text was updated successfully, but these errors were encountered: