Skip to content

Fix master node error#126

Merged
qkaiser merged 2 commits intomainfrom
fix-master-node-error
Mar 24, 2026
Merged

Fix master node error#126
qkaiser merged 2 commits intomainfrom
fix-master-node-error

Conversation

@qkaiser
Copy link
Contributor

@qkaiser qkaiser commented Mar 18, 2026

LEB1/LEB2 contains multiple MasterNodes. The one with the largest cmt_no needs to be scanned, as that is the currently activated one.

Initially opened at #116 but it was opened from a fork's main branch and when I touched it it closed the entire PR.

LEB1/LEB2 contains multiple MasterNodes. The one with the largest cmt_no
needs to be scanned, as that is the currently activated one.
@qkaiser qkaiser force-pushed the fix-master-node-error branch from 1b7e735 to 2ccfb28 Compare March 18, 2026 17:11
@qkaiser qkaiser enabled auto-merge March 18, 2026 17:11
@qkaiser qkaiser requested a review from e3krisztian March 18, 2026 17:11
@qkaiser qkaiser self-assigned this Mar 18, 2026
@qkaiser
Copy link
Contributor Author

qkaiser commented Mar 18, 2026

I'm okay with the changes but since I had to open this I can't approve. Asking for @e3krisztian

@qkaiser qkaiser force-pushed the fix-master-node-error branch from 2ccfb28 to 8d4e881 Compare March 24, 2026 13:09
Calling os.utime with follow_symlinks to False on Windows errors out
with Python >= 3.12 on Windows.

See https://bugs.python.org/issue46490
@qkaiser qkaiser merged commit adfe20d into main Mar 24, 2026
@qkaiser qkaiser deleted the fix-master-node-error branch March 24, 2026 13:09
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.

3 participants