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

[FIXED] Do not unlock here, will panic server. #5571

Merged
merged 1 commit into from
Jun 20, 2024
Merged

Conversation

derekcollison
Copy link
Member

Resolves: #5570

Signed-off-by: Derek Collison derek@nats.io

Signed-off-by: Derek Collison <derek@nats.io>
@derekcollison derekcollison requested a review from a team as a code owner June 20, 2024 09:14
Copy link
Member

@neilalexander neilalexander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@derekcollison derekcollison merged commit 5749c41 into main Jun 20, 2024
4 checks passed
@derekcollison derekcollison deleted the fix-5570 branch June 20, 2024 09:40
derekcollison pushed a commit that referenced this pull request Jun 21, 2024
…subject transform (#5574)

In some cases a bad subject transform could still pass the validation
test that is part of the config check when updating a stream config, and
no error would be returned. Now return an error when trying to update a
stream config with a source that has a bad subject transform that is not
caught by the subject transform destination check in the stream config
check.

Improves #5571

---------

Signed-off-by: Jean-Noël Moyne <jnmoyne@gmail.com>
neilalexander pushed a commit that referenced this pull request Jun 21, 2024
…subject transform (#5574)

In some cases a bad subject transform could still pass the validation
test that is part of the config check when updating a stream config, and
no error would be returned. Now return an error when trying to update a
stream config with a source that has a bad subject transform that is not
caught by the subject transform destination check in the stream config
check.

Improves #5571

---------

Signed-off-by: Jean-Noël Moyne <jnmoyne@gmail.com>
wallyqs added a commit that referenced this pull request Jun 21, 2024
Includes:

* #5571 
* #5082
* #5573
* #5574
* #5575
* #5577
* #5578
* #5580 
* #5559 

Signed-off-by: Neil Twigg <neil@nats.io>
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.

nats-server panic when create a stream with a wrong mapping destination
2 participants