-
Notifications
You must be signed in to change notification settings - Fork 23
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
Added SecondChance algorithm to allow you to retry importing nodes th… #247
Merged
matkonnerth
merged 3 commits into
open62541:master
from
xydan83:Feature-issue246-add-second-chance-for-nodes-without-parents
Dec 13, 2023
Merged
Added SecondChance algorithm to allow you to retry importing nodes th… #247
matkonnerth
merged 3 commits into
open62541:master
from
xydan83:Feature-issue246-add-second-chance-for-nodes-without-parents
Dec 13, 2023
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
xydan83
changed the title
Added SecondChance algorithm to allow you to retry importing nodes th…
[draft] Added SecondChance algorithm to allow you to retry importing nodes th…
Dec 8, 2023
Great job, thanks for the PR. I've added a comment, feel free to ask questions. |
matkonnerth
reviewed
Dec 8, 2023
xydan83
force-pushed
the
Feature-issue246-add-second-chance-for-nodes-without-parents
branch
from
December 11, 2023 09:10
7cd8fb5
to
b3ec7ed
Compare
Hello! I changed some details and included the container in the addNodeImpl function. NL_Node no longer has StatusCode. Look here please. |
xydan83
force-pushed
the
Feature-issue246-add-second-chance-for-nodes-without-parents
branch
3 times, most recently
from
December 11, 2023 09:32
8e73796
to
9e3c680
Compare
…at could not be imported because they did not find their parents. This may be the case if we have a node type of Object which has its own parent node type of Variable. For example, this could be a HasHistoricalConfiguration reference type. Also, the status about how many nodes we have imported shows numbers that include nodes that were not imported due to some error.
xydan83
force-pushed
the
Feature-issue246-add-second-chance-for-nodes-without-parents
branch
from
December 11, 2023 09:55
9e3c680
to
e4a3eed
Compare
Added a couple of tests. |
xydan83
changed the title
[draft] Added SecondChance algorithm to allow you to retry importing nodes th…
Added SecondChance algorithm to allow you to retry importing nodes th…
Dec 12, 2023
Thank you, good job! |
xydan83
deleted the
Feature-issue246-add-second-chance-for-nodes-without-parents
branch
December 14, 2023 07:35
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.
…at could not be imported because they did not find their parents. This may be the case if we have a node type of Object which has its own parent node type of Variable. For example, this could be a HasHistoricalConfiguration reference type. Also, the status about how many nodes we have imported shows numbers that include nodes that were not imported due to some error.