Skip to content

fix: Build against flatbuffers 25.12.19 - #201

Open
sidpug-arcana wants to merge 3 commits into
apache:mainfrom
sidpug-arcana:fix/flatbuffers-25.12.19
Open

sidpug-arcana wants to merge 3 commits into
apache:mainfrom
sidpug-arcana:fix/flatbuffers-25.12.19

Conversation

@sidpug-arcana

Copy link
Copy Markdown
Contributor

What's Changed

Supersedes #160 (chore: bump github.com/google/flatbuffers from 25.2.10 to 25.12.19), which fails CI on its own because the committed generated code was built with flatc 25.2.10 and is incompatible with the 25.12.19 runtime.

This PR includes the version bump from #160 plus the changes required to build and pass tests against the new runtime:

  • Regenerated the FlatBuffers Swift sources (*_generated.swift) with flatc 25.12.19, using the format/*.fbs schemas from apache/arrow (7151dcd6fa, i.e. the same schema revision the previous generated code was based on).
  • Adapted hand-written code to the new generated/runtime API:
    • Vector accessors changed from xxxCount / xxx(at:) to typed Vector collections (xxx.count, xxx[i]).
    • FlatBufferObject protocol split into FlatBufferTable / FlatBufferStruct.
    • ByteBuffer(data:allowReadingUnalignedBuffers:) was removed from the runtime, so the now-obsolete useUnalignedBuffers plumbing was dropped from the IPC readers and ArrowFlight.
  • gen-flatbuffers.sh: added an ARROW_FORMAT_DIR override and fixed the paths for the current repository layout.

Testing

Built and ran the full test suite locally (macOS, Swift 6.4), including the IPC file tests with fixtures generated by data-generator/swift-datagen:

Executed 46 tests, with 0 failures (0 unexpected)

Fixes #160.

@sidpug-arcana

Copy link
Copy Markdown
Contributor Author

@kou can you review and merge if this is okay ??

@kou

kou commented Oct 29, 2026

Copy link
Copy Markdown
Member

Could you work on #203 before this for easy to review?

Could you also update the PR title to follow Conventional Commits?

Bumps [github.com/google/flatbuffers](https://github.com/google/flatbuffers) from 25.2.10 to 25.12.19.
- [Release notes](https://github.com/google/flatbuffers/releases)
- [Commits](google/flatbuffers@v25.2.10...v25.12.19)

---
updated-dependencies:
- dependency-name: github.com/google/flatbuffers
  dependency-version: 25.12.19
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@sidpug-arcana
sidpug-arcana force-pushed the fix/flatbuffers-25.12.19 branch from 83c0262 to 664e3a1 Compare November 2, 2026 05:44
@sidpug-arcana sidpug-arcana changed the title MINOR: [FlatBuffers] Bump flatbuffers to 25.12.19 and regenerate generated code fix: Build against flatbuffers 25.12.19 Nov 2, 2026
sidpug-arcana and others added 2 commits November 2, 2026 15:50
Regenerate the Swift FlatBuffers sources with flatc 25.12.19 and
adapt the hand-written code to the new generated/runtime API:

- Vector accessors changed from `xxxCount`/`xxx(at:)` to typed
  Vector collections (`xxx.count`, `xxx[i]`)
- `FlatBufferObject` protocol split into `FlatBufferTable` /
  `FlatBufferStruct`
- `ByteBuffer(data:allowReadingUnalignedBuffers:)` was removed from
  the runtime; drop the now-obsolete `useUnalignedBuffers` plumbing
  from the IPC readers and ArrowFlight
- gen-flatbuffers.sh: add ARROW_FORMAT_DIR override and fix paths for
  the current repository layout

Co-authored-by: Siddharth Pugalia <sidpug@gmail.com>
Adapt the tests merged from main (TimeBitWidthTests, IPCTests) to
the new FlatbufferVector collection accessors.

Co-authored-by: Siddharth Pugalia <sidpug@gmail.com>
@sidpug-arcana
sidpug-arcana force-pushed the fix/flatbuffers-25.12.19 branch from 664e3a1 to 3c11295 Compare November 2, 2026 10:21
@sidpug-arcana

Copy link
Copy Markdown
Contributor Author

@kou can you check again i tried to update the things as per the convention

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.

2 participants