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

Temp Workaround to recovery from bad string size, #432 #435

Closed
wants to merge 2 commits into from

Conversation

lanmaoxinqing
Copy link
Contributor

@lanmaoxinqing lanmaoxinqing commented Jun 17, 2021

Since the registry data is invalid, i simply empty the content to guarantee the next registry will work correctly.

lanmaoxinqing and others added 2 commits June 17, 2021 16:17
Since the registry data is invalid, i simply empty the content to guarantee the next registry will work correct.
gnodet pushed a commit to gnodet/mvnd that referenced this pull request Jun 18, 2021
…pache#433

Fix a possible write a long string in case where the string length is <= 1024 but the encoded size if > 1024.
Truncate long strings and warn instead of throwing an exception which could lead to an invalid registry.
Since the registry data is invalid, the content is emptied to guarantee the next registry will work correct.
This fix is based on apache#435 provided by lanmaoxinqing, many thanks !
gnodet pushed a commit to gnodet/mvnd that referenced this pull request Jun 18, 2021
…pache#433

Fix a possible write a long string in case where the string length is <= 1024 but the encoded size if > 1024.
Truncate long strings and warn instead of throwing an exception which could lead to an invalid registry.
Since the registry data is invalid, the content is emptied to guarantee the next registry will work correct.
This fix is based on apache#435 provided by @lanmaoxinqing, many thanks !
gnodet pushed a commit to gnodet/mvnd that referenced this pull request Jun 18, 2021
Fix a possible write a long string in case where the string length is <= 1024 but the encoded size if > 1024.
Truncate long strings and warn instead of throwing an exception which could lead to an invalid registry.
Since the registry data is invalid, the content is emptied to guarantee the next registry will work correct.
This fix is based on apache#435 provided by @lanmaoxinqing, many thanks !
@gnodet
Copy link
Contributor

gnodet commented Jun 18, 2021

Superseded by #439

@gnodet gnodet closed this Jun 18, 2021
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.

2 participants