fix: use in-flake version of rocksdb instead of nixpkgs' upstream package #1802

Merged
Jade merged 1 commit from bart/continuwuity:fix/nix-build into main 2026-05-23 18:50:17 +00:00
Contributor

Fixes #1801

cc @Henry-Hiles

Pull request checklist:

  • This pull request targets the main branch, and the branch is named something other than
    main.
  • I have written an appropriate pull request title and my description is clear.
  • I understand I am responsible for the contents of this pull request.
  • I have followed the contributing guidelines:
Fixes #1801 cc @Henry-Hiles <!-- In order to help reviewers know what your pull request does at a glance, you should ensure that 1. Your PR title is a short, single sentence describing what you changed 2. You have described in more detail what you have changed, why you have changed it, what the intended effect is, and why you think this will be beneficial to the project. If you have made any potentially strange/questionable design choices, but didn't feel they'd benefit from code comments, please don't mention them here - after opening your pull request, go to "files changed", and click on the "+" symbol in the line number gutter, and attach comments to the lines that you think would benefit from some clarification. --> <!-- Example: This pull request allows us to warp through time and space ten times faster than before by double-inverting the warp drive with hyperheated jump fluid, both making the drive faster and more efficient. This resolves the common issue where we have to wait more than 10 milliseconds to engage, use, and disengage the warp drive when travelling between galaxies. --> <!-- Closes: #... --> <!-- Fixes: #... --> <!-- Uncomment the above line(s) if your pull request fixes an issue or closes another pull request by superseding it. Replace `#...` with the issue/pr number, such as `#123`. --> **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [x] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages
fix: use in-flake version of rocksdb instead of nixpkgs' upstream package
Some checks failed
Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 33s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 35s
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Checks / Prek / Check changed files (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Update flake hashes / update-flake-hashes (pull_request) Has been cancelled
452049412b
Fixes #1801
Member
hmm, why is this needed, given https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/nix/packages/continuwuity.nix#L13?
Author
Contributor

Since callPackage pulls in the upstream version. foo ? "default" only sets foo to the default of "default" if foo is not set.

Since callPackage pulls in the upstream version. `foo ? "default"` only sets `foo` to the default of `"default"` if `foo` is not set.
Member

Ahh, right, that makes sense.

Ahh, right, that makes sense.
Author
Contributor

Builds for me ;)

Builds for me ;)
Member

@Henry-Hiles wrote in #1802 (comment):

hmm, why is this needed, given https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/nix/packages/continuwuity.nix#L13?

Then can you remove this default plus the line taking in callPackage please? Then this is good, i think :)

@Henry-Hiles wrote in https://forgejo.ellis.link/continuwuation/continuwuity/pulls/1802#issuecomment-29631: > hmm, why is this needed, given https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/nix/packages/continuwuity.nix#L13? Then can you remove this default plus the line taking in `callPackage` please? Then this is good, i think :)
Member

If you just apply this, it will be good :)

If you just apply this, it will be good :)
Author
Contributor

@Henry-Hiles wrote in #1802 (comment):

@Henry-Hiles wrote in #1802 (comment):

hmm, why is this needed, given https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/nix/packages/continuwuity.nix#L13?

Then can you remove this default plus the line taking in callPackage please? Then this is good, i think :)

Doesn't matter IMHO, but I will :)

@Henry-Hiles wrote in https://forgejo.ellis.link/continuwuation/continuwuity/pulls/1802#issuecomment-29635: > @Henry-Hiles wrote in #1802 (comment): > > > hmm, why is this needed, given https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/nix/packages/continuwuity.nix#L13? > > Then can you remove this default plus the line taking in `callPackage` please? Then this is good, i think :) Doesn't matter IMHO, but I will :)
bart force-pushed fix/nix-build from 452049412b
Some checks failed
Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 33s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 35s
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Checks / Prek / Check changed files (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Update flake hashes / update-flake-hashes (pull_request) Has been cancelled
to db724b67ff
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 30s
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Check changed files (pull_request) Successful in 7s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m31s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 21m17s
Checks / Prek / Check changed files (push) Successful in 6s
Release Docker Image / Build linux-amd64 (release) (push) Failing after 3m13s
Checks / Prek / Clippy and Cargo Tests (push) Has been skipped
Documentation / Build and Deploy Documentation (push) Successful in 10m52s
Release Docker Image / Build linux-arm64 (release) (push) Successful in 11m37s
Release Docker Image / Create Multi-arch Release Manifest (push) Has been skipped
Release Docker Image / Build linux-amd64 (max-perf) (push) Has been skipped
Release Docker Image / Build linux-arm64 (max-perf) (push) Has been skipped
Release Docker Image / Create Max-Perf Manifest (push) Has been skipped
Release Docker Image / Mirror Images (push) Has been skipped
Release Docker Image / Release Binaries (push) Has been skipped
Checks / Prek / Pre-commit & Formatting (push) Successful in 21m17s
2026-05-23 18:00:44 +00:00
Compare
Jade scheduled this pull request to auto merge when all checks succeed 2026-05-23 18:02:06 +00:00
Jade merged commit db724b67ff into main 2026-05-23 18:50:17 +00:00
Jade deleted branch fix/nix-build 2026-05-23 18:50:17 +00:00
Contributor

So big issue lol, this compiles right, but at least on max-perf it leads to a core-dump when actually running the server and now I can't use Matrix :p

So big issue lol, this compiles right, but at least on max-perf it leads to a core-dump when actually running the server and now I can't use Matrix :p
Member

I'll look into it.

I'll look into it.
Member

I mean, a fresh build of this does work. I'll try using the previous database and see if it fails to migrate or something.

I mean, a fresh build of this does work. I'll try using the previous database and see if it fails to migrate or something.
Member

Still cannot reproduce a coredump. Can you provide some more info?

Still cannot reproduce a coredump. Can you provide some more info?
Member

Oh, actually, let met try max-perf

Oh, actually, let met try max-perf
Member

Hmm, actually I can reproduce a SIGSEGV now

Hmm, actually I can reproduce a `SIGSEGV` now
Member

Is that what you got also?

Is that what you got also?
Member

See #1808

See https://forgejo.ellis.link/continuwuation/continuwuity/pulls/1808
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity!1802
No description provided.