Merge upstream v0.68.3 → v0.68.22#4
Merged
Conversation
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…s--master--components--gate chore(master): release 0.68.3
…26.1 (minekube#840) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: minekube-release-cascade[bot] <297156081+minekube-release-cascade[bot]@users.noreply.github.com>
…s--master--components--gate chore(master): release 0.68.4
…35.1 (minekube#842) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…s--master--components--gate chore(master): release 0.68.5
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…s--master--components--gate chore(master): release 0.68.6
…27.1 (minekube#847) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…s--master--components--gate chore(master): release 0.68.7
Co-authored-by: minekube-release-cascade[bot] <297156081+minekube-release-cascade[bot]@users.noreply.github.com>
…s--master--components--gate chore(master): release 0.68.8
…kube#853) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…s--master--components--gate chore(master): release 0.68.9
…28.1 (minekube#855) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…s--master--components--gate chore(master): release 0.68.15
…30.1 (minekube#876) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…s--master--components--gate chore(master): release 0.68.16
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…s--master--components--gate chore(master): release 0.68.17
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…s--master--components--gate chore(master): release 0.68.18
…se-without-queued-pack fix(java): ignore untracked modern resource pack responses
…s--master--components--gate chore(master): release 0.68.19
…inekube#883) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…s--master--components--gate chore(master): release 0.68.20
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…s--master--components--gate chore(master): release 0.68.21
…s--master--components--gate chore(master): release 0.68.22
…02.1 (minekube#891) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Zieht die aktuellen Upstream-Änderungen von minekube/gate (v0.68.3 → v0.68.22) in unseren Fork.
Relevantester Fix darunter: "queue config plugin messages during backend login"
(minekube/gate@ccc6212) — betrifft session_client_config.go / handlePluginMessage,
den Bereich, der im Verdacht steht, für die zufälligen Spieler-Timeouts verantwortlich
zu sein (Read-Loop bleibt hängen, wenn ein async gefeuertes PluginMessageEvent nie
zurückkehrt; Gate merkt den Disconnect dann nie, Spieler bleibt intern "verbunden").
Der Fix entschärft das Problem, indem Plugin-Messages während der Config-Phase
zwischengespeichert werden, solange der Backend-Server noch nicht vollständig bereit
ist — reduziert das Zeitfenster, in dem der riskante Code-Pfad überhaupt erreicht wird.
Konflikte gab es nur in .release-please-manifest.json und CHANGELOG.md (reine
Metadaten/Doku, keine Code-Konflikte). Der eigentliche Code wurde automatisch
sauber gemergt.
Nicht lokal gebaut/getestet (kein Go-Setup vorhanden) — bitte vor Merge in CI
oder lokal verifizieren.