Skip to content

Drop kaitai checks#14897

Merged
Ericson2314 merged 1 commit intomasterfrom
drop-kaitai
Jan 5, 2026
Merged

Drop kaitai checks#14897
Ericson2314 merged 1 commit intomasterfrom
drop-kaitai

Conversation

@xokdvium
Copy link
Contributor

@xokdvium xokdvium commented Jan 1, 2026

Motivation

Pulling in the java into the tests closure for just testing a piece of code for the docs (and the tests actually are wrong, since a correct parser must reject those NARs). This is too much of an ask to maintain for zero benefit. I already had to disable it basically everywhere, because it works only on linux.

It can be revisited in the future, but considering that it's not exercised anywhere and shouldn't be used anywhere other than a toy example for the docs I think it's best to drop it.

Context


Add 👍 to pull requests you find important.

The Nix maintainer team uses a GitHub project board to schedule and track reviews.

@xokdvium xokdvium requested a review from edolstra as a code owner January 1, 2026 13:42
@xokdvium xokdvium requested review from Ericson2314, fzakaria and roberth and removed request for Ericson2314, edolstra and roberth January 1, 2026 13:43
Copy link
Contributor

@fzakaria fzakaria left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sad but makes sense

@xokdvium
Copy link
Contributor Author

xokdvium commented Jan 2, 2026

@fzakaria, agree this is unfortunate. I tried making this work better with the dev shell setups and hydra jobsets that we have and that's sadly a total pain in the butt with the amount of platforms we need to target. That's quite a bit of maintenance burden for something that making evaluate on hydra would take a non-trivial amount of hackery. Sorry :(

@xokdvium
Copy link
Contributor Author

xokdvium commented Jan 2, 2026

This is the most pragmatic approach that I've found. Wish there was a better way to have non-critical components, but we have quite a bit of maintenance burden on our side for existing things like i686, static and cross that needs constant maintenance and it's not getting as much attention as it needs to already. Something Java-related is a bit too much.

@grahamc
Copy link
Member

grahamc commented Jan 2, 2026

I wonder if keeping them as independent builds for the CI process would make sense? If not, then I suggest deleting the kaitai code, since it will inevitably grow stale and increasingly wrong.

@Eveeifyeve
Copy link
Member

I wonder if keeping them as independent builds for the CI process would make sense? If not, then I suggest deleting the kaitai code, since it will inevitably grow stale and increasingly wrong.

As said there is no benefits for keeping the checks and we can't gaunteee that it will work on other systems than linux. So it be removed we can always we add it back later if there is proven a needed benefit than a toy example we can revisit it later on.

Pulling in the java into the tests closure for just testing a piece of code
for the docs (and the tests actually are wrong, since a correct parser must *reject*
those NARs). This is too much of an ask to maintain for zero benefit. I already had
to disable it basically everywhere, because it works only on linux.

It can be revisited in the future, but considering that it's not exercised anywhere and
shouldn't be used anywhere other than a toy example for the docs I think it's best to drop
it.
@Ericson2314 Ericson2314 added this pull request to the merge queue Jan 5, 2026
Merged via the queue into master with commit 31bffd3 Jan 5, 2026
18 checks passed
@Ericson2314 Ericson2314 deleted the drop-kaitai branch January 5, 2026 15:39
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.

5 participants