OpsCenter 6.8.32 Release #125
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
msmygit
requested changes
Jan 11, 2024
OpsCenter_6.8_Release_Notes.md
Outdated
| ## Backup Service | ||
| * Add the missing key to details-sstables so opsc won't raise an incorrect error as backup failure (OPSC-17423) | ||
| * Improved test cases to add more value to fetch event store. (OPSC-17419) | ||
| * Clean stale backup/snapshot data when previous cleanup or the job failed in Sync Retry. (OPSC-17186) |
There was a problem hiding this comment.
Suggested change
| * Clean stale backup/snapshot data when previous cleanup or the job failed in Sync Retry. (OPSC-17186) | |
| * Clean-up stale backup/snapshot data when previous cleanup job failed or the job failed during Sync Retry step. (OPSC-17186) |
OpsCenter_6.8_Release_Notes.md
Outdated
| * Added Commitlog backups cache refresh button in commitlogs dialog. (OPSC-17403) | ||
|
|
||
| ## Core | ||
| * Publish failover and missing heartbeat after heartbeat_reply_period through event services (OPSC-17212) |
There was a problem hiding this comment.
Suggested change
| * Publish failover and missing heartbeat after heartbeat_reply_period through event services (OPSC-17212) | |
| * Publish failover and missing heartbeat after `heartbeat_reply_period` through event services (OPSC-17212) |
OpsCenter_6.8_Release_Notes.md
Outdated
| * Scripts for load testing stomp service (OPSC-17443) | ||
|
|
||
| ## UI | ||
| * Limit session to User Agent and IP (OPSC-17278) |
msmygit
requested changes
Jan 11, 2024
OpsCenter_6.8_Release_Notes.md
Outdated
| * Add the missing key to details-sstables so opsc won't raise an incorrect error as backup failure (OPSC-17423) | ||
| * Improved test cases to add more value to fetch event store. (OPSC-17419) | ||
| * Clean-up stale backup/snapshot data when previous cleanup job failed or the job failed during Sync Retry step. (OPSC-17186) | ||
| * Fixed bugs when running a backup using {{allow_one_failure}} when one agent is down. (OPSC-17421) |
There was a problem hiding this comment.
Suggested change
| * Fixed bugs when running a backup using {{allow_one_failure}} when one agent is down. (OPSC-17421) | |
| * Fixed bugs when running a backup using `{{allow_one_failure}}` when one agent is down. (OPSC-17421) |
There was a problem hiding this comment.
I know it's too late in the game, but shouldn't we name that field as {{allow_one_agent_failure}} instead for clarity?
msmygit
approved these changes
Jan 11, 2024
orion104
requested changes
Jan 11, 2024
OpsCenter_6.8_Release_Notes.md
Outdated
| 11 Jan 2024 | ||
|
|
||
| ## Backup Service | ||
| * Add the missing key to details-sstables so opsc won't raise an incorrect error as backup failure (OPSC-17423) |
There was a problem hiding this comment.
"Resolved and error when opscenterd encounters and unexpected key when processing backup status reports from nodes."
OpsCenter_6.8_Release_Notes.md
Outdated
|
|
||
| ## Backup Service | ||
| * Add the missing key to details-sstables so opsc won't raise an incorrect error as backup failure (OPSC-17423) | ||
| * Improved test cases to add more value to fetch event store. (OPSC-17419) |
There was a problem hiding this comment.
"Resolved various errors that occurred after a backup sync was deleted."
OpsCenter_6.8_Release_Notes.md
Outdated
| ## Backup Service | ||
| * Add the missing key to details-sstables so opsc won't raise an incorrect error as backup failure (OPSC-17423) | ||
| * Improved test cases to add more value to fetch event store. (OPSC-17419) | ||
| * Clean-up stale backup/snapshot data when previous cleanup job failed or the job failed during Sync Retry step. (OPSC-17186) |
There was a problem hiding this comment.
"Backup clean up code will now run after a sync retry."
OpsCenter_6.8_Release_Notes.md
Outdated
| * Clean-up stale backup/snapshot data when previous cleanup job failed or the job failed during Sync Retry step. (OPSC-17186) | ||
| * Fixed bugs when running a backup using `{{allow_one_failure}}` when one agent is down. (OPSC-17421) | ||
|
|
||
| ## Backup Service,UI |
There was a problem hiding this comment.
Move this to only be under the backup service rather than trying to display it in two places.
OpsCenter_6.8_Release_Notes.md
Outdated
| * Publish failover and missing heartbeat after `heartbeat_reply_period` through event services (OPSC-17212) | ||
|
|
||
| ## Core,TestEng | ||
| * Scripts for load testing stomp service (OPSC-17443) |
There was a problem hiding this comment.
Remove completely. We only need release notes for code changes that are customer facing. Tests and internal tool don't need release notes.
OpsCenter_6.8_Release_Notes.md
Outdated
| * Publish failover and missing heartbeat after `heartbeat_reply_period` through event services (OPSC-17212) | ||
|
|
||
| ## Core,TestEng | ||
| * Scripts for load testing stomp service (OPSC-17443) |
There was a problem hiding this comment.
Remove completely. We only need release notes for code changes that are customer facing. Tests and internal tool don't need release notes.
OpsCenter_6.8_Release_Notes.md
Outdated
| * Scripts for load testing stomp service (OPSC-17443) | ||
|
|
||
| ## UI | ||
| * Limit a session to a specific User Agent and IP address (OPSC-17278) |
There was a problem hiding this comment.
Change user agent to be lower case.
orion104
approved these changes
Jan 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release Notes Automation
If you name your pull-request as "Product x.y.z Release ...", after merging the
PR, a GitHub Action will automatically create a product version tag "product-x.y.z".
Supported product names are:
Version supports 3 sets or 4 sets of digits.