[obsolete] Bump mysql:mysql-connector-java from 5.1.36 to 8.0.28 in /commons#2
Closed
dependabot[bot] wants to merge 1 commit into
4.8beyond-aion/aion-server:4.8from
dependabot/maven/commons/mysql-mysql-connector-java-8.0.28beyond-aion/aion-server:dependabot/maven/commons/mysql-mysql-connector-java-8.0.28Copy head branch name to clipboard
Closed
[obsolete] Bump mysql:mysql-connector-java from 5.1.36 to 8.0.28 in /commons#2dependabot[bot] wants to merge 1 commit into4.8beyond-aion/aion-server:4.8from dependabot/maven/commons/mysql-mysql-connector-java-8.0.28beyond-aion/aion-server:dependabot/maven/commons/mysql-mysql-connector-java-8.0.28Copy head branch name to clipboard
dependabot[bot] wants to merge 1 commit into
4.8beyond-aion/aion-server:4.8from
dependabot/maven/commons/mysql-mysql-connector-java-8.0.28beyond-aion/aion-server:dependabot/maven/commons/mysql-mysql-connector-java-8.0.28Copy head branch name to clipboard
Conversation
Bumps [mysql:mysql-connector-java](https://github.com/mysql/mysql-connector-j) from 5.1.36 to 8.0.28. - [Changelog](https://github.com/mysql/mysql-connector-j/blob/release/8.x/CHANGES) - [Commits](mysql/mysql-connector-j@5.1.36...8.0.28) --- updated-dependencies: - dependency-name: mysql:mysql-connector-java dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
deleted the
dependabot/maven/commons/mysql-mysql-connector-java-8.0.28
branch
April 14, 2024 15:13
rrfarmer
added a commit
to rrfarmer/aion-server
that referenced
this pull request
Jun 9, 2026
…e/settings/titles/group/abyss/legion/fly-state/prison/flight-path/access; made Creature.GetEffectController virtual
rrfarmer
added a commit
to rrfarmer/aion-server
that referenced
this pull request
Jun 18, 2026
…er, HTMLCache) + refined blockers for the remaining 4 PeriodicInstanceManager (beyond-aion#3) + HTMLCache (beyond-aion#4) wired via real-data fixture seeds. The other 4 sit at a real floor: beyond-aion#1 SiegeService.initSieges + beyond-aion#5 PvpMapService need the heavy SPAWNS_DATA + world-map boot (beyond-aion#5 also breaks the empty-world invariant); beyond-aion#2 Housing is DB-required with no Java null guard; #6 PeriodicSaveService is a coordinated DI->singleton re-port. Documented precise blockers + recommended harnesses.
rrfarmer
added a commit
to rrfarmer/aion-server
that referenced
this pull request
Jun 18, 2026
…3 spawn-path faithfulness bugs New GameServerBootstrapTests.GameServerBootstrap_RealSpawnDataMaterializesNpcsIntoWorld: loads the REAL game-server data+cache (DataManager.LoadAsync(repoRoot)), brings up the real boot machinery (DataManager + World maps + IDFactory/ThreadPool bridges + AIEngine/ZoneService/GeoService), drives the faithful SpawnEngine.SpawnObject path over Sanctum's real SPAWNS_DATA, and asserts the World store materializes real Npc instances (357 NPCs incl. Euterpe 798173). End-to-end proof that the SPAWNS_DATA fix spawns NPCs (was 0). Three faithfulness fixes the spawn path surfaced: - GameServerBootstrapService: move engine-init to its Java-correct order (parallel, after DataManager, before the location-init/spawn services) - AIEngine must be up before any Npc spawn resolves its AI. - GameServerBootstrapService: bind IDFactory.RegisterInstance(_idFactory) after LockIds (every VisibleObject ctor reads IDFactory.GetInstance().NextId(); was a latent production boot NRE). - AIName: [AttributeUsage(Inherited=false)] to match Java's non-@inherited @ainame (SiegeNpcAI extends AggressiveNpcAI must NOT inherit "aggressive" -> was double-registering). Plus a defensive TypeLoad guard in OnClassLoadUnloadListener.DoMethodInvoke for the C# whole-AppDomain script scan (production unaffected). Siege/PvP wires (beyond-aion#1/beyond-aion#5) stay deferred in StartAsync: confirmed via Java source neither guards empty data (siege updateFortressNextState NREs on null getSiegeLocation; pvp init needs world map 301220000), so they cannot be unconditionally on under the minimal-fixture bootstrap. Full SpawnAll boot also needs a DB (beyond-aion#2 HousingService). Findings + recommended next documented in docs/next-slop-targets.md. Per-class GREEN: build 0, Bootstrap 8/8, Golden 167/167, RealStaticDataLoad 1/1.
rrfarmer
added a commit
to rrfarmer/aion-server
that referenced
this pull request
Jun 18, 2026
…ly confirms house-twin Java-latent throw Add opt-in env-gated [Fact] GameServerBootstrap_DbBackedFullBoot_RunsRealStartAsyncAgainstLiveMySql (early-returns unless AION_GAMESERVER_DB_INTEGRATION=1, mirroring SystemMailRepositoryDatabaseIntegrationTests DatabaseFactory/schema setup): points DatabaseFactory at 3307/aion_gs (root/aion), applies the real aion_gs.sql schema, loads the REAL DataManager (LoadAsync(repoRoot), 147MB cache + game-server/data), inits AIEngine/ ZoneService/GeoService, and runs the FULL GameServerBootstrapService.StartAsync via a pass-through IStaticDataLoader plus the real MySqlUsedIdRepository. EMPIRICAL RESULT (live container run): StartAsync THROWS the documented Java-latent house-twin DuplicateAionObjectException at SpawnEngine.SpawnAll -> HousingService.SpawnHouses -> World.StoreObject: Heiron(210040000) HOUSE_6001 objectId 130885 and Beluslan(220040000) HOUSE_7001 objectId 152343 — the same address-cached House re-spawned into a 2nd twin instance. Confirms the prior read-only static analysis at runtime. Faithful boundary: the test asserts the flattened exception chain contains DuplicateAionObjectException (not an unrelated DAO/NRE regression); NO un-faithful dedupe guard added. beyond-aion#2 Housing no-DB deferral EMPIRICALLY LIFTED: with the live (empty) players table, PlayerDAO.GetUsedIDs() returns int[0] (not null), so the HousingService ctor no longer throws ArgumentNullException — boot reaches deep into SpawnAll and HousingService loads cleanly. The GetInstance() block stays commented (enabling it does not change the SpawnAll house-twin boundary, and the no-DB bootstrap fixture must stay green); updated the deferral comment in GameServerBootstrapService.cs to record this finding. docs/next-slop-targets.md gets the empirical-run section. Green gates: build 0; ~Golden 167/167, ~Bootstrap 9/9 (8 pre-existing + new env-gated no-op), ~RealStaticDataLoad green; new DB test green (asserts faithful boundary) with the env var set. (2 full-run failures — stale-3306 DatabaseOptions test + ordering-contaminated GoldenStatsInfo — pre-exist on HEAD, unrelated.)
rrfarmer
added a commit
to rrfarmer/aion-server
that referenced
this pull request
Jun 18, 2026
… re-assessed — NOT a wire bug; live GS path is faithful-only, SerializeFrame is test-only; full unification gated on WorldNpc big-bang. Both build-zero fidelity bugs now resolved-or-understood
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
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.
Bumps mysql:mysql-connector-java from 5.1.36 to 8.0.28.
Changelog
Sourced from mysql:mysql-connector-java's changelog.
... (truncated)
Commits
7ff2161Updating copyright yearsb13af38Fix for DateTimeTest according to changes in MySQL server.5c7b775Update in test for Bug#96900 (30355150).e1169eeFix for Bug#99260 (31189960), statement.setQueryTimeout,creates a database co...05778efFix for Bug#103324 (32770013), X DevAPI Collection.replaceOne() missing match...48219f2Fix for Bug#105197 (33461744), Statement.executeQuery() may return non-naviga...24cf7e2Fix for Bug#105323 (33507321), README.md contains broken links.ad46620Fix for Bug#96900 (30355150), STATEMENT.CANCEL()CREATE A DATABASE4d19ea1Fix for Bug#104067 (33054827), No reset autoCommit after unknown issue occurs.bc45d35Fix for Bug#85223 (25656020), MYSQLSQLXML SETSTRING CRASH.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.