Issue 756 fixed the graphd crashed. #760
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
This time only temporarily avoided this crash, In issue vesoft-inc#192, I will solve this problem for better.
monadbobo
requested review from
dutor,
CPWstatic,
dangleptr,
laura-ding and
jude-zhu
|
jenkins go! |
CPWstatic
approved these changes
Aug 13, 2019
|
Unit testing passed. |
|
Unit testing passed. |
yixinglu
pushed a commit
to yixinglu/nebula
that referenced
this pull request
Feb 16, 2020
This time only temporarily avoided this crash, In issue vesoft-inc#192, I will solve this problem for better.
tong-hao
pushed a commit
to tong-hao/nebula
that referenced
this pull request
Jun 1, 2021
This time only temporarily avoided this crash, In issue vesoft-inc#192, I will solve this problem for better.
liwenhui-soul
pushed a commit
to liwenhui-soul/nebula
that referenced
this pull request
May 10, 2022
<!-- Thanks for your contribution! In order to review PR more efficiently, please add information according to the template. --> ## What type of PR is this? - [ ] bug - [ ] feature - [X] enhancement ## What problem(s) does this PR solve? #### Issue(s) number: close vesoft-inc#3815 #### Description: when releasing a nebula PATCH version(z version of x.y.z), create git tag on one same branch rather than a new branch, such as: ```text release-3.2 -----+----------+------- branch \ \ v3.2.0 v3.2.1 tag ``` ## How do you solve it? use github action manual trigger to package rc version. ## Special notes for your reviewer, ex. impact of this fix, design document, etc: ## Checklist: Tests: - [ ] Unit test(positive and negative cases) - [ ] Function test - [ ] Performance test - [X] N/A Affects: - [ ] Documentation affected (Please add the label if documentation needs to be modified.) - [ ] Incompatibility (If it breaks the compatibility, please describe it and add the label.） - [ ] If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).) - [ ] Performance impacted: Consumes more CPU/Memory ## Release notes: None Please confirm whether to be reflected in release notes and how to describe: > ex. Fixed the bug ..... None Migrated from vesoft-inc#4105 Co-authored-by: Yee <[email protected]>
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.
This time only temporarily avoided this crash,
In issue #192, I will solve this problem for better.